Microsoft has recently announced further steps to prevent users from signing in via a local account:
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 ~ <source>
Back in March this year, Microsoft announced that it was blocking a well-known script used for circumventing the internet connection and Microsoft account sign-in requirements. However, it didn’t prevent users from applying other workarounds, such as performing a registry edit to activate the script, hence this new announcement regarding further steps.
As for Microsoft’s claim that by bypassing the Microsoft account setup, users also skip critical setup options, meaning the device is not properly configured. As far as I can recall, none of those additional setup options offer anything critical or important, so I’ve always skipped right through them anyway.
BOTTOM LINE:
Microsoft’s insistence on forcing users to sign in via a Microsoft account is not only anti-freedom-of-choice, but it also creates concerns for many users who prefer to sign in via a local account for privacy and security reasons.
As far as I am concerned, this decision exemplifies Microsoft’s increasingly dictatorial attitude. Let us know your thoughts via the comments.
—
