Earlier this morning I was troubleshooting a failing build and capture of a Windows 10 build 9879 image using MDT 2013. What happened was that when the sysprep action run, the task sequence immediately rebooted, causing the following crash on reboot (Error code: 0xc0000428 ):
Sysprep rebooting on it’s own, even when told not to, seems to be a new “feature” in build 9879 (to be verified), but at least I found a workaround for the issue, so keep on reading…
The not so nice error message.
The why
After some troubleshooting I found out that it was a pending a reboot causing the sysprep action to reboot the machine after WinPE had been applied, but before the task sequence had a chance to configure the BCD.
The info was found in BDD.LOG (as well as in the LTISysprep.log since BDD.log is just aggregating all other logs).
The BDD.log file showing the issue (Office 2013 setup requiring a reboot).
The Fix
In addition to the normal task sequence edits needed for having MDT 2013 deploy Windows 10, described here, I simply added an extra reboot prior to the Apply Windows PE in the task sequence.
I also modified the ZTIBackup.wsf script to use DISM instead of ImageX, a best practice when deploying anything newer than Windows 7 SP1. Those mods are described here.
Adding the extra reboot to the task sequence.
WIM file being created.
/ Johan
More ...