So basically with the MediaCreationTool I could re-install the windows, after I put the key it detected the correct windows version.
I hit the same problem, however turning off the ethernet cable I was able to bypass the screens.
Thanks once again!
I still don't understand why MS is forcing the connection to internet.
How do I set up a local account now?
So basically with the MediaCreationTool I could re-install the windows, after I put the key it detected the correct windows version.
I hit the same problem, however turning off the ethernet cable I was able to bypass the screens.
Thanks once again!
I still don't understand why MS is forcing the connection to internet.
Hi there,
This is Tamal trying to help you with the issue.
Yes, you can go you with the fresh installation. You may not need reactivate windows upon installation as the process is automated. You can still use your windows 7 key during installation or proceed with choosing I don't have a key option.
I think your reset was not complete or might be initial installation was done as a domain joined computer. You have tried all the good things and those should have worked, but as that is not happening better go with the fresh installation after creating an installation media.
Videos
I’m doing a data transfer at work today and I have to bypass the create you’re account on windows and I can’t seem to run oobe\bypassnro, it’s comes back saying “not recognized externally or internally”
More specifically “ ‘oobe\ is not recognized as an internal or external command”
Since according to AveYo (thanks for this) this is only temporarily integrated into Windows 11 by Microsoft, one can assume that this command will not work for much longer. I truly hope it remains.
oobe\bypassnro
Then you can reactivate the Internet connection and add a password to the account, as well as make all other settings.
Alternative Workaround that should remain feasible, more trouble than the simple above command:
If the Internet is disabled, you start the reinstallation of Windows 11. You get to the window: "Unfortunately you have lost the Internet connection". From here it starts. Replace "User Name" with whatever you wish to use for the account:
Press Shift + F10. The command prompt opens
net.exe user "User Name" /add
net.exe localgroup "Administrators" "User Name" /add
cd OOBE
msoobe.exe && shutdown.exe -r
Windows will now restart and start with the other settings until Windows 11 is installed correctly with a local account.
When logging in, "The user name or password is incorrect" now appears.
Simply press OK and select the right account at the bottom left of screen. You should have one for Administrator and one for whatever name you used as "User Name" above.
Lets hope the simple oobe\bypassnro stays, as I have used both methods, and the first is by far the easiest.
Regards,
[I edited this message to remove the unnecessary content at the top. Please refrain from the personal attacks. - Jason]
Great piece of info, will save it for future use
I just had trouble with this on a Lenovo laptop I got. I’m just gonna get straight on with it
-
Press shift + f10 or fn + shift + f10 (don’t leave hear me out)
-
Then for a split second you should see the blue mouse loading circle and nothing happens, next do Windows + R
-
Put in “ms-settings:” then go to system, then recovery, click recovery mode. Then restart now
-
Go to trouble shoot, advanced options and then startup options, click restart
-
Click 7 (disable digital signature enforcement*) on your keyboard when you see a bunch of options
-
You should be back at setup, do shift + f10 again, this time CMD should pop up. Put in oobe\bypassnro
-
After restart, open run (Windows + R) put in ipconfig /release and continue with setup
-
If anything happens like the sign in menu pops up then do the last step before this one (ipconfig /release) and then press the little arrow in the corner to go back a page and it should bring you to choose a name for the local account.
Explanation: with Windows 11 S Mode you can only run Microsoft verified apps, oobe/bypassnro.cmd isn’t signed by Microsoft so in this case isn’t Microsoft verified. CMD is also disabled and in order to get into CMD we can use the “disable digital signature enforcement” in the advanced startup which will ignore the rules set in place for S Mode and open CMD.
*Keep in mind that disabling signatures will be temporary until a restart happens
You know what even crazier? I’m literally 13 and did this. I couldn’t find a tutorial anywhere. Consider this a new bypass for S Mode if you want a local account.