Microsoft Accounts, Now Mandatory to use your computer

The brief: a fresh Windows install would not proceed past first setup without a Microsoft account. No local account, no “work or school” bypass – just a wall at the login screen demanding an email address. A textbook case of the enshittification playbook: convert a local, offline function into a gate for account capture.

The Problem

During initial Windows setup (OOBE), Microsoft progressively removed the local account path. On Windows 11 Home and most Pro builds, the out-of-box experience pushes a Microsoft account sign-in as the only option. The well-known workarounds – disconnecting from the network, the oobebypassnro command – have been quietly patched out or made conditional across successive 22H2/23H2/24H2 releases.

The result: you can’t complete setup without handing over an email address, accepting consumer telemetry defaults, and (in many builds) agreeing to OneDrive backup and advertising preferences before you’ve even seen the desktop.

The Rot

• Feature gates under account walls: BitLocker recovery keys, OneDrive, Office activation, and the Windows Store all lean on the Microsoft identity. The account stops being optional.
• Workarounds rot too: every documented bypass gets a shelf life. Network-pull trick dead on newer ISOs; bypassnro removed from the Home SKU in 23H2 and later requiring a registry key.
• Telemetry by default: the forced sign-in is bundled with “help Microsoft improve your experience” toggles that default to on.

What Worked

• Deploying with an in-box account: for fleet/business imaging, creating the local user during unattended install (OOBE <AutoLogon> + <LocalAccounts>) sidesteps the consumer wall entirely.
• Pro/Edu registry escape: the HKLMSOFTWAREMicrosoftWindowsCurrentVersionOOBE BypassNRO DWORD still opens a local-account door on some Pro builds.
• Separating the gate from the product: telling clients “Microsoft account ≠ Windows” – you can run Windows fully, offline, with a local admin – resets expectations at the counter.

The Takeaway

This isn’t a bug; it’s the product roadmap. The forced account is deliberate friction designed to fold the local user into Microsoft’s identity graph. For the IT technician it means every clean install is now a negotiation – either with the client about what “their” account means, or with the OOBE itself. The countermeasure is not a magic command; it’s knowing which install path actually keeps the machine local, and being upfront that the wall exists.

Status

Still rotting. Microsoft continues to tighten the path each release. Expect the local-account door to keep shrinking; plan deployments accordingly.

Watch: NO Microsoft Account Needed: Windows 11 Local Setup