Windows 10: Issue with source machine after it was sysprepped.

I reimage a machine with my current image. I make a few file change and sysprep it.After the machine is powered back on, using a std sysprep.exe /generalize /oobe /shutdown /unattend:c:\unattend.xml. When the machine starts I get the "just a moment" screen and then after a few minutes machine will reboot and I will get a blue screen stating Why did my PC restart?I boot the machine with a winpe stick and copy the log in the c:\windows\panther\UnattendGC to check them. I see no error that would cause screen.What have I not checked? Where do i go from here.

:)

 

SysPrep Advice

Hi Joseph,

The topic that you raised is beyond the scope of support for this site which focuses more on home and personal end users. Here's what I found about SysPrep:

• What Is Sysprep?
• How To Sysprep – Sysprep is a Great And powerful tool And Easy
  Too If You Know How (Step-By-Step).

However these are old articles and the process may have been changed already. You may re-post this question in

TechNet Forums for further assistance.

All the best.

 

Windows 10 1709 sysprep fail

Hi,

I had the same problem, checked the logs and they basically said Windows was unable to remove the Miracast app.

Tried multiple suggestions, nothing worked until I found this:

https://social.technet.microsoft.co...pture-windows-10-fall-creators-1709?forum=mdt

Basically Microsoft have pushed out their 1709 image without the Miracast app installed, to fix:

• Copy the C:\Windows\MiracastView folder from a working 1703 build into the C:\Windows directory on the 1709 machine
• Restart and then run sysprep

Sysprep should then run successfully!

Josh

 

Windows 10 1709 sysprep fail

Unfortunately this did not work for me.