This can result in a situation where an old password can be used to access a system remotely, and can be considered a security threat.Īfter changing your password on the Microsoft account website, you must update the password on the local machine by either signing out or locking the system and signing back in by using the new password. If the user then attempts to log in remotely via Remote Desktop, and has changed the Microsoft account password without using it to log in locally afterwards, the remote login will fail because the system is still expecting the old password. This leaves the accounts in an "out-of-sync" state where the local user account still accepts the old password until the Microsoft account, not the pin or picture password, is used to log in to the system locally. If the user then switches to using a pin or picture password at the local console, the credentials do not get updated locally, even if the user changes the password on the Microsoft website, the "Manage Microsoft Account" link in Settings, or the "Change Password" utility in Sign-in Options. What is happening: When a Microsoft account is linked to a user account in Windows 10, the credentials are cached locally to facilitate offline logins. This can happen even if the user changes the password on the Microsoft site. This happens when users only use a pin or picture password when logging in at the local console. When using Remote Desktop on Windows 10 and using a Microsoft account to authenticate, the login will sometimes fail if the credentials have not been updated locally.
Follow the guidelines below for more information on this issue and steps to take to resolve it. But the commands that I am trying in Powershell are the new equivalent.When using Remote Desktop on Windows 10 and using a Microsoft account to authenticate, the login will sometimes fail if the credentials have not been updated locally. Is Azure just not going to allow me to re-install Windows in this manner, or am I missing something?Įdit: Yes, I have looked at this post and the command in that answer will not work for me since I am using the new Azure Resource Manager model to set up the VM. I tried deleting the VM and creating a new one, and get the same results. I have also tried redeploying the VM and trying to upgrade the OS, and I got the same results.
I can go to the Boot Diagnostics page, and see that it is stuck on the setup screen after restart: I do what it says and check my Extensions on my VM and it basically seems that they aren't available since Windows hasn't finished re-installing. I followed the troubleshooting steps to reset the VMAccessExtension, but the command keeps failing. The OS was re-installed so I am guessing my credentials no longer work to RDP.
I think I know why this is happening, but I don't know how to fix it.
I was able to mount the ISO and the install seemed to work fine, then the machine needed to restart - and now I cannot connect. I tried to install the latest Windows 10 Preview Build using an ISO from my MSDN account.