Stuck on "Just a Moment" in middle of OOBE setup on newly image system

Hello,

I have build about 20 laptop images for a Lenovo Yoga S1 thinkpad. I use sysprep and a simple answer file with the license key embedded. I select generalize, oobe as sysprep options.

Half way through the OOBE immediately after selecting "customize" and before Azure/AD option and local admin account creation sections it gets stuck on "Just a Moment."

I am able to "work around" this, by waiting a few minutes and forcing the system off and then it will usually go to where it left off and I am able to create a local account. However it leaves a residual "defaultuser0" user in the User folder and in the registry which is obnoxious.

Any ideas what I am missing? I have created images with same process that work normally. So am at a loss as to what I may be doing wrong.

thanks for any help!

I have seen this behaviour in Tons of computers.
Main reasons can be (not sure why)
1. Secure Boot is On
2. Drive not formatted Properly

.. AS you are able to log in windows .. Just create a new user account with Admin Right.. Sikgn into it and delete old account.

Thank you Kari and manish9009!

Weirdly, I built an image for the Lenovo M900 tiny about a month ago (we have about 20). Two computers out of seven exhibited exact same symptoms (getting stuck and defaultuser0) when imaged and then the third (and the rest) worked fine from same image. On top of that I had 20 E460's that got stuck on "just a moment" but no defaultuser0 issue. I used the same answer file for them as well.

For the Yogas I built a new answer file from scratch didn't make a difference. Stuck and defaultuser0.

As for the secure boot, the image I built was done in legacy mode in MBR with secure boot off, but that is at least something to try and will keep in mind. Given that I am using Ghost to image and have not tried anything else--can't speak to formatting issues, but that seems unlikely.

In any case, I am glad to know its not something I've been doing wrong and the issue is not causing anything other than a short term, one time annoyance into this.

cheers!

Thanks Kari and ToadTilley!

I do quite a bit of sysprepped image creation as well.

A coworker was showing me his hand-rolled 1607 Win10 system and was wonder what the "defaultuser0" user account was for.

A quick search turned up many hits, but I was wondering why my Win10 builds didn't have this.

I did a clean install of these Win10 installs (1507, 1511, and 1607) (Enterprise 64-bit) and found some more info on this.

If I did a clean install straight from the ISO source files, the defaultuser0 account would exist when the desktop is reached.

It's MSOOBE.EXE that's creating that account. Look in the C:\Windows\Panther\unattendGC\Setupact.log file.
You may need to copy it to another location in order to view its contents.
Search the file for the string "created successfully".
This is what it read on each Win10 version:
1507: [msoobe.exe] Default account: 嗐ᾥL is created successfully
1511: [msoobe.exe] Default account: ༰㞫Ż is created successfully
1607: [msoobe.exe] Default account: defaultuser0 is created successfully.

Yes, 1507 and 1511 have the user name in some funky way.

Like Kari said, I rebooted my 1507 a couple times and the user account went away.

I set up another 1507 and left it at the desktop. After about 15 to 20 minutes, the user account went away.
Same with the 1511.

Not so for the 1607. It's now been half an hour and the user account is still there.

I haven't found a log file yet that says what removes the account on the 1507 and 1511 systems.

It looks like 1607 has something mucked up with the removal of the account.
I see that there are many threads regarding the 1607 upgrade putting this user account in place and not removing it.

After my coworker brought this user account to my attention, I was wondering why this account didn't exist in my sysprepped 1511 image.
It wasn't that it was deleted automatically as in my clean install tests, but rather because my install for the sysprepped image is run with an unattend.xml which tells it to skip the OOBE and log in as THE Administrator.

I hope this info helps.