SOLVED

Unable to connect via RDP with Microsoft Account

Copper Contributor

Hello,

I have a computer with a clean install of Windows 10 22H2 build 19045.4123.
There is one local user account and one user with a Microsoft account on the computer. Both of these users have admin rights, and RDP connections are also explicitly enabled for both.
The user with the local account connects to the computer using RDP without any problems, but the user with the Microsoft account cannot connect - the system responds "The logon attempt failed", but the username and password for the Microsoft account are entered without error.

Any ideas what is wrong and how to fix it?

 

8 Replies
best response confirmed by Tomas_Chylik (Copper Contributor)
Solution

@Tomas_Chylik 

If anyone has run into the same problem, I have found that a user with a Microsoft account has never logged into the computer with a password. The first time he logged in with Microsoft Authenticator and then used his PIN each time.
So the solution was to log this user on the remote computer using the password first.
The RDP connection to the Microsoft Accoun account is then fully functional.

To ensure that Windows 10 Enterprise only uses the C: system drive for installations, you can modify the default installation settings by following these steps:

Create a backup: Before making any changes, it's essential to create a backup of your important data. Modifying system settings can be risky, so having a backup will help in case anything goes wrong.

Verify current drive configuration: Open the Disk Management tool by pressing Windows key + X and selecting "Disk Management." Ensure that the C: drive is labeled as the System partition and contains the Windows installation, while other drives are labeled as Data partitions.

Set default installation drive: Open the Settings app by pressing Windows key + I and navigate to "System" > "Storage." Under the "More storage settings" section, click on "Change where new content is saved." Set the default installation drive to C: by selecting it for each category (Apps, Documents, Music, Pictures, etc.). This will ensure that new installations are directed to the C: drive.
I'm afraid this answer has nothing to do with the original problem - the impossibility of RDP connection using Microsoft Account. Maybe it should have been put in another thread
Thank you for your reply.

In my original post I stated that while a user with MicrosoftAccount cannot connect, a user with a local account can connect without any problem.
Therefore, the problem is not a broken RDP and this general advice about RDP is not relevant to solve this problem.
However, I have stated in another message that I have already solved the problem - In order for a user with a Microsoft account to log in with a Microsoft account password to be functional, it is absolutely necessary that the user logs in at least once on that computer with the Microsoft account password. If the user logs on to the computer using Windows hello/PIN only and never logs on to the computer using the Microsoft account password, then the connection using RDP and the Microsoft account password is not functional
Thomas's suggestion worked fine on my Windows 11 laptop as well, thank you

I confirm that this solution works as it worked perfectly for me.

 

I've been (not actively) trying to get RDP work since last year but couldn't. Gave one last attempt before switching to Chrome Remote Desktop and came across this thread. Thank you so much, Tomas!

Hi@Tomas_Chylik 

 

thanks for sharing your solution but it didn't work for me. Actually the user has logged in many times before I connected via Remote Desktop client.

Also I tried with a local account and it works.

 

The solution instead, can be to put a \ before the username. This works.

1 best response

Accepted Solutions
best response confirmed by Tomas_Chylik (Copper Contributor)
Solution

@Tomas_Chylik 

If anyone has run into the same problem, I have found that a user with a Microsoft account has never logged into the computer with a password. The first time he logged in with Microsoft Authenticator and then used his PIN each time.
So the solution was to log this user on the remote computer using the password first.
The RDP connection to the Microsoft Accoun account is then fully functional.

View solution in original post