Windows 10: Error after booting a VM after Sysprep

  1.    22 Sep 2015 #1

    Error after booting a VM after Sysprep


    Howdy,
    So we're trying to get our first Win10 VM up and running. I downloaded the latest ISo from the Volume License site and installed it on a VM just fine. I ran all Windows Updates as well.

    After that I ran Sysprep and choose OOBE, Generalize, and Shutdown. I then copied the VHDX file to a new location for a new VM as we normally do.

    That all seemed to work fine until I then attached that hard drive file to a new VM and fired it up. After clicking the through the timezone page I get an error stating:
    Windows could not complete the installation. To install Windows on this computer, restart the installation.

    I found some info online about changing the minimum password setting to 0 but that did not help. I then fired up my Template machine to see if that would setup fine and that now gets the same error so I'm kind of stuck.

    Has anyone had this error before and is there a fix for it? I don't want to have to do manual steps on every VM we create
      My ComputerSystem Spec


  2. Posts : 11,252
    Windows 10 Pro
       22 Sep 2015 #2

    The correct procedure would be:
    • Install Windows 10 without a network connection (Yes, really: no network connection until in Audit Mode!)
    • When done and the OOBE starts, reboot to Audit Mode
    • When in Audit Mode, connect the vm to the network
    • Do not update Windows! This is extremely important, the Sysprep process still has some bugs this being one, updating Windows will most probably cause Sysprep to fail
    • If customizing, be careful: again one of the Sysprep bugs in Windows 10 is that the CopyProfile component in answer file might cause issues. You can quite safely generalize build 10240 with CopyProfile set to TRUE but later builds 10525, 10532 and 10547 will be totally screwed if CopyProfile is used
    • Run the Sysprep
    • Capture the image
    • Deploy the image to a new vm or physical machine

    Kari
      My ComputerSystem Spec

  3.    22 Sep 2015 #3

    We don't do any customization at all. We only update our templates so that Windows Updates are completed. The rest of our settings are GPO pushes.

    So I guess I might as well just install Windows directly on each VM since it doesn't take very long and will wait to make a Template image until they fix Sysprep?

    Thanks.
      My ComputerSystem Spec


 

Related Threads
Windows skip oobe after sysprep in PC Custom Builds and Overclocking
hello, i am making an deployment image of Windows 10. i have made an answer file whith skip oobe. but after i have syspreped and captured the image, boots up the newly made Windows 10, the oobe keeps coming up. can anybody help me?
I am sorry if I am not very good at constructing this, but this is a log I had come across after fiddling around with the "OS Error Fix Menu????" Logfile: C\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt I am not sure if that is of any help what...
Sysprep error during win 10 upgrade in Installation and Upgrade
Hi there. Using the media creation tool (both usb and ISO) I get an error. Something like "installation has encountered an error during first_boot with sysprep." In not at my toshiba laptop at the moment so the wording may be a little off. Upgrading...
Working with ICD and Sysprep in Installation and Upgrade
Trying to work on creating Windows 10 Image deployment without MDT. Ideally what I am thinking is that I use system Image manager to create an unattend.xml file for the main image. Then I am hoping i can use the ICD to apply Desktop Image...
SYSPREP issues in Installation and Upgrade
Hi, I am wondering if anyone is experiencing the same issues i am, after (apparently successfully) SYSPREPping a Windows 10 (clean) installation, and restarting it? BTW: i have used a very simple autoanswer file: <?xml version="1.0"...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:03.
Find Us