There’s an issue in Windows 10 which causes Microsoft Account passwords to become out of sync when using Remote Desktop (RDP). For example, I have a few computer systems running Windows 10 which I only access via Remote Desktop using my Microsoft Account (for example, username@outlook.com). If I were to change my Microsoft Account password from another computer system or Outlook.com, the new password will not work when connecting over RDP. However, the old password will continue to authenticate successfully. This is both annoying and a security issue. Below is a method to force a password sync.
The easiest way to resolve this issue is to create a local administrator account (not a Microsoft account) and then use the local account to runas an application using your Microsoft account. If that sounds ridiculous, that’s because it is.
The instructions below assume a local (non-Microsoft) account is not currently accessible on the affected machine. A local account is required to resolve the issue.
net user /add [username] [password] net localgroup administrators [username] /add
runas /u:MicrosoftAccount\username@outlook.com cmd.exe
View Comments
You're a godsend. All these other posts out there about weird group policy shenanigans, but it's always password sync that's the real culprit it seems..
An aside that seems to be a slightly faster work around. Rather than logging on as the new user, one could use
runas ->new user cmd.exe
and that would give a command prompt to then run as the existing user and that seems to solve things.
Can´t believe it, this is ridiculous! So much time wasted and this is the only answer that works! thanks man, let me buy you a beer
Wow thanks! It was really messing up my day!
you are a thru hero, thanks a million, I had this problem for so long. I had to create an other user, but the could access app installed on my microsoft user.
THHHHHAAANKS.
Thank you! I had this problem too. I wouldn't have figured out how to fix it were it not for this article. Thanks!
Still working on 1909. Thanks!
And in regards to what shawn said above… the 'new' is also supposed to be 'net' just like the command before it.
Whoops! I forgot to fix that - all fixed. Thanks!
Thank you what a life saver and what a pain. BTW not sure why but I could not do the "new localgroup administrators [username] /add" part. It gave an error about New not being a valid command. I had to go into the user manager in windows and set it to an administrator. Then follow the rest of your steps
Thanks for the update. I'll check the commands to make sure they're correct.