Technical Anshu
Tutorials Blog
🛠️ Setup Routes Verified

Create a Local Account During Windows 11 Setup The Routes Verified Today

Setup is where the Microsoft account demand feels absolute — but it is also where advice goes stale fastest. Commands get removed from install media, registry tricks get blocked in new builds, and yesterday's clever shortcut becomes today's dead end. Here are the during-setup routes, each labelled with what it actually does on current Windows.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 9 minute read
🎥 Watch the video to see the setup command working on screen

The honest starting point: there is no single trick that works on every Windows 11 build any more — and any guide that promises one is out of date. Microsoft is closing these mechanisms deliberately and has said so. What remains is a small set of routes with different requirements: one needs older media, one needs the Pro edition, one needs you to prepare your own USB. Match the route to your situation and you will not waste an evening typing commands into a build that has already removed them.

Command Prompt over setup — the screen from the video
Microsoft Windows [Version 10.0.26200] (c) Microsoft Corporation. All rights reserved. X:\windows\system32>start ms-cxh:localonly
Older install media — local account creator opensWorked
Newest builds — command blocked, screen stays on sign-inClosed

👆 The video's command, honestly labelled: real, demonstrated — and being switched off build by build. Do not confuse "worked in the video" with "works on media made this month".

1

The Video Method — Try It, With Eyes Open

  1. Reach the Microsoft account sign-in screen during setup
  2. Press Shift + F10 — add Fn on laptops whose F-keys are shared with brightness and volume
  3. In the Command Prompt, type start ms-cxh:localonly and press Enter
  4. If the local account creator opens, create the account and finish. If nothing happens, your build has the command blocked — close the prompt and use Step 2 or Step 3 instead of hunting for more commands

Why the honesty: Microsoft has stated publicly it is removing setup mechanisms that create local accounts, because they can skip configuration screens. Testers confirmed this command, start ms-cxh://setaddlocalonly, the BypassNRO registry value and the fake-email route all blocked in current preview builds. Blocks land in preview builds first — which is why reports disagree — but the direction is one-way.

2

Pro Edition — The Documented Domain Join Path

Windows 11 Pro setup contains a supported offline path because businesses genuinely need it:

  1. When setup asks how you will use the device, choose Set up for work or school
  2. On the sign-in screen, open Sign-in options
  3. Choose Domain join instead
  4. Create the local username and password on the classic screens that follow, and finish setup — the PC never contacts a domain

Because this is a real deployment feature rather than a loophole, it is the during-setup route most likely to still be there next year. It needs Pro; most consumer laptops ship with Home, and Home does not show it.

3

Any Edition — Prepare the USB With Rufus

If you are creating your own install media, the decision can be made before setup starts, using documented options in the free Rufus tool:

  1. Download the official Windows 11 ISO from Microsoft, and Rufus from its official site
  2. Select the ISO and your USB stick, and click Start
  3. In the Windows User Experience dialog that appears, tick Remove requirement for an online Microsoft account
  4. Tick Create a local account with username and type the name you want
  5. Write the USB, boot from it, and setup goes straight to local account creation

Honest limits: Rufus modifies the install media, so use ISOs from Microsoft only, and in a company, check your IT policy before using customised media. For a single home PC it is the most predictable during-setup route that exists today.

4

The Graveyard — Do Not Waste an Evening on These

  1. oobe\bypassnro — the script file was removed from newer Windows install media entirely. The command now simply fails
  2. The BypassNRO registry value — survived the script for a while, then was tested as blocked in current preview builds. Some older media may still honour it; current media increasingly does not
  3. Fake email addresses — typing a nonsense or over-used email to force an error screen worked years ago. Setup now just rejects and loops
  4. The "Learn more" link path — a brief OOBE quirk that opened a local account flow on Home; it was closed from Microsoft's side without any update on the PC

Notice the pattern: every route that depends on Microsoft not noticing is temporary. The two routes above that survive — domain join and pre-built media — survive because they are deployment features, not bugs.

🔴 One rule for every during-setup trick: it is only real on the media in your hand. A video — including ours — can only show the build it was recorded on. If a command does nothing on your screen, your build has moved on; fall back to the domain join or switch-after-setup routes instead of stacking more commands from older and older guides.

🎥 Watch the Complete Process in the Video

The video demonstrates the setup command live - watch it, and keep this page open to pick the fallback route if your build has moved on.

▶️ Watch Full Video
❓ Frequently Asked Questions

The video command did nothing on my PC. Is my laptop faulty?

No — your install media is simply newer than the build in the video. Microsoft announced it is removing local-account mechanisms from setup, and current builds block start ms-cxh:localonly. On Windows 11 Pro, use Set up for work or school, then Sign-in options, then Domain join instead. On Home, finish setup with a Microsoft account and switch to a local account afterwards in Settings, Accounts, Your info.

Can I still use oobe bypassnro?

The bypassnro script was removed from Windows install media in newer builds, so the command fails outright. The registry value that did the same job was later tested as blocked in current preview builds as well. Some older ISOs still accept one or both, which is why old guides seem to work for some people — but neither is a route to plan a new install around.

Is using Rufus to create a local account safe?

Rufus is a long-standing, widely used tool, and the two options — removing the online account requirement and creating a local account with a username — are documented features of it. Download Rufus and the Windows ISO only from their official sources, and know that the USB it writes is customised media: fine for your own PC, but check policy before using it on company machines.

This guide is based on the Technical Anshu video on using Windows without a Microsoft account • Stuck on any step? Ask in the video comments — you will get a reply there 🙏