Comment by MaximilianEmel
3 months ago
Search for "Local-only commands removal" on the page for the relevant section:
Local-only commands removal: We are removing known mechanisms for creating a local account in the Windows Setup experience (OOBE). 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. Users will need to complete OOBE with internet and a Microsoft account, to ensure device is setup correctly.
>While these mechanisms were often used to bypass Microsoft account setup, they also inadvertently skip critical setup screens
Poor people. Surely Microsoft is fixing this by giving them a proper local skip that doesn’t bypass the other critical setup?
Presumably the business/enterprise editions still do?
Enterprise might but Professional sure doesn't.
4 replies →
Maybe not for the long term; business/enterprise are mostly using domain accounts for non-server systems.
The requiring internet part is particularly egregious, wow.
Because it seems that microsoft could not shitify windows experience anymore.
I like windows, Its a great system specially for being productive, but the godamn start menu using react and edge and the online requirements are a pain in the ass.
Sometimes it just hangs while you click the windows key. All I want is to open notepad++...
I've found the start menu is perfectly responsive if you disable its internet results.
2 replies →
Sounds like more lies: you can still use autounattend.xml as far as I know. If they broke this it would break almost all the top corporate enterprise stuff
(same reason they still have network printer driver vulnerabilities because they refuse to fix old shit in the name of backward compatibility)
NOTE: I originally left this comment here: https://news.ycombinator.com/item?id=45497893
"critical"