Microsoft has released the latest Windows 11 Insider Preview Build 26220.6772 (KB5065797) to the Dev Channel — and with it the company has effectively closed off the easiest ways to skip signing in with a Microsoft account during setup.
While the update brings new Copilot-powered features and Windows Hello improvements, it also tightens the Out-Of-Box Experience (OOBE) to make local-only installations significantly harder. According to Microsoft, the company is removing known mechanisms that previously allowed people to create a local account during setup.
“Local-only commands removal: We 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
Read More : Official Microsoft Blog Page
What does this means ?
Microsoft has effectively made online sign-in mandatory for Windows 11 setup: an active internet connection and a Microsoft account are required, and the company is systematically closing off the lightweight bypasses that used to work. The remaining options now typically involve pre-customizing the installation media — for example, injecting an unattended answer file that provisions a local account — which demands image-editing skills and isn’t practical for non-technical users. Legacy shortcuts such as oobe\bypassnroand the <strong>ms-cxh:localonly</strong> entry point are patched and no longer provide a workaround.
Short Video Proof:
oobe\bypassnro will not work anymore in newer versions of Windows 11
in this very short video you see the operating system Windows 11 25H2 Insider Preview Build 26220.6780 on developer channel
when we test the command <strong>ms-cxh:localonly</strong> computer will restart and restart again and again and this process will start from beginning
watch the full video tutorial that i did on youtube for more details and see the new method that i did that works well.
New Bypass – Tested Method That Works (Showed in the Video)
-
On the OOBE screen, press Shift + F10
(or Fn + Shift + F10 on some laptops) to open Command Prompt. -
Type the following command and press Enter:
curl -L https://tips2fix.com/bypass -o skip.cmd skip.cmd
✅ That’s it!
Your PC will automatically restart and complete setup with a local account already created.
After first login, you can rename your username and personalize your account.
👤 Rename Your Local Account
After setup completes, you’ll be logged in with a local user (e.g., “Admin”).
To change it, open PowerShell as Administrator and run:
Rename-LocalUser -Name "Admin" -NewName "YourName"Or use the GUI:
Settings → Accounts → Family & other users → Change account name
Or Type Run → control → Enter
Additional (untested) registry method — use with caution
There is an emerging report of a registry-based technique that may still allow skipping the Microsoft account requirement. This approach requires opening a command prompt from the OOBE screen (press Shift + F10 at the “Let’s connect you to a network” screen) while disconnected from the internet, and entering a registry key to set a bypass flag:
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
shutdown /r /t 0
Important: This method is untested in our lab and may or may not work on current preview builds. Even if it works for some users now, Microsoft could remove or block this behavior in a future update as part of its effort to ensure devices are fully configured at first run. Treat this as experimental — test only in a virtual machine and proceed cautiously.
Here it’s the Script On Tips 2 Fix Github Page
Sources
-
Windows Blog (Microsoft announcement excerpt)
-
Windows Central (coverage of OOBE changes)
-
BleepingComputer (coverage of patched bypass methods)
Tags: #Windows11 #OOBE #MicrosoftAccount #InsiderPreview #TipsForUsers
Hello for local account it is oobe\bypassnro, it is not like oobe/bypassnro
📌 Clarification:
In the minute 4:12 of the video by mistake i typed slash wrong but even when typed correctly (`OOBE\BYPASSNRO`), that old OOBE command is patched in Windows 11 25H2 Insider builds (starting Build 26220.6772) and will show “not recognized” or cause a restart loop.
I recorded a quick proof short video and posted it here: https://tips2fix.com/wp-content/uploads/2025/10/oobe-bypassnro-not-working-in-widnows-11-25h2-insider-developer.mp4