Windows 10: Breaking OOBE setup bricks the lock screen?

You can read about how my lock screen is not working over here: https://answers.microsoft.com/en-us/windows/forum/windows_10-hello/cant-do-anything-with-the-lock-screen/649395e4-9bf7-4cc6-b005-b8f7c444730b?tm=1613122250736


Although this was done on and Insider build, it has nothing to do with Insider bugs, as this can be reproduced on a stable release since OOBE hasn't changed much. So please don't switch this question to an Insider bug report

I know the secrets of the Windows 10 OOBE thanks to the internet and that's the reason why I managed to break everything.


So I was on my way setting up an Dev channel Insider installation on a second hard drive when I got stuck at "Checking the connection to Microsoft" no matter how good the connection is it will just spin infinitely and prompts me to connect to another one. I've tried everything from resetting the router, tethering from my phone to even Googling, all didn't help. During troubleshooting I managed to get the Settings app open. Then I thought "I'm on an older Insider build 21286, maybe this is a bug that they fixed in the next build?", so I went to Windows Update and let if flew to build 21301. But I was wrong.

After the flight, instead of continuing the setup I got into defaultuser0's desktop the once-use user used for the OOBE setup process. Well, I thought I might have skipped the setup, so I went ahead and created my user through Settings like I normally would on a properly set up install, deleted defaultuser0 through Command Prompt and thought I made my day, until I found out the lock screen was inaccessible. I got bored so I went back to my main stable install on the other drive.


Coming back a few weeks later, I was surprised by this:

Windows somehow still tries to login to its long-gone once-use user, thinking that the setup hasn't done yet, even if the registry told it it's done already: before that it autofilled something into the password field then said the username or password is incorrect



I'm still able to login to my user, but again, no lock screen. The "managed" setting thing might be to prevent the end-user from accidentaly lock out defaultuser0 and don't know how to log back in as it's protected with a secret random password afaik. But I'm done already so why didn't it give me the setting back?


Any of you guy's help are appreciated. Thanks.

:)

 

PC Build Steps

Ok just because I like steps i am going to create some steps. Please give me the stamp of approval/disapproval

• Install system in case
  • Remember to connect SSD and optical to same SATA ports on motherboard
• Turn on PC
• setup HDD
• run blend test in prime95 for 30-60 min
  • run realtemp at the same time

• While in Prime95 test
  • if CPU goes above 70c in RealTemp, I have a leaky CPU
  • if my system locks up or blue screens, there is an instability in the system somewhere
  • if my system does not lock up or blue screen, my CPU is not damaged and I am in the clear!

What do you guys think??

 

Lock screen woes

Hi,

Thank you for posting on Microsoft Community.

I would suggest you to follow the below steps to try resolving the issue.

Setting the timeout for Lock Screen

• Press Windows + I and select personalization.
  
• Select Lock screen.
  
  
• Select the Screen Timeout setting.
  
• Select the time of timeout you need and check.

Keep us posted if the issue resolves to help you better.

 

Lock vs Login screen screenshot

You can use your own image of any background and just go to settings/personalize/lock screen and click on browse as in the image below. It should make whatever picture you use as the Lock Screen