We’re removing the bypassnro.cmd script from the build to enhance security and user experience of Windows 11. This change ensures that all users exit
[See the full post at: Removing bypassnro]
Susan Bradley Patch Lady/Prudent patcher
![]() |
There are isolated problems with current patches, but they are well-known and documented on this site. |
SIGN IN | Not a member? | REGISTER | PLUS MEMBERSHIP |
Home » Forums » Newsletter and Homepage topics » Removing bypassnro
We’re removing the bypassnro.cmd script from the build to enhance security and user experience of Windows 11. This change ensures that all users exit
[See the full post at: Removing bypassnro]
Susan Bradley Patch Lady/Prudent patcher
I got into the Feedback Hub and upvoted this feedback.
Ok here’s a question. If one is upgrading from win10 pro with a local account, will the local account be “honored” by win11 at upgrade or will one have to log onto a Microsoft account?
You can use Rufus setup to bypass the MS account and set up a local account directly, I believe. If installing W11 Pro, you can designate the device is for work and elect to join a domain and then set up the local account. That said, Microsoft is really becoming insufferable in the cr$p they are trying to force on users to engineer a growth rate for Azure in their quarterly reports. That, and their desire to use the OS as an adverting billboard is getting exceedingly unprofessional IMHO. I consider my comment an observation rather than a rant.
Susan, why upgrade W10 to W11 23H2 instead of 24H2 with Rufus ?
Susan doesn’t currently recommend installing 24H2 for Windows 11, only 23H2. Therefore, for those who want to move from Windows 10 to Windows 11, 23H2 is the current version to migrate to.
She currently only recommends Windows 11 24H2 if you’re buying a new machine with Windows 11 already installed on it.
Thanks Bob99. The reason I asked is, I have 4 Windows machines. One with W11 pro 23H2, and three old laptops under Windows 10 without TPM 2.0. It pains me to get rid of 3 good machines that I use mainly for surfing and text editing. So I want to use Rufus to upgrade one of the three to W11, but I don’t want to go through that procedure twice, which I would have to do eventually if I first install 23H2. So I’ll take my chance with 24H2. As for the other 2 Windows 10 machines, I might try 0Patch when the time comes.
It is my understanding that this “bypassnro” needs to be used for ALL Windows 11 installations not just Home to be allowed to set up a Local Account, No?
I’m expecting my new computer build next week with Windows 11 Pro 24H2. Maingear (the builder) will probably be loading whatever they currently have sometime this week. When will this announcement take affect?
For those still successfully being able to use the “bypassnro” for a Local Account, does this mean MS is planning on “force implementing” this on all of us in future updates?
IF forced into an initial MS Account at setup, will we still be able to switch to a Local Account after the fact?
When will this announcement take affect?
To Quote Susan’s Post:
Today, Microsoft announced that the Windows 11 Insider Build (26200.5516) had been released to the Dev channel. The nugget quoted above is mentioned in that Windows Blog post.
I think that means it is a part of the insider build, but I could be wrong!
It is my understanding that this “bypassnro” needs to be used for ALL Windows 11 installations not just Home to be allowed to set up a Local Account, No?
I’m expecting my new computer build next week with Windows 11 Pro 24H2. Maingear (the builder) will probably be loading whatever they currently have sometime this week. When will this announcement take affect?
For those still successfully being able to use the “bypassnro” for a Local Account, does this mean MS is planning on “force implementing” this on all of us in future updates?
IF forced into an initial MS Account at setup, will we still be able to switch to a Local Account after the fact?
No, it’s only required on Home. On the others, use the “Domain join instead” option in the “sign-in options” link, even if you don’t plan to join it to a domain. That will create a local account.
https://learn.microsoft.com/en-us/windows-insider/flighting
Developer channel is the earliest/most raw of all of their releases.
Susan Bradley Patch Lady/Prudent patcher
Windows was originally an OS that could be installed on one’s PC – which meant a Personal Computer. Other choices were OS2, DOS, CPM, etc.
If I can’t install an OS on my computer without a connection to the web nor without an account with the maker of that OS, then it is no longer my Personal Computer. It becomes, in effect, the OS maker’s computer.
Google, Apple and now Microsoft (post-Windows 7) have all usurped foundational control of our personal tech. I believe it is less about “security and user experience” and more about the surveillance economy and increased revenue streams.
Hopefully, Linux (and maybe some other fringe OS’s) will keep some semblance of the Personal Computer a reality.
Win10 Pro x64 22H2, Win10 Home 22H2, Linux Mint + a cat with 'tortitude'.
This sort of flies in the face of Microsoft’s own marketing, see 7 common myths about Windows 11:
Myth 2: You need a Microsoft account to use Windows 11
While having a Microsoft account can enhance your experience, you can still use Windows 11 with a local account if you prefer.
Looks this like this myth is about to become legend!
Note: I am mincing words a bit because it says use not setup.
Personal note:
Past experimentation has shown that with a local administrator account it is possible to go to Settings > Accounts and select “Sign in with a Microsoft account instead”. Later I was able to remove that again in Settings. So even if you were to have to use a Microsoft account during setup, I believe you should be able to convert the account back into a local account by removing the email address in settings.
When you use a Microsoft account for signing in, your online Microsoft account will list your computer in Devices. When changed back to a local account, it may say “We don’t see any devices” like mine does at moment.
Also, when local account user signs into the Microsoft Store to download an app with in-app purchases that requires it, the login is remembered separately by the Microsoft Store but also can be removed. Aw shucks, in my case there are no payment options available! Too bad…
That said, if the Microsoft account is used to login does not have administrator privileges on the computer, various things in Settings > Accounts will fail. In particular, when I tried that on a test system OneDrive failed because it could not login.
Hey Y’all,
I just made a copy of it to my network drive and took a look. Pretty simple.
@echo off reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f shutdown /r /t 0
You could just type those two commands into the Command Window yourself. Or save the file to a USB drive and run it from there.
Note: they didn’t say they were removing the functionality just the file!
Does this bother you? If so, it’s time to get into that feedback hub and make your voice heard. Unfortunately, you may not be able to do so, at least for the moment. Use this link, which will prompt you to open the Feedback Hub app on your PC and sign in. Microsoft may tell you that “Your account doesn’t have access to this feedback.” That happened to me on a 23H2 PC, but I was able to get there on a PC running 24H2.
That feedback was submitted by an Insider account so it’s not accessible by any non-Insider accounts:
Feedback Hub – Insider and non-Insider accounts cannot see each other’s topics
It’s been that way for more than nine years.
(P.S. Is it ironic that submitting feedback complaining about requiring a Microsoft account requires a Microsoft account?)
No, I was on a 23H2 and it said that this build no longer had the ability to provide feedback and I needed to upgrade.
That’s not what “Your account doesn’t have access to this feedback” means.
It had nothing to do with insider as I used my insider credentials.
I’ve tested and your feedback at aka.ms/AAva3jg is only available after signing in to Feedback Hub as an Insider.
The feedback mentioned in the first reply here at aka.ms/AAvabey is only available after signing in to Feedback Hub as a non-Insider.
They have both now been added to a collection titled “Do not remove bypassnro.cmd script from Windows 11 OOBE”. But access still requires using the correct Insider or non-Insider link and corresponding account.
You still aren’t understanding. I went to go start a new feedback item on my 23H2 and it indicated that I could not do so. I tried both non insider and insider and it indicated that 23H2 couldn’t provide feedback. I had to log into a 24H2 and then with my insider credentials in order to open a feedback item.
With my 23H2 firm machine with my non insider Microsoft account it would not let me open up a feedback item.
Susan Bradley Patch Lady/Prudent patcher
Here’s how to run the BYPASSNRO.exe from your install USB:
1. Copy BYPASSNRO.exe to you prepared installation USB disk.
From where? Did you mean BYPASSNRO.cmd?
b,
YES! i is .cmd sorry for the Brain Fart!
AH HA – just removed the script/batch file, did not remove the impact of the registry key. Scroll down this Will Dormann post and the responses.
Will Dormann: “Upcoming Windows 11 builds won…” – Infosec Exchange
“..turns out that yes, the registry entry that the script sets still works – they just removed the script lol”
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
@wdormann @ajn142 I mod my install media to have this inserted, as it skips the need for a reboot during OOBE.
Write-Host "Set BypassNRO" -ForegroundColor Cyan
& reg load HKLM\SOFT $workdir\Windows\System32\Config\Software
& reg add HKLM\SOFT\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
& reg unload HKLM\SOFT
Susan Bradley Patch Lady/Prudent patcher
Good work, Susan…but…
I have no doubt Microsoft monitors AskWoody and similar sites, and that as soon as work around are published, new fixes are being developed to disable them.
Microsoft won’t budge, no matter how much we petition to keep local accounts. They will force those (and other things) on users as long as they are a monopoly. If users don’t like that, the best option is to move to another OS.
Use Rufus and install 23H2
Rufus gives you the option to bypass creating a Microsoft account.
Wonder if Rufus uses BYPASSNRO
Wonder if Rufus uses BYPASSNRO
Apparently not:
Remove requirement for an online Microsoft account
This option sets the “BypassNRO” value to 1 in the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE registry key via an unattend.xml RunSynchronousCommand entry.
[source code analyzed by expert]
I mod my install media to have this inserted, as it skips the need for a reboot during OOBE.
Susan, please correct me if I’m wrong, but the bypass method being discussed by you and RG appears to be geared toward people who are some “install media” to set up 24H2 on an already-running machine. How would the same thing be done by someone who had just had their new PC delivered to their front step?
…How would the same thing be done by someone who had just had their new PC delivered to their front step?
My name’s not Susan, but I believe I have an answer for you.
In RG’s first post, he wrote
You could just type those two commands into the Command Window yourself.
So, once one gets to the point in the OOBE where they’d normally invoke the (possibly soon to be non-existent) script, they’d summon the command line by using the correct key sequence and enter the commands themselves, one at a time, hitting [Enter] after each one. The first command would add the registry key and the second one would then reboot the machine immediately upon hitting the [Enter] key. Once the machine reboots,
Installation will continue as expected with the “I don’t have Internet” prompt.
Thanks, @Bob99. So, just to make sure I understand, and also for the benefit of others reading this, when you say in your long paragraph to…
enter the commands themselves, one at a time, hitting [Enter] after each one
…the two commands are, first, “@echo off” and, second, the text that starts with “reg add” and ends with “shutdown /r /t 0” as offered by RG, right?
…the two commands are, first, “@echo off” and, second, the text that starts with “reg add” and ends with “shutdown /r /t 0” as offered by RG, right?
No, the first is;
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
and the second is;
shutdown /r /t 0
Being picky, but I assume the “first command line” (shown above as 3 lines probably due to display space limitations) would still be properly entered as 1 single line starting with “reg add”- correct?
Second command line – no problem, understood.
What happened to the “@echo off” line? Is that not needed? Is it actually the first part of the first command line? Or, should it the first line, and the others are 2nd & 3rd lines?
Being picky, but I assume the “first command line” (shown above as 3 lines probably due to display space limitations) would still be properly entered as 1 single line starting with “reg add”- correct?
Yes.
What happened to the “@echo off” line? Is that not needed?
Not needed (it just hides the commands when a script is run).
I think it is clear that Microsoft eventually wants everyone who uses Windows (Home, at least) to use a Microsoft account, and these little things show that it is moving in that direction. I can’t even setup Windows without access to the internet and a Microsoft account? No thanks.
I never used the Home version of Windows since Windows 8.1, and from what I can see the Home version of Windows has since become more and more crappy and rubbish.
I echo Donny H’s advice above :
Never use Windows Home, it is a worthless OS.
Yesterday morning my aunt came to my home and I helped her to “configure” a preinstalled Windows 11 Home on her “brand new” notebook with a Intel 13th generation CPU (two generations behind) as she has complained she can’t navigate around the “shiny new” interface. I installed Open Shell and configured Windows to present the old right click context menu for her. Also installed LibreOffice on her computer for her to try and use (instead of the “free” Microsoft 365 given to her as part of the purchase of the new computer). Didn’t do anything else as she needed to leave for work. I suppose she now has a Microsoft account although I am pretty sure she is not aware of it.
Hope for the best. Prepare for the worst.
.cmd files are actually batch scripts not programs and @RetiredGeek posted the full contents of BypassNRO.cmd in his above post #2758761.
As a simple solution in case Microsoft does decide to remove it, I copied my existing BypassNRO.cmd to an alternate location on my drive and renamed it BypassNRO.bat.
Just FYI,
.bat files were for the old DOS command.com
.cmd files are for the new cmd.exe.
And, while they both work in Windows 10 & 11, there are “some” differences in exactly how they function (CMD vs BAT | top 17 differences).
Disclaimer: I don’t use Bitlocker, don’t ever intend to use Bitlocker, and I disable it in Servicces, along with a few other things. I don’t need a MS account to recover a key.
In my experience, this method does not trigger Bitlocker encryption. To insure that Bitlocker stays off, I open Services.msc, scroll down to Bitlocker, right-click and select Properties, then set it to Disabled.
A very simple installation method is to use a fake email address
You can accomplish the same thing using a real MS account for installation purposes, then follow the instructions to delete that user account from your PC.
I usually create a new Standard user account, reboot, log into the Standard user account and do everything else from there, dealing with UAC as it occurs. This works with or without being connected to the internet.
It… “offers” to verify? I would think it would be very pushy in verifying, like not letting you proceed setup without a code.
This works with or without being connected to the internet.
mail.com is a legitimate email service. For that reason, Windows “offers” to verify, but one can click the “Not now” (or something similar, I forget the exact wording) and continue with installation.
By using
It may not be obvious to everyone that you’re advocating the (temporary) creation of a Microsoft account, not avoiding doing so.
A very simple installation method is to use a fake email address @mail.com for a new MS account.
How much plainer can I say that? Did you miss it?
Before starting, read the disclaimer.
Step #1 – Create a fake MS account.
Step #2 – Complete the installation of Windows.
Step #3 – Create a new local account in the Administrators group.
Step #4 – Reboot into the local account in the Administrators group.
Step #5 – Complete the OOBE for the new account, then delete the fake MS account.
I also advocate creating a local Standard user account for everyday use. Is that clear enough for you? “…use a fake email address @mail.com for a new MS account.”
This avoids trying to bring up a console and use console commands in order to use a local account. MS hasn’t deprecated using an MS account to install Windows. It just isn’t necessary to keep a MS account on one’s PC.
Annnnnd I’m out.
Yea but that’s probably going to trigger bitlocker. You need to add instructions to disable bitlocker.
In my experience, installing Windows 11 Pro, it doesn’t trigger Bitlocker encryption. After the first OOBE is finished, Bitlocker status looks like this:
But I’ll edit to add disabling the service.
Step #1 – Create a fake MS account.
…
then delete the fake MS account.
It’s not a fake MS account. It’s an actual MS account.
Calling it fake is why I think people may be confused.
For fresh device installations with a W10 activation token with or without W11 requirements, there’s nothing stopping 3rd party OS installation media creators including bypassnro registry files and bypassnro.cmd for pre-configuration into their process, which to me, equates to a much more hassle-free sensible option.
IOW, just look for those media creation utilities nearer the time when required, IF progress goes beyond ‘insider’ builds for Home Editions..
NOTE: Remember to create a W10 image prior to a 23H2 upgrade or a 24H2 regression 🙂
I figured this was coming eventually because it’s a terrible decision and Microsoft can’t help but make those.
I wonder when they’ll remove the option to create a local account entirely.
Personally I despise the idea that everything electronic must be identifiable and trackable. It’s a tool, it doesn’t need to know me and hold a conversation with me and report on me to a trillion-dollar master.
Here’s how to run the BYPASSNRO.exe from your install USB:
- Copy BYPASSNRO.exe to you prepared installation USB disk.
- Boot the computer from the USB disk and begin setup.
- When you get to the point where you need internet disconnect the internet and hit SHIFT+F10.
- Type: diskpart [Enter]
- Type: list disk [Enter]
- Note the disk number of the USB drive (this will be the smallest drive listed.
- Type: select disk # [Enter] where # is the info from previous command.
- Type: list volume [Enter]
- Note the letter of the desired partition.
- Type: Exit [Enter]
- Type: CD d: [Enter] where d: is the letter of the drive from above.
- Type: Bypassnro.exe [Enter]
- Installation will continue as expected with the “I don’t have Internet” prompt.
I hope you will post a detailled procedure on how to do that because for a non-geek, it
is unclear. When you say “bypassnro.exe”, did you mean “bypassnro.cmd” ?
If not, “bypassnro.exe” comes from where ?
Hi, RG:
Do you mean C:\\Windows\System32\OOBE for the location of BypassNRO.CMD ?
Mark
Mark,
You are correct. I’m getting too old too fast! I used to be able to edit my posts at any time but AW changes have robbed me of that capability.
So how long will this ‘new’ M/S SUDDEN change (and workarounds) last?? Thx to AW for letting us know, but this came out of nowhere, with no time to pivot. Disgusting really. So: how does a small island with few adept costly techs to deal with our win 10 pro data with local accounts only? I have no tech expertise other than here. Can’t keep up with changes. Where does that leave us?
Yes, as corrected above it is BypassNRO.CMD and it can currently be found in:
C:\Windows\oobe
Thanks but can you write a detailled procedure on how to do that.
Also you wrote ” BypassNRO.CMD” !
The capital letters are not the same as your original post. Can you be more precise please.
Thank you for your good work RetiredGeek
Yes, as corrected above it is BypassNRO.CMD and it can currently be found in:
C:\Windows\oobeThanks but can you write a detailled procedure on how to do that.
Also you wrote ” BypassNRO.CMD” !
The capital letters are not the same as your original post. Can you be more precise please.
Thank you for your good work RetiredGeek
There is no OOBE in the C:\windows directory !?
It makes me so mad that MS chooses to be user hostile
Microsoft is now to disable account password replaced by Passkeys
WinJS-Microsoft-Account-Bypass
This guide explains a method to bypass the Microsoft Account (MSA) requirement during the Windows 11 Out-Of-Box Experience (OOBE) by using the Developer Console to invoke a hidden local account setup screen. ..
1. Start Windows 11 Setup
Begin the Windows 11 Setup Process.
Select your region and keyboard layout.2. Stop at the Secondary Keyboard Layout Screen
When you reach the Secondary Keyboard Layout screen, do not click Skip.
If you accidentally skipped and reached the Network Setup Screen, don’t stress. I have a guide in the troubleshooting section.3. Open the Developer Console
Press Ctrl + Shift + J to open the Developer Console.
Your screen will go dark and will appear with a prompt (indicated by a > symbol) at the top left of the screen.
Note: If you can’t open the console, troubleshooting steps are below.4. Enter the Restart Command
Type the following command exactly as shown:
WinJS.Application.restart(“ms-cxh://LOCALONLY”)
Note: This command is case-sensitive. You can use Tab-completion to help:After typing WinJS.A, press Tab to auto-complete Application.
After typing res, press Tab to auto-complete restart.5. Exit the Developer Console
After entering the command, press Enter to execute it.
Press Escape to exit the Developer Console and return to the OOBE interface.
Note: If the Escape key doesn’t close the Console, click anywhere on the screen to ensure the console is focused and then press the key again.6. Local Account Setup
The Secondary Keyboard Layout screen will refresh, and a Windows 10-style local account setup screen will appear.
Enter your desired username, password, and security questions and click Next.7. Complete the Setup
The Setup will go black and will then log you in to your newly created account. Allow Windows 11 a few moments to configure the user.
Continue with the remaining privacy setting prompts.
Once finished, you will have successfully created a local account in Windows 11…
That’s a need that any OEM or company needs in order to script their custom installs.
Susan Bradley Patch Lady/Prudent patcher
Just another reason to ditch Windows.
When your OS manufacturer is fighting against you, you’re using the wrong OS.
There is no OOBE in the C:\windows directory !?
The default location for a standard Windows installation is C:\Windows\System32\oobe
You can also copy/paste the following into Notepad and then save it as BypassNRO.cmd
@echo off reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f shutdown /r /t 0
Note: the above is the actual contents of the BypassNRO.cmd file as it currently exists.
Never use Windows Home, it is a worthless OS.
Sure, we all have our reasons to be disgusted with Microsoft and WinOSs’ but had I followed that quote in 2004 I would never have entered the World Wide Web and learned much and enjoyed the sights and sounds through the years.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Welcome to our unique respite from the madness.
It's easy to post questions about Windows 11, Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Questions? Contact Customer Support.
Want to Advertise in the free newsletter? How about a gift subscription in honor of a birthday? Send an email to sb@askwoody.com to ask how.
Mastodon profile for DefConPatch
Mastodon profile for AskWoody
Home • About • FAQ • Posts & Privacy • Forums • My Account
Register • Free Newsletter • Plus Membership • Gift Certificates • MS-DEFCON Alerts
Copyright ©2004-2025 by AskWoody Tech LLC. All Rights Reserved.