Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The stated "reason" makes no sense:

> While these mechanisms were often used to bypass Microsoft account setup, they also inadvertently skip critical setup screens, potentially causing users to exit OOBE with a device that is not fully configured for use.

If they're only worried that their users may end up with an incomplete Windows install, surely the solution is to provide a better way to set up Windows with a local account? It's not like people are digging around in CMD and RegEdit during the install for the fun of it, they could immediately stop everyone from using these workarounds by adding back the "set up with a local account" button





They're not worried about that, they're worried about users not creating and using microsoft accounts. The stated reason could be a paragraph of lorem ipsum and it wouldn't make the press release any less obtuse.

Everyone knows they're not worried about that. GP is simply pointing out a hole in their story of claiming to care about something else.

"Fully configured for use" in Microsoft's eyes means that you've turned on all the extra crap they nag you about in the setup screen, which 99% of users who are skipping the account setup also don't want.

The user isn't in focus here, it is about placing their often quite defunct products and to make people dependent.

These are probably the typical fail-upwards product manager decisions. Maybe Windows will sooner than later go the way of the Xbox.


They mention in the article: there is a way to use bypass Microsoft account setup, but you need to use an unattended setup file. And these tools didn't want to use that.

Because they are in the second stage of enshittification. You as a user of their products are not their primary customer - they want to sell your data. Companies buying that data are now their primary customer, so they will prioritize them over you.



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: