win7 deployment - stuck after loading wim files (w8 boot screen??)

Unanswered win7 deployment - stuck after loading wim files (w8 boot screen??)

  • Sunday, February 03, 2013 8:57 AM
     
     

    hi

    I just updated to 2012.

    I added Windows 8 to my deployment shares (seperate folder)

    All was well until I decided to do a new capture of Windows 7 to get all updates etc. included into the .Wim file.

    Now... after changing my standard TS, step: install operating system to the new .Wim there seems to have happened something..

    After doing a complete rebuild of the deployment share, adding the new file to wds, and starting up a test VM, the VM "stops" after loading files... it displays the Windows 8 logo (just the slightly skew 4 Square Windows logo in a light blue color)... and that's it.. it just does that.. nothing else...

    There is no log started since I haven't selected a TS and mdt hasn't started the customsettings check yet..

    it just sits there... :-|

    I can't even do a F8 to get a cmd so I at least can check stuff.. .but what can I do to error-check this?


    Kindest regards, Martin

All Replies

  • Sunday, February 03, 2013 11:34 AM
     
     

    ok.. It's something in the bootfile

    I created a generic Wim file and an iso file.. and all are showing the same problem...

    I tried mounting the .Wim file to check if I could find something.. but so far I can't see anything out of the ordinary...

    what can I check?


    Kindest regards, Martin

  • Monday, February 04, 2013 6:58 AM
     
     
    Are you using VMs or physical computer? If you are using VMs you could try to boot a physical computer and vice versa to see if it works. If it does its probably a driver related issue.
  • Monday, February 04, 2013 8:03 AM
     
     

    damn...

    it works on a laptop.. but not on a Hyper-V machine???

    what drivers could be implicated here?


    Kindest regards, Martin

  • Monday, February 04, 2013 1:58 PM
     
     

    we have had the same problem with one specific system i forgot the hardware specs.

    we didn't find a solution other then doing a manual install or using winpe 3 instead of 4