SEO metadata

  • Slug: /windows-11-local-account-removed-microsoft-account-required
  • Title tag (58 chars): Windows 11 Local Account Removed: Microsoft Account Required
  • Meta description (154 chars): Microsoft removed bypassnro.cmd and ms-cxh:localonly from Windows 11 setup. Here's what changed in 2025–2026 and which local account methods still work.
  • Primary keyword: Windows 11 local account
  • Secondary keywords: bypassnro removed, Windows 11 without Microsoft account, ms-cxh:localonly, Windows 11 OOBE Microsoft account requirement, BitLocker recovery key Microsoft account
  • Schema: NewsArticle + FAQPage (FAQ block below), author, datePublished, dateModified
  • Image alt text: "Windows 11 OOBE screen requiring a Microsoft account sign-in during setup"

Windows 11 Local Account Removed: Microsoft Deletes Local Account Creation Mechanisms From Setup

Author: Lyle Heartman

Beginning in March 2025, Microsoft removed a series of mechanisms that allowed a new installation of Windows 11 to be completed without an internet connection and without signing in to a Microsoft account. The first of these was bypassnro.cmd, a script shipped by Microsoft as part of the operating system itself, which was deleted from Insider Preview builds on 28 March 2025. In October 2025 Microsoft went further, stating that it was removing the remaining known methods for creating a local account during setup. Because Windows 11 also escrows disk encryption keys to a Microsoft account by default, the change links a consumer's access to their own encrypted data to the continued availability of an online account.

Key points at a glance

  • bypassnro.cmd was removed from Windows 11 Insider Preview Build 26200.5516 on 28 March 2025.
  • start ms-cxh:localonly and the BypassNRO registry value were removed in Builds 26220.6772 / 26120.6772 (KB5065797) on 6 October 2025.
  • Windows 11 24H2 and later enable device encryption automatically and upload the recovery key to the Microsoft account.
  • Local account setup remains possible in 2026, but mainly through pre-installation image modification.

Background: Windows 11 OOBE and the Microsoft account requirement

The Out-of-Box Experience (OOBE) is the sequence of setup screens shown the first time Windows is installed or a new device is switched on. Windows 11 Home has required an internet connection and a Microsoft account to complete OOBE since the operating system launched in October 2021, and the same requirement was extended to Windows 11 Pro with version 22H2. A local account, meaning an account stored only on the device with no online component, remained possible to create, but only through undocumented routes.

What bypassnro.cmd did

BypassNRO.cmd ("NRO" for network requirement override) was one such route, and was distinguished from the others by being a Microsoft-authored script included in the operating system at C:\Windows\System32\OOBE\BypassNRO.cmd. Run from a command prompt opened during setup, it wrote a single registry value (BypassNRO under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE) and restarted the machine, after which setup offered an option to continue without an internet connection.

How device encryption changed in Windows 11 24H2

Separately, Windows 11 version 24H2 expanded device encryption, the consumer version of Microsoft's BitLocker full-disk encryption, so that it is enabled automatically on clean installations across all editions, including Home, on hardware meeting the standard Windows 11 requirements. When setup is completed with a Microsoft account, the recovery key needed to unlock the drive is uploaded to that account automatically. The two changes interact: with local account creation removed, the default path for a consumer installing Windows 11 results in an encrypted drive whose recovery key is held by Microsoft.

Removal of local account setup mechanisms in Windows 11

March 2025: Microsoft removes bypassnro.cmd

On 28 March 2025, Microsoft published release notes for Windows 11 Insider Preview Build 26200.5516 (KB5054687) in the Dev Channel. Under the "Other" heading, the notes stated that the bypassnro.cmd script was being removed from the build, described as being done to "enhance security and user experience of Windows 11", and that the change would result in users finishing setup with both internet connectivity and a Microsoft account.

The removal deleted the script, but not the underlying registry behaviour it triggered. For a period afterwards, the same result could be obtained by writing the BypassNRO registry value manually, or by using the command start ms-cxh:localonly, which invoked a Cloud Experience Host URI that opened a legacy local account creation screen.

October 2025: Microsoft removes the remaining local-only commands

On 6 October 2025, Microsoft released Insider Preview Builds 26220.6772 (Dev Channel) and 26120.6772 (Beta Channel), both under KB5065797. The release notes contained a section headed "Local-only commands removal", in which Microsoft said it was "removing known mechanisms for creating a local account" in the Windows Setup experience. Microsoft's stated reasoning was that these mechanisms, while used to avoid Microsoft account sign-in, also caused setup screens relevant to configuration to be skipped, potentially leaving a device incompletely set up.

Independent testing of the affected builds found that oobe\bypassnro, the BypassNRO registry value, and start ms-cxh:localonly no longer produced a local account path. Instead the commands either had no effect, returned setup to the Microsoft account sign-in screen, or restarted OOBE in a loop. Reporting noted that the change applied to consumer installations and did not affect managed or domain-joined enterprise deployments.

In the same builds, Microsoft added SetDefaultUserFolder.cmd, a supported command allowing the default user folder to be named during setup. This addressed a long-standing complaint about folder naming under Microsoft accounts but did not restore an offline local account path.

Microsoft's response

Microsoft has not published a response separate from the release notes themselves. In both instances the company framed the removals as improvements to security and to setup completeness rather than as account policy, stating in October 2025 that users would need to complete OOBE with an internet connection and a Microsoft account to ensure the device is configured correctly.

Consumer impact of the Windows 11 Microsoft account requirement

Commentary and reporting identified several consequences of the requirement for consumers who would otherwise use a local account:

  • Encryption key escrow. On Windows 11 24H2 and later, completing setup with a Microsoft account triggers automatic device encryption and uploads the recovery key to that account. Recovery prompts can be triggered by ordinary events such as firmware updates or changes to UEFI settings, at which point the key is required to regain access to the data.
  • Dependency on account availability. Because the recovery key is stored in the Microsoft account, loss of access to that account, whether through suspension, closure, or lost credentials, can result in loss of access to the encrypted drive.
  • Association of device data with an identity. Setup with a Microsoft account links diagnostic and usage data collected by the operating system to an identified account rather than to an anonymous device.
  • Additional contractual terms. Creating a Microsoft account requires acceptance of the Microsoft Services Agreement and associated privacy terms, which are separate from and additional to the licence terms for the operating system.

Consumer response and community workarounds

The March 2025 removal drew criticism on Microsoft's own community forums, where users questioned the stated security rationale and asked what would happen to existing local account installations on upgrade. Technology press coverage characterised the sequence of removals as an escalating contest between Microsoft and users, with each closed method followed by the circulation of a new one.

Community-maintained workarounds continued to appear after each removal. These included a method using the OOBE developer console, opened with Ctrl+Shift+J, to call a WinJS.Application.restart function that loads an older local account creation screen; this method was documented in public repositories and reported to still function after the October 2025 builds, including on devices in S Mode. Projects also emerged to reimplement the removed BypassNRO functionality using PowerShell, Sysprep, and unattended answer files.

The methods that remained most reliable were those that modify the installation media before setup begins, such as an autounattend.xml answer file or an ISO customised with a third-party tool. These are substantially more involved than the single command they replaced, and reporting noted that they are impractical for most consumers.

Current status in 2026

The removals were introduced through Insider Preview channels and have propagated unevenly to general release builds. Into early 2026, testing reported that oobe\bypassnro still functioned on some retail Windows 11 25H2 installations, while newer builds blocked it. Coverage in 2026 has continued to treat local account creation as possible but increasingly dependent on pre-installation image modification rather than on any in-setup command.

Frequently asked questions

Can you still create a local account in Windows 11 in 2026? Yes, but not reliably through an in-setup command. The methods reported to still work depend on modifying the installation media before setup begins, such as an autounattend.xml answer file or a customised ISO.

Why did Microsoft remove bypassnro.cmd? Microsoft's release notes for Build 26200.5516 described the removal as being done to "enhance security and user experience of Windows 11", and said the change would result in users finishing setup with both internet connectivity and a Microsoft account.

Does the change affect enterprise deployments? Reporting noted that the October 2025 change applied to consumer installations and did not affect managed or domain-joined enterprise deployments.

Where is my BitLocker recovery key stored? On Windows 11 24H2 and later, completing setup with a Microsoft account uploads the device encryption recovery key to that Microsoft account automatically.

References

  1. "Announcing Windows 11 Insider Preview Build 26200.5516 (Dev Channel)", Windows Insider Blog, 28 March 2025. https://blogs.windows.com/windows-insider/2025/03/28/announcing-windows-11-insider-preview-build-26200-5516-dev-channel/
  2. Amanda Langowski, "Announcing Windows 11 Insider Preview Build 26220.6772 (Dev Channel)", Windows Insider Blog, 6 October 2025. https://blogs.windows.com/windows-insider/2025/10/06/announcing-windows-11-insider-preview-build-26220-6772-dev-channel/
  3. "Forensic Implications of BitLocker-by-Default in Windows 11 24H2", ElcomSoft blog, 8 May 2025. https://blog.elcomsoft.com/2025/05/forensic-implications-of-bitlocker-by-default-in-windows-11-24h2/
  4. "Find your BitLocker recovery key", Microsoft Support. https://support.microsoft.com/en-us/windows/find-your-bitlocker-recovery-key-6b71ad27-0b89-ea08-f143-056f5ab347d6
  5. "Microsoft's killing script used to avoid Microsoft Account in Windows 11", BleepingComputer, 30 March 2025. https://www.bleepingcomputer.com/news/microsoft/microsofts-killing-script-used-to-avoid-microsoft-account-in-windows-11/
  6. "Microsoft confirms Windows 11 24H2 turns on Device Encryption by default", Windows Latest, 8 May 2024. https://www.windowslatest.com/2024/05/08/microsoft-confirms-windows-11-24h2-turns-on-device-encryption-by-default/
  7. "Microsoft has disabled the popular 'bypassnro' Windows 11 sign-in workaround in the latest Insider build, but there exists another", PC Gamer, 31 March 2025. https://www.pcgamer.com/software/operating-systems/microsoft-has-disabled-the-popular-bypassnro-windows-11-sign-in-workaround-in-the-latest-insider-build-but-there-exists-another/
  8. Mark Tyson, "Microsoft eliminates workaround that circumvents Microsoft account requirement during Windows 11 installation", Tom's Hardware, 30 March 2025. https://tech.yahoo.com/articles/microsoft-eliminates-workaround-circumvents-microsoft-162036008.html
  9. "Announcing Windows 11 Insider Preview Build 26120.6772 (Beta Channel)", Windows Insider Blog, 6 October 2025. https://blogs.windows.com/windows-insider/2025/10/06/announcing-windows-11-insider-preview-build-26120-6772-beta-channel/
  10. "Microsoft blocks bypass to skip Microsoft Account during setup on Windows 11", Pureinfotech, 7 October 2025. https://pureinfotech.com/microsoft-blocks-windows-11-microsoft-account-bypass/
  11. "Tested: Microsoft confirms Windows 11 requires a Microsoft account, internet in OOBE", Windows Latest, 7 October 2025. https://www.windowslatest.com/2025/10/07/microsoft-confirms-windows-11-to-require-microsoft-account-internet-during-oobe-tested/
  12. Hassam Nasir, "Microsoft clamping down on Windows 11 local account setup: latest Insider build removes 'local-only commands'", Tom's Hardware, 7 October 2025. https://www.tomshardware.com/software/windows/microsoft-clamping-down-on-windows-11-local-account-setup-latest-insider-build-removes-local-only-commands-skipping-microsoft-account-sign-in-will-crash-setup-process
  13. "Microsoft kills two more ways to install Windows 11 with local accounts", PCWorld, 7 October 2025. https://www.pcworld.com/article/2932975/microsoft-kills-two-more-ways-to-install-windows-11-with-local-accounts.html
  14. "Microsoft Ends Local Account Workarounds in Latest Windows 11 Build", Redmond Magazine, 8 October 2025. https://redmondmag.com/articles/2025/10/08/microsoft-ends-local-account-workarounds-in-latest-windows-11-build.aspx
  15. "bypassnro Removal", Microsoft Community Hub, 29 March 2025. https://techcommunity.microsoft.com/discussions/windowsinsiderprogram/bypassnro-removal/4398756
  16. "WinJS-Microsoft-Account-Bypass", GitHub. https://github.com/the-P1neapple/WinJS-Microsoft-Account-Bypass
  17. "How to bypass Microsoft Account in OOBE on Windows 11: methods that still work", Pureinfotech, 25 March 2026. https://pureinfotech.com/bypass-microsoft-account-windows-11-oobe/
  18. "BypassNRO: Fixing and Re-implementing Microsoft's removal of BypassNRO", GitHub. https://github.com/Stensel8/BypassNRO
  19. "Microsoft says I need a Microsoft account to set up Windows 11, but that's still not true in 2026", XDA Developers, 2026. https://www.xda-developers.com/windows-11-without-microsoft-account-possible-2026/
  20. "Set Up Windows 11 With Only a Local Account", Ask Leo!, March 2026. https://askleo.com/set-up-windows-11-with-only-a-local-account/