Every laptop that lands on my desk gets set up offline. No Microsoft account, no cloud sync, no OneDrive prompt on first boot. Windows 11 has made this progressively harder to do, but there is still a fast, clean way to get it done.
Why Local Accounts Still Matter
A local account keeps the machine independent. The user’s login is not tied to a Microsoft account, no settings sync happens without being explicitly configured, and OneDrive does not auto-enable. For work deployments this matters — you want a clean baseline, not a machine that immediately starts pulling down the previous user’s cloud state.
Microsoft has been quietly tightening the OOBE (Out-of-Box Experience) to push account sign-in as the only path. The well-known oobe\bypassnro workaround has been officially removed from newer builds, which is what led most people to notice the change. The replacement is faster anyway.
The Command That Actually Works
During Windows 11 setup, when you hit the screen asking you to connect to a network or sign in with a Microsoft account:
- Press
Shift + F10to open a command prompt - Type the following and press Enter:
start ms-cxh:localonly
Code language: PowerShell (powershell)A local account creation window appears. Fill in username and password, click Next, and setup continues straight to the desktop. No reboot required, unlike the old bypassnro method.
The full flow is: choose region and keyboard layout, skip Wi-Fi, open the command prompt with Shift + F10, run the command, set your username and password, and decline the telemetry prompts. From command prompt to desktop takes about 30 seconds.
What I Use for the USB
I use YUMI Multiboot to manage my bootable USB. It supports multiple ISOs on a single drive, so the same stick carries the Windows 11 installer, a Linux live environment, and a diagnostics tool. The Windows 11 ISO itself comes from the official Media Creation Tool — always the latest build, which matters because older ISOs may behave differently during OOBE.
How Long This Will Last
The honest answer: probably not forever. Microsoft has already been testing removal of ms-cxh:localonly in Insider preview builds, with some October 2025 builds looping OOBE back to the Microsoft account gate when the command is run. Those changes have not hit mainstream release builds yet, but the direction is clear.
If permanent offline-first deployment matters for your environment, the longer-term solution is a documented offline deployment strategy — unattend.xml answer files or a pre-configured image rather than relying on OOBE bypass commands that Microsoft can remove in any update.
For now, start ms-cxh:localonly works on every release build I have tested, including 24H2 and 25H2. It is the fastest method currently available and a direct replacement for bypassnro on any build where that script has been removed.