Microsoft really does not want you using a local account on Windows 11, and boy is it annoying. Every major update since 2023 has closed another loophole, and the 24H2 release took it further by killing the classic no@thankyou.com email trick entirely. Microsoft confirmed in late 2025 that the online account requirement during OOBE is here to stay.

But local accounts still work fine after setup. You just need to get past the setup screen. Here are six methods that work right now, ranked by reliability.

Why Skip the Microsoft Account?

Not everyone wants their PC tied to a cloud identity. A few good reasons to go local:

  • Privacy. No Microsoft account linked to your hardware fingerprint.
  • Offline setups. Deployments where internet access during install is not available or not wanted.
  • Business environments. Domain join and workgroup setups that do not use Microsoft 365.
  • Shared machines. Kiosk PCs, lab computers, or family desktops where individual cloud accounts add unnecessary complexity.
  • Less telemetry. Local accounts send less diagnostic data back to Microsoft by default.
  • No forced OneDrive. Microsoft accounts automatically enroll in OneDrive cloud storage, which many users do not want.

Method 1: The ms-cxh:localonly Command

This is the most reliable method for Windows 11 24H2 and later builds. It triggers a hidden local account creation dialog built into OOBE.

  1. Boot into Windows 11 setup and proceed until you reach the Microsoft Account sign-in screen.
  2. Press Shift+F10 to open Command Prompt.
  3. Type start ms-cxh:localonly and press Enter.
  4. A local account creation dialog appears. Enter your username and password.
  5. Close the Command Prompt and continue setup normally.

This works because Microsoft still includes the local account path internally. The ms-cxh:localonly URI activates it directly.

Method 2: OOBE\BYPASSNRO

This classic method still works on many 24H2 builds, but Microsoft is actively removing it from newer ISOs. It is being phased out. Test it first; if the command is not recognized, use Method 3 instead.

  1. Disconnect from the internet. Unplug Ethernet or skip Wi-Fi.
  2. At the sign-in screen, press Shift+F10 for Command Prompt.
  3. Type OOBE\BYPASSNRO and press Enter.
  4. The PC restarts. After reboot, you will see an "I don't have internet" option.
  5. Click through to create a local account.

If the command returns "not recognized," the file has been removed from your build. Move on to Method 3.

Method 3: Registry Edit

When the BYPASSNRO command file is missing, you can set the same flag manually through the registry. This method works on every build tested so far.

  1. Press Shift+F10 during OOBE.
  2. Type regedit and press Enter.
  3. Navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE.
  4. Right-click the right pane, select New > DWORD (32-bit) Value.
  5. Name it BypassNRO and set its value to 1.
  6. Close Registry Editor.
  7. Type shutdown /r /t 0 in the Command Prompt to reboot.
  8. After restart, the "I don't have internet" option appears.

You can also create a second DWORD called HideOnlineAccountScreens with value 1 to suppress the Microsoft Account prompt entirely.

Method 4: Rufus

If you are doing a fresh install from USB, Rufus can bake the bypass directly into the installation media. This is the cleanest approach for new machines.

  1. Download the Windows 11 ISO from Microsoft's website.
  2. Download Rufus 4.4 or later.
  3. Open Rufus, select your USB drive, and choose the Windows 11 ISO.
  4. Click Start. A customization dialog appears.
  5. Check "Remove requirement for an online Microsoft account."
  6. Optionally check the boxes for TPM 2.0, Secure Boot, and RAM bypass as well.
  7. You can also pre-fill a local username in the dialog.
  8. Write the USB drive and install Windows normally. No account prompt appears.

Rufus is open source and has been doing this since Windows 11 launched. It also handles TPM, Secure Boot, and CPU requirement bypasses if your hardware does not meet Microsoft's specs.

Method 5: Domain Join, Windows 11 Pro Only

If you have Windows 11 Pro, there is a built-in workaround that does not require Command Prompt or registry edits.

  1. At the sign-in screen, select "Set up for work or school."
  2. Click "Sign-in options."
  3. Choose "Domain join instead."
  4. Create a local account with username and password.

This option does not exist on Windows 11 Home. Pro, Enterprise, and Education editions only.

What No Longer Works

A few popular methods from 2023 and 2024 have been patched:

  • The fake email trick (no@thankyou.com or a@a.com): Fully blocked in 24H2. Microsoft now validates the email format and checks account existence.
  • Killing the network connection flow in Task Manager: Used to work but now causes incomplete installs and missing drivers. Not recommended.
  • Running bypassnro without the full OOBE\ path: Newer builds require the full path or do not include the file at all.

If you find a guide recommending any of these, check the date. Anything published before mid-2025 is likely outdated.

A Note on TPM and Hardware Bypasses

The Microsoft Account requirement is separate from the TPM 2.0, Secure Boot, and CPU restrictions that also block Windows 11 installation on older hardware. If you need to bypass those as well, Rufus handles all of them in one step. For in-place upgrades on unsupported hardware, check out FlyOOBE from Builtbybel.

A full guide to TPM and hardware bypasses is coming in Part 2.

Microsoft will keep patching these methods. The ms-cxh:localonly command is the most stable option right now because it uses a legitimate internal path rather than exploiting a bug, but there is no guarantee it survives the next feature update. Bookmark this page. We will update it as methods change.

Need help deploying Windows 11 across your organization? Contact Rain City Techworks.