Microsoft's own VP just said "Ya I hate that. Working on it." about the mandatory Microsoft Account requirement in Windows 11.
That's Scott Hanselman. Vice President of Developer Community. The person Microsoft literally pays to make developers happy.
And he's publicly admitting the setup experience for Windows 11 is broken.
Here's the backstory
Windows 11 launched in October 2021. From day one, the Home edition forced you to create a Microsoft Account during setup. No internet? No local account? No computer.
By mid-2022, they extended the same requirement to Windows 11 Pro.
The developer community responded exactly how you'd expect. People started sharing workarounds like oobe\bypassnro in Command Prompt. Others used Rufus to create modified install media. Some disconnected their ethernet mid-setup just to get a local account.
Microsoft noticed. They started patching the workarounds. Killing bypass scripts. Removing the "I don't have internet" button from preview builds.
It became an arms race between Microsoft and its own users.
Why this matters to devs
If you've ever set up a test VM, a CI runner, or a bare-metal build machine, you know this pain. You don't want your throwaway dev environment tied to your personal Microsoft Account. You don't want OneDrive syncing your temp files. You don't want Copilot suggestions on a machine you're wiping next week.
Enterprise customers get around this with domain joins and Intune. But individual developers, freelancers, and hobbyists? They're stuck playing cat-and-mouse with setup hacks.
The real fight is internal
According to Windows Central, senior engineers inside Microsoft have been pushing to drop the requirement. Hanselman's tweet wasn't a solo act. Multiple employees reportedly want an "MSA-free" login option.
But here's the friction. The teams that own advertising, product engagement metrics, and Microsoft 365 upsells benefit from every forced account creation. Every new setup is a data point, a potential subscription, a number on a quarterly slide.
It's the classic platform tension. The people building the product want it to be good. The people measuring the product want it to convert.
The pattern is bigger than Windows
This isn't just a Microsoft problem. It's the same pattern everywhere.
→ Adobe won't let you use Photoshop without Creative Cloud
→ JetBrains requires an account for IDE activation
→ Even VS Code's Settings Sync nudges you toward GitHub or Microsoft login
The industry decided that accounts equal engagement and engagement equals revenue. Users became conversion metrics, not people trying to get work done.
What actually changed
Hanselman's tweet landed on March 20, 2026. A week later, there's no official announcement, no timeline, no committed plan.
The teams that benefit from mandatory accounts are reportedly resisting the change. So we have a Microsoft VP publicly saying "I hate that" about his own company's product while other teams inside the same company fight to keep it.
If that doesn't perfectly capture how large companies make product decisions, I don't know what does.
The optimistic read is that enough internal pressure will eventually win. The realistic read is that engagement metrics rarely lose to developer experience in a boardroom.
What do you think? Should operating systems require an account to set up, or is that a line that should never have been crossed? 👇
Top comments (0)