Tuesday, October 7th 2025

Microsoft Blocks Online Account Bypass on Windows 11

Microsoft has released its latest Windows 11 Insider Preview Build 26220.6772 (KB5065797) in the Dev Channel. While it introduces some new Copilot-powered features and updates to Windows Hello, it also rings a death sentence to bypassing Microsoft Online Account, which is now mandatory for everyone. Microsoft has doubled-down on making users sign in with their Microsoft Online Account, and local-only installations are no longer possible at the time of writing. Although new workarounds will likely emerge over time, Microsoft has successfully closed off the most accessible and widely known methods for avoiding Microsoft account creation in recent Windows 11 preview releases. Since these changes currently exist only in preview versions, several weeks will probably pass before they reach the stable, public releases of Windows 11. The latest Windows Blog confirms:
MicrosoftWe are removing known mechanisms for creating a local account in the Windows Setup experience (OOBE). While these mechanisms were often used to bypass Microsoft account setup, they also inadvertently skip critical setup screens, potentially causing users to exit OOBE with a device that is not fully configured for use. Users will need to complete OOBE with internet and a Microsoft account, to ensure device is setup correctly.
Microsoft has made it clear that Windows 11 installation requires both a Microsoft account and active internet connectivity, and the company is systematically eliminating the simpler workarounds that previously allowed users to skip this requirement. While alternative methods remain available, they now demand significantly more technical expertise, specifically requiring users to modify the Windows installation image beforehand by configuring an unattended setup that includes a local account, a process that proves challenging for average users. Commands like "oobe/bypassnro" and the starting "ms-cxh:localonly" will not give you the desired workaround, as Microsoft has patched that as well.
Sources: Windows Central, Windows Blog
Add your own comment

184 Comments on Microsoft Blocks Online Account Bypass on Windows 11

#151
lexluthermiester
AndyGawgI tried Rufus for local account, Win 11 25H2. But while it installed and activated fine - it was an online MS account. Had to do the usual online account setup.

I am pretty sure I did everything correctly, but there was no avoiding the setup of an online account. I guess, although can't say 100% that the latest Win 11, even with Rufus blocks local accounts at setup.

I went on to create a local account later. Not ideal though. I am not going into any detail, the whole thing really pissed me off. Back on a local W10 and all is fine.
You were connected to the internet. The online account can not be created without internet.
You have two options at this point;
A: Wipe your drive, disconnect from the internet and reinstall Windows.
B: Create a local account in the Account manager, login to it and delete the ms account.
Posted on Reply
#152
Tomorrow
AndyGawgIt was Pro.
Shouldn't the fake domain join trick still work to create local account on Pro?
At the account creation screen select that you want to join domain. Then enter some random bs. It should error out and let you create local account anyway.
Posted on Reply
#153
Knight47
A Computer GuyIt didn't work for me anymore using rufus and the new 25H2 to allow me to make local account even when network was disconnected however I think found a corner case. I managed to bork my Windows 10 install today (that only ever used local account not MS account) either by installing another GPU or UEFI update (not sure which broke it) and it caused Windows to deactivate but I didn't find out until later as it didn't put up the usual watermark. I couldn't get it activated again even with the troubleshooter - then got pissed and wiped the drive to install Linux but I decided to see what Windows 11 would do for science.

Unfortunately I didn't have the Windows 10 OEM key I used for that motherboard anywhere, because I thought it was always going to be tied to the motherboard and I would never have to remember it, but I grabbed the BackupProductKeyDefault out of the system (which is different than the original product key) and used that when Windows 11 installed and it worked. The rufus prepared USB stick that was setup to create a local account by default worked and I didn't get stuck at the screen prompting me to login to an MS account. Regarding windows activation however it seems the backup key didn't work and Windows wouldn't activate.
I downloaded 25H2 in October 30 and that ISO works fine with offline account creation, I use Pro too. I did not have internet during setup and Installed Win11 a bunch on times on my main X670E and B850 testbench.
I might try with a fresh Win11 iso tomorrow when I have time.
Posted on Reply
#154
AndyGawg
lexluthermiesterYou were connected to the internet. The online account can not be created without internet.
You have two options at this point;
A: Wipe your drive, disconnect from the internet and reinstall Windows.
B: Create a local account in the Account manager, login to it and delete the ms account.
Yeah you are right, I was connected.

Option B is what I did, successfully. But coming from my highly modified, no edge no Store highly tweaked W10 pro it was trash.
I couldn't stand it. I did give it 2 weeks and probably well over 30 hours. Bit long in the tooth to rage quit.

Thing is it's plain awful. I am back on my W10 pro. Safe from Malware (MS patches, MS A.I. MS anything.) It made me realize how good a properly tweaked W10pro is. The last 10 hours I tried tweaking W11 local account expecting to get it to at least match W10. Granted, 10 hours is nothing, but W11 is locked down pretty hard in terms of sending telemetry among many other things.

Finally I will point out this was my third go at W11pro. 1st was 6 months after release. Tried again 18 months ago. It seemed worse. Tried again over the course of a few weeks in Nov 2025 with 25H2.
It's sickening. I'll never try a fourth time. W10 pro for at least a year, then Linux.

For folks who just use their PCs/Laptops for mail, browsing and a few other things I guess it seems OK. Folks on this forum know (or should) all that goes on in the background. I don't even consider W11 a safe piece of Software. It's by no means worthy of being called an OS. It's garbage.

I'll also point out this is my take, after giving it a good few try outs. Not all will agree with my absolute conclusion that W11 is junkware. I speak for myself. I suspect quite a few with knowledge about how awful and potentially dangerous bunch of code in terms of security, W11 is - and getting worse all the time, will at least partly agree.

Windows 10 had major security issues ironed out years ago. It's not perfect of course, but safe with sensible user practice. W11 has been around for four years or so. But especially in the past year it goes backwards in terms of security. Not to mention using it is just awful. Seems it wants to use itself, user be damned. Well MS and W11 be damned!
TomorrowShouldn't the fake domain join trick still work to create local account on Pro?
At the account creation screen select that you want to join domain. Then enter some random bs. It should error out and let you create local account anyway.
Yes, you are right too as are other posts. Firstly I was online. That was careless. And dumb, I admit.

Thing is after creating a working Local account as detailed above, and by Lexluthermiester, I still found it detestable.

So for me regardless of it being an online account, or a local account, W11 is an example of very bad programming, and only getting worse. I wish that were not the case.
Posted on Reply
#155
lexluthermiester
AndyGawgYeah you are right, I was connected.
Never allow an internet connection during Windows setup. It has the potential for many problems, including the one you encountered.
AndyGawgThe last 10 hours I tried tweaking W11 local account expecting to get it to at least match W10. Granted, 10 hours is nothing, but W11 is locked down pretty hard in terms of sending telemetry among many other things.
You should take a look at the following.
schneegans.de/windows/unattend-generator/
This is one of the best ways to debloat and trim down Windows 11, including telemetry.
Posted on Reply
#156
Knight47
Knight47I downloaded 25H2 in October 30 and that ISO works fine with offline account creation, I use Pro too. I did not have internet during setup and Installed Win11 a bunch on times on my main X670E and B850 testbench.
I might try with a fresh Win11 iso tomorrow when I have time.
So I downloaded 25H2 from MS and used rufus


I downloaded the ISO twice and created two different USB installers just to be sure. I do not have internet during install(because it will mess things up) and it automatically created local accounts for me.
Posted on Reply
#157
AndyGawg
lexluthermiesterNever allow an internet connection during Windows setup. It has the potential for many problems, including the one you encountered.


You should take a look at the following.
schneegans.de/windows/unattend-generator/
This is one of the best ways to debloat and trim down Windows 11, including telemetry.
Hey, thanks for the link!

BTW: I am now 100% sure why It went to online account. (Internet connected) Thanks to you, and everybody for the advice.
Posted on Reply
#158
NesteaZen
? did something happen? seems like [iCODE]start ms-cxh:localonly[/iCODE] is back on the menu. ?

Posted on Reply
#159
CrAsHnBuRnXp
NesteaZen? did something happen? seems like [ICODE]start ms-cxh:localonly[/ICODE] is back on the menu. ?

Do we know what version hes running? Could be an older ISO that still has this functionality.
Posted on Reply
#160
Darmok N Jalad
Knowing Microsoft, they probably screwed up when it went away, and screwed up when it comes back again.
Posted on Reply
#161
lexluthermiester
CrAsHnBuRnXpDo we know what version hes running? Could be an older ISO that still has this functionality.
That information is shown at time index 9:58. 10.0.2610.1742 is 24H2. In that version, all the bypasses still work.
NesteaZen? did something happen? seems like [ICODE]start ms-cxh:localonly[/ICODE] is back on the menu. ?

That video shows an older version and does not apply to the current release subject of this article.
Posted on Reply
#162
CrAsHnBuRnXp
lexluthermiesterThat information is shown at time index 9:58. 10.0.2610.1742 is 24H2. In that version, all the bypasses still work.
So then of course this bypass is still going to work. @NesteaZen
Posted on Reply
#163
AleXXX666
CrAsHnBuRnXpSo then of course this bypass is still going to work. @NesteaZen
25H2 with disconnected internet creates local still perfectly;)
Posted on Reply
#164
AndyGawg
I forgot to update this thread. On June 1st 2026 I successfully installed with Rufus, a local account directly. Worked perfectly first time.
Thanks again to Lex who was the first one to point out that It had failed previously because I didn't disconnect temporarily. Spot on, that literally was the reason, the only reason.


Still working fine. Got the H26H2 enablement package (not that it does much beyond extending support - so far.)

With a few GPO changes, and some other tweaks Windows 11 isn't as frustrating as standard install.

To AleXXX post above. Yes. I used the latest image as of (June 1st 2026) which of course was 25H2.

The guy who makes Rufus is a saint! 👍
His intuitve setup program works great (except for technically challenged like me, who didn't bother to disconnect from the interenet the first time. :banghead: )

I used vs 4.14, it was updated to 4.15 a little while back. Probably everyone knows that as it was mentioned (I think?) on this site.

Be interesting to hear to experience/outcome of anyone who uses the latest Rufus for local account only with 26H2 - I guess it would still work as the core files are the same as 25H2 and 24Hx I read?
Posted on Reply
#165
Vayra86
24H2 guys... anything newer is a shitshow in varying states of Copilot integration and other MS funny business. Not that 24H2 is completely clean, but it did get made before this AI nonsense got real.
Posted on Reply
#166
vgm
Isn't 25/26H2 is based on 24H2 with few features enabled via enablement package except 26H1 which is exclusive for new SoC for Qcomm, NVIDIA.
Posted on Reply
#167
Unregistered
Vayra8624H2 guys... anything newer is a shitshow in varying states of Copilot integration and other MS funny business. Not that 24H2 is completely clean, but it did get made before this AI nonsense got real.
I cleaned up my version of 24H2 and I’m running just fine on my local account. Looks like I’m gonna be staying on 24H2 for quite some time.
#168
lexluthermiester
Vayra8624H2 guys... anything newer is a shitshow in varying states of Copilot integration and other MS funny business. Not that 24H2 is completely clean, but it did get made before this AI nonsense got real.
To be fair, the LTSC IOT version of 26H2 is fairly solid. Been testing all of them for a few days, LTSC IOT is lacking all of microsoft's normal nonsense.
Posted on Reply
#169
GeoffreyA
lexluthermiesterTo be fair, the LTSC IOT version of 26H2 is fairly solid. Been testing all of them for a few days, LTSC IOT is lacking all of microsoft's normal nonsense.
Can vouch for this. No problems with 26100.9550.
Posted on Reply
#170
AleXXX666
lexluthermiesterTo be fair, the LTSC IOT version of 26H2 is fairly solid. Been testing all of them for a few days, LTSC IOT is lacking all of microsoft's normal nonsense.
why I can't find the source of 26H2 LTSC proofing it exists?
GeoffreyACan vouch for this. No problems with 26100.9550.
yours is 24H2, while lexluthermiester claims of 26H2 LTSC:confused:
Posted on Reply
#171
lexluthermiester
AleXXX666why I can't find the source of 26H2 LTSC proofing it exists?
Maybe you're not looking in the right place? What do you want, a screenshot?

EDIT; ScreenShot for your viewing pleasure. Seems it's just Enterprise IoT, not LTSC. Still, I don't care about the differences as IoT is still massively debloated from the normal versions.
Posted on Reply
#172
GeoffreyA
AleXXX666yours is 24H2
Yes, mine is 24H2. I thought Lex was referring to IoT LTSC 24H2 updated to Build 9550. I'm all right with how things are and will install a fresh copy when a new LTSC comes out next year, hopefully.
Posted on Reply
#173
AleXXX666
lexluthermiesterMaybe you're not looking in the right place? What do you want, a screenshot?

EDIT; ScreenShot for your viewing pleasure. Seems it's just Enterprise IoT, not LTSC. Still, I don't care about the differences as IoT is still massively debloated from the normal versions.
ltsc is "more debloated" still. but I'm curious about testing that new 26H2 IoT :)
Posted on Reply
#174
Vayra86
lexluthermiesterMaybe you're not looking in the right place? What do you want, a screenshot?

EDIT; ScreenShot for your viewing pleasure. Seems it's just Enterprise IoT, not LTSC. Still, I don't care about the differences as IoT is still massively debloated from the normal versions.
This still likely includes a lot of packages you don't want AND more importantly, the install isn't in support for 8+ years.
Posted on Reply
#175
lexluthermiester
Vayra86This still likely includes a lot of packages you don't want
It doesn't have anything that isn't easily removed as a part of my debloating and customizing routine. Defender was the most difficult to remove, but I discovered a way around that.
Vayra86the install isn't in support for 8+ years.
Not really concerned about that one.
Posted on Reply
Add your own comment
Nov 19th, 2026 00:18 PST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts