Windows 11 BypassNRO used to be one of the easiest ways to complete setup without connecting to the internet or signing in with a Microsoft account. That changed when Microsoft began removing the old bypassnro.cmd script from newer Windows 11 builds.
The important point in 2026 is this:
The classic OOBE\BYPASSNRO command is no longer dependable on every Windows 11 installation.
Microsoft announced in March 2025 that it was removing the bypassnro.cmd script from newer Insider builds so users would complete setup with internet connectivity and a Microsoft account.
That does not mean every existing Windows 11 ISO suddenly behaves the same way. Setup behavior depends on the Windows build, installation media, and updates included with that media.
So before following an older tutorial, identify what your current Windows 11 installer actually supports.
Quick Answer
If you are at Windows 11 setup and want to create a local account:
- Try
Shift + F10to open Command Prompt. - On some laptops, use
Shift + Fn + F10. - If your build still recognizes
OOBE\BYPASSNRO, the classic method may work. - If the command is not recognized, do not keep repeating it.
- On some current Windows 11 setups,
start ms-cxh:localonlycan still open the local-account creation flow. - These workarounds are not guaranteed to remain available because Microsoft continues changing OOBE.
If you can complete setup normally with a Microsoft account, you can also switch to a local account afterward from Windows Settings.
What Is BypassNRO?
BypassNRO is associated with the Windows Out-of-Box Experience, commonly called OOBE.
OOBE is the setup process you see after installing or resetting Windows. It handles items such as:
- region
- keyboard
- network
- user account
- privacy settings
- device naming
For several Windows 11 releases, the command:
OOBE\BYPASSNROcould restart setup and expose an offline path that allowed the user to continue without an internet connection.
That method became popular because Windows 11 Home and many Windows 11 Pro setup paths increasingly encouraged or required Microsoft account sign-in.
Why the Old BypassNRO Method Is Less Reliable Now
Microsoft officially announced that it was removing the bypassnro.cmd script from newer Windows 11 Insider builds.
Microsoft said the change was intended to ensure that users leave Windows setup with internet connectivity and a Microsoft account.
That matters because many tutorials still present:
OOBE\BYPASSNROas though it works on every Windows 11 computer.
It does not.
You may still find installation media where the command works, especially older media. On newer media, Command Prompt may report that the command is not recognized.
Do not assume the computer is broken when that happens.
The setup files may simply no longer contain the old script.
Try the Classic BypassNRO Command Only Once
At the Windows setup screen:
- Press
Shift + F10. - If nothing happens, try
Shift + Fn + F10. - Enter:
OOBE\BYPASSNRO- Press Enter.
If the Command Works
Windows may restart.
After setup starts again, look for an option such as:
I don’t have internet
or another offline setup path.
The exact wording can vary.
If the Command Is Not Recognized
Stop there.
Do not spend time repeatedly entering the same command or assuming you typed it incorrectly.
Your Windows build may no longer include the old BypassNRO script.
Current Alternative: Local Account Setup Command
Recent Microsoft Q&A discussions in 2026 continue to show this command working on some current Windows 11 setups:
start ms-cxh:localonlyTo try it:
- Stay on the Windows setup screen.
- Press
Shift + F10. - On some laptops, use
Shift + Fn + F10. - Enter:
start ms-cxh:localonly- Press Enter.
If supported by that build, Windows may open a local account creation window.
Create the local account and continue setup.
Important Limitation
This is not something I would describe as a permanently supported Windows setup feature.
Microsoft has repeatedly changed OOBE behavior, so a workaround that functions on one Windows 11 build may disappear on another.
If the command no longer works on your installer, do not keep trying random commands from old tutorials.
What About the Registry Bypass?
Some Windows 11 builds have also responded to manually creating the BypassNRO registry value during setup.
The commonly used command is:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /ffollowed by:
shutdown /r /t 0This manually creates the value associated with the older BypassNRO behavior.
However, I would treat this as a build-dependent workaround, not a guaranteed Windows feature.
Microsoft can change how OOBE handles this value at any time.
If the setup process does not expose an offline option after restarting, use another approach rather than repeatedly editing setup values.
The Simplest Supported Alternative: Finish Setup and Switch Later
For many users, the least complicated route is:
- Complete Windows setup with a Microsoft account.
- Reach the Windows desktop.
- Open Settings.
- Go to Accounts > Your info.
- Choose Sign in with a local account instead.
- Follow the prompts.
Microsoft officially supports switching between Microsoft and local accounts after Windows is installed.
That means you do not necessarily need to fight with OOBE if your only goal is to use a local account for everyday Windows sign-in.
If you already finished setup and want to change account types, see my How to Remove a Microsoft Account From Windows 11 guide.
Local Account vs Microsoft Account
A local account exists only on that Windows device.
A Microsoft account connects Windows sign-in with Microsoft’s online services.
Microsoft currently explains the difference this way:
Local Account
- specific to one device
- does not require internet access to sign in
- not automatically connected to Microsoft cloud services
- settings and files stay associated with that device unless you connect other services separately
Microsoft Account
- can be used across multiple Microsoft services
- integrates with OneDrive and Microsoft Store
- can synchronize settings and data
- provides additional account recovery and cloud-connected features
Microsoft recommends using a Microsoft account, but Windows still supports local accounts after setup.
What If Shift + F10 Does Not Work?
Some laptops use the function keys for brightness, volume, and other hardware controls.
Try:
Shift + Fn + F10Also try using the built-in laptop keyboard rather than a wireless keyboard that may not yet be fully initialized during setup.
If Command Prompt still will not open, avoid repeatedly forcing the computer off unless setup itself has frozen.
What If BypassNRO Works but Windows Hangs Afterward?
There have been reports on newer Windows 11 builds where offline OOBE completes but the first sign-in process takes unusually long or appears stuck.
That can happen because Windows setup still attempts to initialize cloud-connected services while the computer is offline.
If the system eventually reaches the desktop, connect it to the internet afterward and allow Windows Update and Microsoft Store components to initialize normally.
If setup genuinely freezes, restart once and check whether Windows resumes the account setup process.
Do not repeatedly hard-power the computer off during OOBE unless it is completely unresponsive.
Does BypassNRO Affect Windows Activation?
BypassNRO itself does not activate Windows and does not replace a Windows license.
Activation is separate from the account creation process.
A PC that already has a valid digital license can normally activate after Windows is installed and connected to the internet, provided the correct Windows edition is installed.
A local account does not automatically invalidate Windows activation.
Can You Add a Microsoft Account Later?
Yes.
Open:
Settings > Accounts > Your info
Then choose:
Sign in with a Microsoft account instead
Microsoft officially supports switching from a local account to a Microsoft account without reinstalling Windows.
Can You Switch Back to a Local Account Later?
Yes.
Windows also supports switching from a Microsoft account to a local account after setup.
Open:
Settings > Accounts > Your info
Choose:
Sign in with a local account instead
Create the local username and password, then complete the sign-out process.
Should You Use Rufus to Avoid the Microsoft Account Requirement?
Rufus can create customized Windows installation media and has offered options that modify parts of the Windows setup experience.
That can be useful for experienced users creating installation media.
However, it adds another variable to the installation process.
For a normal consumer PC, I prefer this order:
- Try the setup options already available in your Windows build.
- If appropriate, test the current local-account command.
- Complete setup normally and switch to a local account afterward if necessary.
- Use customized installation media only when you understand the changes being applied.
Do Not Rely on Windows Version Numbers Alone
One weakness in many BypassNRO tutorials is that they say something like:
- 22H2 works
- 23H2 works
- 24H2 sometimes works
- 25H2 does not work
That is too simplistic.
Two computers showing the same marketing version can still use installation media with different cumulative updates and OOBE components.
A better rule is:
Test what your actual installer supports.
If OOBE\BYPASSNRO is missing, move on rather than assuming every installation of that Windows version must behave the same way.
Avoid These Common Mistakes
Following Old Tutorials Without Checking the Date
Windows OOBE changes frequently.
Instructions from 2023 or 2024 may no longer match a 2026 installer.
Repeating a Removed Command
When Windows says OOBE\BYPASSNRO is not recognized, repeating it will not restore the missing script.
Assuming a Local Account Disables Windows Update
A local Windows account can still receive Windows updates.
Account type and Windows Update are separate issues.
Confusing Account Setup With Activation
Skipping Microsoft account sign-in does not bypass Windows licensing.
Using Random Registry Commands
Only change the specific value you understand.
Do not import unknown .reg files or scripts from download sites during Windows setup.
What I Recommend in 2026
Treat BypassNRO as a changing Windows setup workaround rather than a permanent feature.
If the classic command works on your installer, you can use it.
If it does not, current Windows 11 builds may still respond to the local account setup command:
start ms-cxh:localonlyBut even that can change as Microsoft updates OOBE.
For users who simply want a local Windows account and do not need offline setup, completing installation normally and switching account types afterward is the most predictable long-term method.
That keeps the process simple and avoids depending on a workaround Microsoft may remove in a later build.


