>OOBE not found.
Did you type it exactly as shown? No space: oobe\bypassnro
Still worked fine with 25309.1000 ISO.
Set up Windows 11 without internet - oobe\bypassnro
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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: Oldest
-
Anonymous
2023-03-07T04:08:44+00:00 -
Anonymous
2023-03-07T05:59:50+00:00 >OOBE not found.
Did you type it exactly as shown? No space: oobe\bypassnro
Still worked fine with 25309.1000 ISO.
Yes I did
-
Anonymous
2023-03-07T06:19:44+00:00 >OOBE not found.
Did you type it exactly as shown? No space: oobe\bypassnro
Still worked fine with 25309.1000 ISO.
Yes I did
What build number are you using for the installation media?
This command only failed with one specific Build, 25193 was mentioned earlier on this thread, never had any problem after that for several months now.
If you tell me which Build number you are using, I can give it a try. 😎😉
-
Anonymous
2023-03-07T06:35:37+00:00 This command only failed with one specific Build, but I don' remember which one it was, never had any problem after that for several months now.
Two builds actually, 25120.1010 and 25193 with autopilot error. 😉
As you said, it does work with 25309
-
Anonymous
2023-03-07T06:48:13+00:00 This command only failed with one specific Build, but I don' remember which one it was, never had any problem after that for several months now.
Two builds actually, 25120.1010 and 25193 with autopilot error. 😉
As you said, it does work with 25309
He's showing a specific message "OOBE not found". I don't remember seeing that one. 😎