This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 71%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
I have a new MDT image that, when I deploy to a machine, hangs at the "just a moment" configuration phase forever.
I have found that I can prompt it to then continue (to installing applications phase) by RDP'ing in as Local Admin and then the MDT TS "State Restore / Gather Local stage" kick into gear and the application installs complete and it finishes the deployment with no errors.
Also, Power cycling the machine whilst stuck at the "just a moment" screen allows it to continue to successful completion - but I am not so sure this is a good idea!
When the machine is hung, I can see that it is joined to the Domain, and that the C:\MININT and C:_SMSTaskSequence (or similar) junk folders are still present and the BDD.log bas not been copied to WinDir\Temp\DeploymentLogs (so it's as if the cleanup has not happened?)
Here in this screenshot of the final BDD.log, you can see that it is just stuck since 29th Aug 14:30 until I then login using RDP as Local Admin - and then it continues, quite happily. On the console it shows "Just a Moment":
I attach the entire BDD.log - maybe someone can tell me why it is getting stuck here and how to fix?
Thanks
Gary
Here is the Task Sequence - I think it might be hanging before or after the "Restart computer":
Here is the event viewer admin events showing the time of it kicking back in to life when I logged in via RDP today:
There are hundreds of Client-Licensing errors (not sure if they are relevant - but they are around the time that it hang yesterday during deployment):
I have had a look through, and I cannot see a Reboot in the Event Viewer - so my best guess is that it is hanging before the Restart stage of the Task Sequence...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
I have a new MDT image
If it will appear that hangs at "just a moment" when we use an old image?
so my best guess is that it is hanging before the Restart stage of the Task Sequence
Please try to replace the restart computer step with Run Command line: shutdown /r /t 0 /f
So, I sat infront of the computer as it was imaging and I can confirm that the Restart action does occur as expected (after the OS WIM install and unattend.xml are applied whilst it is PXE booted).
Then, it shows a Dell logo whilst it gets devices ready and windows ready etc... Then, it boots into Windows and that is when the "Just a moment" screen appears (and stays forever).
I also note, at this time when it is showing the "just a moment" screen - that it appears in the Domain's computers OU, so it must have been Domain Joined as part of the Windows OS boot. Does this mean that the "Recover From Domain" Action (highligted in the TS below) was reached, or is the Domain join done somewhere else?
If so, it seems likely to me that the "Recover from Domain" and "Tattoo" Actions probably ran OK, and the issue is with the login to the machine before the final Install Applications Action can run - in this case our "Standard CAD OS build Components".
So - where do I find the logs that tell me what the login issue was and to confirm where/why it is hanging?
I also note, when I access the machine's C: drive over the network whilst it is hung at "Just a moment", that these folders still exist on the machine:
I thought these folders were removed by the "Post-Apply clean up" action - so how come these are still present when it seems to have moved passed here and done the "Recover from Domain" action successfully?
If I then RDP to the machine as Local Admin, first I get this screen:
Then, this:
Then, the RDP Session disconnects, and when I then immediately RDP in again, it then seems to login completely to the Desktop this time and run the "Gather Info" stage (which confuses me as I thought we must have gone past this stage to do the Domain Join)?
It then installs the Standard CAD OS Build components (applications):
Whilst doing the Application installs, I can see that the "Drivers" folder has been deleted from the root of C: (but the other MDT folders still are present):
And finally goes all the way to completion successfully (and delets the MDT build folders):
And the logs are copied to the MDT Server (I attach the BDD.LOG and the panther\unattendGC setuperr.log and the setupact.log files)
In the setuperr.log file, I see this which might be something (as it is around the time that the "Just a Moment" screen occurs)?
2023-08-31 10:22:33, Error [msoobe.exe] WinRE not configured
The setupact.log shows this:
So, does all that info give anyone any clues as to why this is hanging at the "Just a Moment" screen and how I get this fixed?
Thanks in advance for any help.
Gary
I also note that the Recovery Environment is disabled in the resulting OS:
I have fixed up the disabled Recovery Environment in the Master image, re-captured it, and when I deploy it, it still hangs at the "Just a Moment" screen when it does the first Administrator auto-login after booting ito the deployed image on the machine.
But, if I login via RDP as Admin, then the MDT Task sequence will eventually continue from the "State Restore" section of the Task Sequence and complete successfully.
I upload a new set of the log here (the panther/setuperr.log and panther/UnattendGC/setuperr.log - are both empty files now)
Any suggestions what is hanging the deployment, woulc be welcome?
Bumping this - to see if anyone can help me on this still?
Some further things I have tried to no avail:
Adding <SkipMachineOOBE>true</SkipMachineOOBE> in the unattended.xml (in the OOBE section) - breaks the deployment with the error "There was a problem starting GetCurrentOOBE.dll". I also note that this is a deprecated setting.
The registry value "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorAdmin" is already set to the DWORD value 5
The "defaultuser0" is already present as a member of the Administrators Group
A reboot after leaving the machine at the "Just a moment" screen for half an hour (to be sure whatever it needs to do has been done) - causes the machine to come back up and login as Admin as expected and completes the deployment successfully.
Any ideas where I can go next on this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 9%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECT%3C/text%3E%3C/svg%3E)
Hello,
Were you able to resolve this? I'm running into roughly the same issue, except for me the "just a moment" screen finally goes through after about 20 minutes. It just started happening to my images around the same time as you. I'm still using windows 10. my suspicion is that is has something to do with it trying to join the domain.
I can post what I've found so far this week and hopefully it'll help. Let me know if you're still having this issue though. Thanks!
Hi, in the end what worked was to re-install Windows into the master image (retaining apps and data). Then it went all the way through no problemo