Build 10162, local account and Insider updates

After a clean install of the latest build 10162, I noticed the following issue. The system complaint that something was wrong with the Insider setup and eventually requested my Microsoft account login data. Fair enough, I thought, and gave it my password, only to be greeted with the screen that said something like "give us your local password one last time, we're replacing it by the new password you've just created".

Now, wait a minute! I am not going to, I mean I absolutely refuse to login into my local Windows machine with the Microsoft account or any other web-based stuff. It's just not going to happen.

I mean, sure, I can login into the Microsoft account to download a new build or for any update pr whatever, but what does that have to do with the local login?

Is anyone else bothered by this, or do I misread the issue?

I've always viewed that as just (another) part of the verification process and really haven't given it much thought.

unifex said:

After a clean install of the latest build 10162, I noticed the following issue. The system complaint that something was wrong with the Insider setup and eventually requested my Microsoft account login data. Fair enough, I thought, and gave it my password, only to be greeted with the screen that said something like "give us your local password one last time, we're replacing it by the new password you've just created".

Now, wait a minute! I am not going to, I mean I absolutely refuse to login into my local Windows machine with the Microsoft account or any other web-based stuff. It's just not going to happen.

I mean, sure, I can login into the Microsoft account to download a new build or for any update pr whatever, but what does that have to do with the local login?

Is anyone else bothered by this, or do I misread the issue?

If by misreading you mean misreading how the Insider program works with the preview then yes. It's even stated in User Account settings that an MSA isn't required to use Windows, only that it gives the "best experience". You, however, are using an Insider Preview, which they are tying to MSAs.

What is it you think they are going to do with your MSA tied to your login that they aren't already doing when you log in over the web, use other services they provide, etc?

Also, have you looked​ into Telemetry and the Insider Preview? If you are paranoid about data collection the preview probably isn't for you.

Earlier builds of the insider preview were not specifically tied to the Microsoft account. I had to login into the account to provide feedback, etc., but not to run the PC. Now it looks like the PC is running just fine on a local account, but it won't offer newer builds anymore. If that's all there is to it, than it's fine with me.

unifex said:

Earlier builds of the insider preview were not specifically tied to the Microsoft account. I had to login into the account to provide feedback, etc., but not to run the PC. Now it looks like the PC is running just fine on a local account, but it won't offer newer builds anymore. If that's all there is to it, than it's fine with me.

Gabe Aul announced with the 10158 build that going forward, Insiders would need to use an MSA to continue receiving Insider builds. The reason for this is to differentiate them from normal Windows 10 users. The only way they can do this is by using an MSA (this is the same process they use to target builds to their own employees).

Upcoming changes to Windows 10 Insider Preview builds [UPDATED 6/22] | Blogging Windows

Right, thanks Mystere, that clears up my question.

I actually had an earlier build 10130 installed on my test machine, but it was rather buggy and did not even want to update itself, so I just downloaded an ISO of 10162 and did a clean install. I was rather surprised that its insistence on changing to the Microsoft account as the local login (I always install OSs while disconnected from the Internet, so the installer just generates a local user account for me automatically).