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!
First, the defaultuser() account: it seems that it is a minor bug in Windows with nothing to do with sysprep or your answer file. It seems to be present even after a clean install on clean hardware in Pro, Education and Enterprise editions. In Home editions I have not seen it.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 do quite a lot sysprepping and image customization (re: this tutfor instance) and have basically given up to find an explanation for that after finding out that this profile will be created also after totally normal clean install.
I am testing various first run scripts as we speak, to add a Run Once batch to be run when initial user signs in first time to remove this profile (it's totally safe to just delete it).
I clean installed Windows 10 Pro Anniversary Update Build 14393.10 on a Hyper-V vm on Tuesday, with default settings, no sysprep. After OOBE, first sign in to desktop, this is what Users folder shows:For why your OOBE freezes when run first time and continues without issues when restarted I have no ideas at the moment. I've seen that behaviour, as well as OOBE restarting after settings selection by itself two three times always returning to settings selection before finally continuing from there, still no clue why this is happening.
Kari
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!