Microsoft VP Scott Hanselman has revealed he is working to end Windows 11's mandatory Microsoft account requirement. His remark, posted on X on 20 March 2026 in response to a user complaint, marks a rare public signal that one of Windows 11's most despised features may finally be under review at the company's highest levels.
Windows 11 currently forces every consumer to create a Microsoft account and connect to the internet during setup, a policy that has frustrated millions of users since it was extended to Windows 11 Pro in February 2022. Prior to that extension, Home edition users were already subject to the requirement, meaning the mandate has been steadily broadened over successive Windows releases.
Hanselman's public comment carries weight beyond a typical employee observation. He holds the title of Vice President of Developer Community at Microsoft and is among the leaders responsible for improving Windows 11. His willingness to acknowledge the frustration suggests momentum building within Microsoft engineering to address the issue.
Yet significant obstacles remain. Internal business units that benefit from mandatory sign-ins for advertising and product engagement metrics are resisting the change. Advertising and telemetry systems tied to logged-in users represent real revenue streams for Microsoft, creating institutional friction against what might seem like a straightforward user experience improvement.
The practical case for change is substantial. Even the Professional version of Windows 11 now requires a Microsoft account. Windows 11 normally requires a Microsoft account when you set it up, but users can bypass Microsoft account creation and use a local account instead. That users must resort to technical workarounds like disconnecting from the internet or entering invalid email addresses during setup underscores the gap between what many want and what Microsoft offers by default.
Microsoft has actively enforced the policy by closing workarounds that allowed users to bypass setup with a local account, including one that was blocked in October 2025. This aggressive stance against user self-determination has fed the perception that the requirement is not about technical necessity but about forcing adoption of Microsoft's ecosystem.
The counterargument carries validity. A Microsoft account is an online account that uses your email and password to sign in to the computer. It offers more security, provides more recovery options in case you forget your PIN or Password, and syncs themes, apps, and settings to other devices. For users managing multiple devices, cloud synchronisation is genuinely useful. The problem is Microsoft has collapsed choice and convenience into a single requirement.
Importantly, Hanselman's statement does not represent official policy. The removal of the account requirement is not on the list of new features and improvements that Pavan Davuluri, President of Microsoft's Windows and Devices division, published. No concrete plan or committed timeline exists for removing the requirement, despite growing internal and external pressure.
Microsoft's Windows team is actively exploring options for relaxing or removing the mandate, which could include offering local account setup as a parallel option rather than eliminating the Microsoft account flow entirely. No committed timeline currently exists for any of these options.
The broader context matters here. In late January 2026, Windows president Pavan Davuluri publicly admitted Windows 11 had gone off track and pledged to fix the operating system this year. What followed was a detailed strategy of new features, fixes, and improvements coming to Windows in April and throughout the year. That Microsoft is publicly committing to major improvements suggests the company understands the depth of user dissatisfaction and the business risk of ignoring it.
The account requirement sits at an intersection of legitimate technical advantage and genuine user autonomy concerns. A shift toward making local account setup simpler and equally prominent during installation would represent a pragmatic compromise. Microsoft would preserve cloud benefits for those who want them whilst respecting users who prefer to own their system setup process. Whether Hanselman's working comment translates into actual change depends on whether the engineering momentum can overcome the institutional interests defending the status quo.