MDT Deployment hangs at OOBE stage and does not reboot to continue "State Restore" phase?

Question

My new MDT image deployment reboots into the deployed WIM on the OS Disk and starts OOBE (I think)? But, I think it should restart after OOBE completes and then continue into the "State Restore" phase of the Task Sequence.

Where can I find the OOBE logs at this stage to see what is going on/wrong?

The bottom line in the C:\MININT\SMSOSD\OSDLOGS\BDD.log has this (but the machine has not rebooted):

Event 41017 sent: LTI initiating task sequence-requested reboot. LiteTouch 01/09/2023 09:48:04 0 (0x0000)

The machine console is hung with "Just a moment" displayed.

If I reboot, or login as Local Admin, the deployment will continue to successful completion - but that is not really a suitable solution for production deployment, and may indicate the deployment is not "good".

Thanks in advance for any suggestions

Gary

Answer 1

If I remotely reboot the machine whilst the console is hung at the "just a moment" screen, then the Deployment the continues and successfully finishes with no other input.

I also note that the Local Administrator account folder gets created too, and some (but not all) of the Deployment "junk" folders are removed:

So, it seems to me that the problem is just that the reboot does not happen after the OOBE setup completes, how do I go about debugging/fixing this, as I can't just at a reboot action to the task sequence?

Thanks

Gary

Answer 2

I have checked C:\Windows\Panther\setuperr.log and it is empty, but C:\Windows\Panther\UnattendGC\setuperr.log has this line in it:

2023-09-01 11:50:02, Error [CloudExperienceHostBroker.exe] Disabling default account failed [hr=0xD00000E5]

I believe CloudExperienceHostBroker.exe is what runs the OOBE setup as the defaultuser on first boot of a generalised image.

The bottom of the C:\Windows\Panther\UnattendGC\setupact.log, has this in it where you can see this error too, but also the delay whilst I then manually reboot the machine to get it to finish (I think the hours are skewed due to initial timezone being wrong until I reboot):

2023-09-01 11:50:02, Info [taskhostw.exe] OOBE Monitor event received: 999
2023-09-01 11:50:02, Info [CloudExperienceHostBroker.exe] Clearing Auto-logon values per request
2023-09-01 11:50:02, Info [CloudExperienceHostBroker.exe] Transferring unattend.xml autologon values
2023-09-01 11:50:02, Error [CloudExperienceHostBroker.exe] Disabling default account failed [hr=0xD00000E5]
2023-09-01 14:03:15, Info [svchost.exe] Enter WinReIsWimBootEnabled
2023-09-01 14:03:15, Info [svchost.exe] Parameters: pszWinDir: NULL
2023-09-01 14:03:15, Info [svchost.exe] Exit WinReIsWimBootEnabled returns 0 with last error: 0x2

So, is it this that is causing the OOBE to hang and not reboot like it should, perhaps?

Answer 3

Hi, @Gary Mansell

Thank you for posting in Microsoft Q&A forum.

The OOBE logs can be found in the following location: %WINDIR%\Panther\UnattendGC\setupact.log.

For the error "Error [CloudExperienceHostBroker.exe] Disabling default account failed [hr=0xD00000E5]", check if this helps:

https://social.technet.microsoft.com/Forums/en-US/0a725d09-56b9-48b2-912b-d883b2567bd6/windows-10-1803-deployment-cloud-experiance-problem

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".