Windows 10 Death Loop/Reboot

[Wayne Workman]

@msaglioc99 Read through this for sysprep information while using the fog client: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

[msaglioc99]

I’ve followed those instructions, disabled the service and placed the .cmd txt file in the folder stated.

[Wayne Workman]

@msaglioc99 Ok, on this computer that is rebooting - when you’re at work - let it reboot a couple more times and then disconnect it’s network cable completely - let it do it’s thing for a while longer after this, it should stop rebooting. Then I need you to get a copy of the C:\fog.log file (use a thumb drive) and post the last 1,000 or so lines from it to here. It should tell us exactly what is happening and should lead us to an answer.

[msaglioc99]

Okay I’ll do this Monday morning. Thx!

[george1421]

@msaglioc99 I’ve been working on 1703 in my home lab and I’ve run into the issue where windows can’t install correctly after sysprep.

After some intense debugging there are a few things that I came across.

1. I have to place the unattend.xml file in c:\windows\panther if I placed it in the traditional place I’ve used since, forever c:\windows\system32\sysprep I was getting an error that windows couldn’t install because it couldn’t find the defined unattend.xml file. As soon as I change the location to c:\windows\panther and updated my sysprep command that part worked.
2. For my unattend.xml file I decided to use the online generator here: http://windowsafg.no-ip.org/ I wanted to use this site to generate the unattend.xml script because I wanted a clean unattend.xml file and not rely on the one I’ve used for imaging for years. The unattend.xml downloaded from the online generator caused another error in that the product key defined by the generator was not liked by OOBE for Win10 1703. I removed the product key from the unattend.xml that came from the online generator and then it worked.

Once the above fixes where implemented the sysprep and reboot on the reference system worked correctly. I’m currently in the process of rebuilding the reference image completely again with MDT to start with a clean build again to test the next part (capturing and deploying with FOG). To see if I can generate the error in this and other threads with not being able to capture and deploy the image correctly.

[msaglioc99]

Awesome ! I’ll have to try moving the XML file Monday as of now the image I uploaded with disabling the FOG service and creating the cmd script as found in the Wiki worked. So if I deploy to it using FOG it works fine. The only way it gets stuck in a reboot loop now is if I tell it to join to the domain after the task has been complete in the AD settings. If this is checked it gets stuck in the loop. There’s definitely some kind of conflict between FOG and Sysprep when booting the machine up.

[msaglioc99]

Okay so the image I created with sysprep seems to work with the FOG Client Service but if I use that same image and tell it to join to the domain after the task has been complete it gets stuck in the reboot loop. Even after disconnecting it from the network it get’s stuck in this loop. I’m assuming this loop has something to do with the FOG Service and sysprep as this seems to be the common denominator. I have already followed the Wiki Instructions and disable the FOG Service and placed the .cmd file to start the service back up. Any ideas? Thanks for all your help!

[Quazz]

@msaglioc99 What happens if you turn off force reboot for AD join?

It’s possible it tries to join/change name, fails for some reason, forcefully reboots, and thus gets stuck in a loop.

[Sebastian Roth]

@msaglioc99 Is this solved yet?

[msaglioc99]

This has been solved. It was an issue with Sysprep and the FOG service starting at the same time. I had to disable before Sysprep and uploading the image and then creating a cmd file to re enable the service.

[Quazz]

@msaglioc99 I don’t quite understand, you said you had already done that earlier when it wasn’t working, what changed?