SOLVED

SYSPREP + 1709 = OOBE stuck at logon screen with "defaultuser0"

Brass Contributor

Okay, we've sliced and diced this every which way until Sunday.

 

When you prep an image for Windows 10 CBB Enterprise v1709, you'll get stuck at the logon screen during OOBE with "defaultuser0". You can hear Cortana babbling her spiel but you're basically dead in the water since OOBE didn't automatically logon with the "defaultuser0" account.  We've done nothing out of the ordinary during the preparation of the image.  Basically, we ran SYSPREP w/"generalize" and OOBE as the selected options. We then uploaded it to our WDS server after creating the image w/IMAGEX.

 

Anyone else having this issue?

 

Thanks!

9 Replies

I am having exactly this same issue. Did you solve it?

No, we can't seem to get passed this issue regardless of what we've tried.

best response confirmed by Daniel Smith (Brass Contributor)
Solution

First of all, I strongly recommend using Microsoft Deployment Toolkit to build and capture the image, it has built-in fixes for common issues. 

 

That being said, the November 2017 CU seems to have fixed the OOBE issues in 1709, and to get Cortana to stop annoying you (and others), you can set a registry key during OS deployment.

 

Keith has a good post here: 

https://keithga.wordpress.com/2017/12/11/silence-is-golden-during-setup

 

I have a script you can add to a MDT task sequence here: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Config-DisableCortana.wsf

 

And, Anton has a post here on using that script: http://www.vacuumbreather.com/index.php/blog/item/60-disabling-cortana-voice-support-during-oobe  

 

Thank you sir! We'll try this again. :)

Hi Daniel, did you have a time to test it? It takes some hours and I've been busy lately, please let me know if it is finally working for you.

Regards,

Just tested it today... No Dice!

 

I used a freshly installed copy of 1709 w/all of the updates current to 1/16/2018. I ran Sysprep and then uploaded to WDS using ImageX. Then I imaged a new box with the new image and was presented w/the same situation:

 

Instead of the OOBE wizard, I'm given a lock screen with "defaultuser0" as the currently logged on user. You can hear Cortana blathering in the background.

Please stop using WDS without the MDT integration. WDS+MDT gives a much better experience, and the integration makes it much easier to make custom changes on the fly during OS deployment. This platform is also tested end-to-end for modern deployment scenarios.

 

Anyway, by tweaking the unattend.xml to add the registry keys for Cortana to be quiet, it should work with just plain vanilla WDS as well (not tested). Here is a post explaining the process: https://keithga.wordpress.com/2017/12/11/silence-is-golden-during-setup/

 

For WDS with MDT, I have posted a script here that you can add to your task sequence: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Config-DisableCortana.wsf

 

/ Johan

 

 

Okay, we prepped an image using MDT and even removed the OOBE via ICD.

 

Result: Stuck at logon screen with "defaultuser0" after imaging.

Any luck? Experiencing the same issue here. 

1 best response

Accepted Solutions
best response confirmed by Daniel Smith (Brass Contributor)
Solution

First of all, I strongly recommend using Microsoft Deployment Toolkit to build and capture the image, it has built-in fixes for common issues. 

 

That being said, the November 2017 CU seems to have fixed the OOBE issues in 1709, and to get Cortana to stop annoying you (and others), you can set a registry key during OS deployment.

 

Keith has a good post here: 

https://keithga.wordpress.com/2017/12/11/silence-is-golden-during-setup

 

I have a script you can add to a MDT task sequence here: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Config-DisableCortana.wsf

 

And, Anton has a post here on using that script: http://www.vacuumbreather.com/index.php/blog/item/60-disabling-cortana-voice-support-during-oobe  

 

View solution in original post