Is anyone else having issues with Windows Updates and signing into there Microsoft Account that uses 2 Step Auth? After I upgraded via WU to 10240 it signed me out of Insider Program or something. See Pic. If I Click the Refresh button I get a login to my MS account window. If I sign in with my regular password and aprove the login with my android phone it says the same thing. If I create a ONE TIME password it says password is wrong.
I think I might have just realized why its acting this way. I'm running 10240 Enterprise and its joined to a Server 2012 R2 Domain and I am signing into Windows 10 using my AD account rather than signing into Windows 10 with my MS account. That is just my guess though. I might switch to a workgroup and see what happens just for the hell of it. I will share the results. ~MC
Same thing happened to me. I would sign in my MSA and approve the one time password via text message, I would get an error and could not sign in.
So much for that idea. didnt seem to make any difference. in fact it doesnt seem to like the fact that my ms account uses 2 step auth. didnt have this issue with previous insider builds. I really do want to have to turn off 2 step auth on my ms account. Wont let me attach my ms account to my local admin account or add it as a separate account at all. I dont think it likes my 2 step auth. bummer.
In the past (last tried it on 10162), MSA sign-in with 2-step verification (via Android app) worked fine for me. Can't say if/how it works now though.
My guess it would be something to do with your AD stuff. I've been using 2-step authentication on my test laptop since build 10074. Mostly clean installs, so had to verify my account and trust device on install. The last few builds have been upgrades, which have transferred across fine. Sidenote: After the last Android update the authenticator on my Nexus 7 stopped working, so I swapped to my Lumia. Not sure if that's relevant.