Solution: Install Windows 10 instead.
Set up Windows 11 without internet - oobe\bypassnro
Ok, now on Insider builds you can't get it past anymore by killing OOBE Connection Flow. This is just nonsense.
How are we supposed to set up PCs that don't have any Wi-Fi/Ethernet drivers in the first place?
When killing Connection Flow you just get this message:
Here is the solution:
Open cmd with Shift + F10 and type OOBE\BYPASSNRO.
Your computer will restart and now you will have the "I don't have Internet" option.
No need to thank me.
Windows Insider program | Windows Insider preview | Install, activate, and Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
143 answers
Sort by: Most helpful
-
Anonymous
2023-05-20T00:46:47+00:00 -
Anonymous
2023-05-12T03:47:48+00:00 I run in the Problem that the Command dint worked. Simple fix just Type as the first Command cd oobe to navigate in the folder. Then just Type beypassnro for the second Command*.* The PC or VM will Restart and you have the option to say you don't have Internet.
Kind Regards
Max
That works too, but I never had the need for "cd oobe" because oobe\bypassnro always worked fine for me after Shift + F10. 🤷♂️
-
Anonymous
2023-05-11T15:42:52+00:00 Nothing changed, M$ updated something to stop making this command (OOBE\BYPASSNRO) work. RIP.
-
Anonymous
2023-04-20T05:08:30+00:00 BypassNRO.cmd and msoobe.exe are both on the same folder System32\oobe, perhaps both ways would work the same if they really removed the bypassnro.cmd. I'll give it a try next time. 😎
oobe\msoobe.exe /bypassnro
Edit:
That "msoobe.exe /bypassnro" for sure did not work. 🤣🤣🤣
Just sits in a loop with spinning dots with a message "Just a moment..." and never reboots. 🤷♂️
Had to power off. 🤣🤷♂️
When I rebooted it prompted to login to a default user. 😵💫
Perhaps only on machines that come with Windows preinstalled they have msoobe.exe to handle that parameter /bypassnro, but that is not the case for the MS MCT ISO nor for the Insider ISOs. 🤷♂️
-
Anonymous
2023-04-20T00:20:58+00:00 New PC setup did not have OOBE in the root of system32 - if it's not there try:
windows\system32\oobe\msoobe.exe /bypassnro
that did the trick for me. hope this helps someone else :)
Which Build were you installing?