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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-05-11T16:44:13+00:00

    Works just fine using ISO of Canary 25357.1 even in a non-compliant virtual machine. You must be doing something wrong.

    Confirmed, same here. 👍

    Was this answer helpful?

    2 people found 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-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
  4. Johnny55 5,155 Reputation points Volunteer Moderator
    2023-03-07T20:48:16+00:00

    Opening a prompt (which I needed to create a RAID0 volume during setup with diskpart) was not able to locate OOBE in Windows/System32. This command is no longer available and it would help future users to take the answers here with a grain of salt. What might've worked for you is not garanteed to work with others.

    .

    I wonder if this is somehow related to using a RAID setup. I didn't think anyone used that anymore with SSD and NVme drives. Is it possible that the OOBE folder is in another location. It's been decades since I looked at RAID. This could be a factor.

    It also appears you may be entering the oobe\bypassnro command too soon. You need to wait till you get to one of the graphic setup screens, then type shift F10 to bring up command prompt. Just a wild guess as I have not touched RAID.

    Hope this helps.

    Regards,

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more