Set up Windows 11 without internet - oobe\bypassnro

Anonymous
2022-05-15T21:52:40+00:00

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.

0 comments

143 answers

Sort by: Newest
Most helpful Newest Oldest
  1. 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. 😎

    Image

    oobe\msoobe.exe /bypassnro

    Image

    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. 🤷‍♂️

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-04-20T04:32:35+00:00

    New PC setup did not have OOBE in the root of system32 - if it's not there try:

    Maybe the OEM or MS (if this is a Surface device) removed it.

    oobe\bypassnro is still working as usual from the default location C:\Windows\System32 in both builds released today (23440 & 25346).

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. 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?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-04-20T00:05:42+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 :)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2023-03-22T23:27:52+00:00

    This method is still working with build 23419 👍

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments