Hey fg, Sibro,
Appears with todays Dev build 25197 total offline clean install is working with oobe bypass again.
Have a great weekend guys.
Regards,
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: Newest
-
Anonymous
2022-09-06T02:07:34+00:00 btw, for you information and others, official build 25179 ISO expires on 9/15. It shows a warning upon first boot and keeps nagging users a few times per hour. We need a new official Dev ISO asap.
Yes, I see that it only has a few days left on 25179, while 25193 has till Sept 2023. 🤣
Got this again on second and third try, after installing 25179 and W.U. to 25193 🤣
Then it stopped doing it on any subsequent "Open file location" attempts.🤷♂️
W.U. kept repeating these same 3 messages on every check, then cleared by closing and reopening Windows Update. 🤣
-
Anonymous
2022-09-05T20:07:34+00:00 I don't think loading the Wi-Fi drivers will help in that specific situation unless you connect the network before issuing the oobe\bypassnro, assuming it reconnects after it restarts. 😉
Hi fg,
I'm sure you're right, that is one of the reasons why I didn't bothered to try.
Besides, I'm way past that point. I used a clean install of 25179 official ISO and then performed an in-place upgrade with 25193 from UUPdump. I was having some weird issues with extra features being installed silently but it turned out to be my own mistake. I restored the previous build, fixed the problems and upgraded to 25193 via WU, no issues.
btw, for you information and others, official build 25179 ISO expires on 9/15. It shows a warning upon first boot and keeps nagging users a few times per hour. We need a new official Dev ISO asap.
-
Anonymous
2022-09-05T19:44:30+00:00 Thank you both for checking and confirming.
Windows 11 doesn't have native drivers for my wi-fi adapter so I can't test the workaround but good to know there's one. I could load the drivers and test it but not worth it.
Hi Sibro,
I don't think loading the Wi-Fi drivers will help in that specific situation unless you connect the network before issuing the oobe\bypassnro, assuming it reconnects after it restarts. 😉
Keep in mind that after the "AUTOPILOTUPDATE" error message it did not offer the option to connect Wi-Fi, I just connected the Ethernet cable and hit "Try again" to get over that error page, after that I disconnected the cable and went on with the offline installation.
We'll see if MS is coming up with a fix in future Builds or the next MS official ISO. 😎
-
Anonymous
2022-09-05T14:25:01+00:00 Thank you both for checking and confirming.
Windows 11 doesn't have native drivers for my wi-fi adapter so I can't test the workaround but good to know there's one. I could load the drivers and test it but not worth it.