Remote Desktop Connection failure in Win11 24H2

I have a brand new Beelink AMD computer with Windows 11 Pro installed (24H2). I am trying to use Remote Desktop Connection from another Windows 11 Pro (24H2) computer and it fails to open a session due to “Your credentials did not work”. Both computers are installed under my Microsoft account. It makes no difference if I use the computer name or the IP address.

I am using the computer name BLUEIRIS, which is the name I assigned to the remote computer. It is also in the HOME domain and is the same as the local computer. I can ping the remote from the local computer, so I have verified network connections.

I have Remote Desktop services enabled and set to automatically start. I even disabled the request for credentials in the Group Policy Editor. I also have network discovery turned on.

The Windows Defender firewall has a rule allowing RDP connections through port 3389.

What is interesting is that I can remote into another computer, which is running Windows 11 Pro (23H2). There are no Windows credentials on the remote computer. This must be a bug in 24H2.

Are there recommended fixes to this problem? I have updated Windows to the latest update available.

Thanks
Dale

DaleC said:

I have a brand new Beelink AMD computer with Windows 11 Pro installed (24H2). I am trying to use Remote Desktop Connection from another Windows 11 Pro (24H2) computer and it fails to open a session due to “Your credentials did not work”. Both computers are installed under my Microsoft account. It makes no difference if I use the computer name or the IP address.

Click to expand...

The credentials you are using are for an account on the remote computer you're trying to connect to. Have you made the account on the Beelink a member of the Remote Desktop Users group? This is essential, else the connection will be rejected.

Bree said:

The credentials you are using are for an account on the remote computer you're trying to connect to. Have you made the account on the Beelink a member of the Remote Desktop Users group? This is essential, else the connection will be rejected.

View attachment 147692

Click to expand...

Has this changed? I've never had to set up an account on the remote computer before and it always worked.

If you cloned your main computer to the new one by restoring a system image and didn't change the machine SID, as of the September Patch Tuesday, RDP and networking (shares) will no longer work between the two computers. You'll be able to ping them from one another, but the other stuff fails. I ran into this myself, and there are a couple of threads on it.

Also, see this thread for a solution to RDP connection errors stemming from "Windows Credentials Guard":


I added this article to my OneNote in March 2023, which means it solved that problem for me back then.

barreleye said:

If you cloned your main computer to the new one by restoring a system image and didn't change the machine SID, as of the September Patch Tuesday, RDP and networking (shares) will no longer work between the two computers. You'll be able to ping them from one another, but the other stuff fails. I ran into this myself, and there are a couple of threads on it.

Also, see this thread for a solution to RDP connection errors stemming from "Windows Credentials Guard":

"Windows Defender Credential Guard does not allow using saved credentials" for RDP connections?

Recently when running a Remote Desktop Connection under this Windows version OS Name Microsoft Windows 11 Pro Version 10.0.22621 Build 22621 Other OS Description Not Available OS Manufacturer

superuser.com

I added this article to my OneNote in March 2023, which means it solved that problem for me back then.

Click to expand...

I did not clone my main computer to the new one. The new one is a brand new BeeLink with a fresh install of Windows 11 Pro. I am still confused as to what credentials it is looking for.

Bree said:

The credentials you are using are for an account on the remote computer you're trying to connect to. Have you made the account on the Beelink a member of the Remote Desktop Users group? This is essential, else the connection will be rejected.

View attachment 147692

Click to expand...

Where does the Access and Owner come from? My remote computer shows nothing for members of the Remote Desktop Users

DaleC said:

Where does the Access and Owner come from? My remote computer shows nothing for members of the Remote Desktop Users

Click to expand...

Access and Owner are just the names of two of the accounts on my remote computer, accounts that I have added to the Remote Desktop Users group. If you want to connect to a remote computer the account you connect with must be a member of the Remote Desktop Users group on that remote computer. If it is not, you will see this....

DaleC said:

The new one is a brand new BeeLink with a fresh install of Windows 11 Pro. I am still confused as to what credentials it is looking for.

Click to expand...

The credentials it needs are the name and password of a valid account on that Beelink computer. To be valid for remote connections, the account must have a password (RDP does not allow connections to accounts with a blank password) and the account must be a member of the Remote Desktop Users group.

Bree said:

The credentials it needs are the name and password of a valid account on that Beelink computer. To be valid for remote connections, the account must have a password (RDP does not allow connections to accounts with a blank password) and the account must be a member of the Remote Desktop Users group.

Click to expand...

Okay, I set up an account on the Beelink and put it in the Remote Desktop User group. I can now connect to it from my local desktop, however, all my settings that I had configured on the BeeLink are non existant including some apps I installed.

Microsoft really messed this one up. It used to be so simple and now I've blown an entire day and not where I want to be.

DaleC said:

Okay, I set up an account on the Beelink and put it in the Remote Desktop User group. I can now connect to it from my local desktop, however, all my settings that I had configured on the BeeLink are non existant including some apps I installed.

Click to expand...

If you created a new account, then the settings you see will be those of the new account, not those for your original account you set it up with.

Have you tried adding the original account to the Remote Desktop Users group?

Bree said:

If you created a new account, then the settings you see will be those of the new account, not those for your original account you set it up with.

Have you tried adding the original account to the Remote Desktop Users group?

Click to expand...

It said it was already part of the Remote Desktop Users group, but when I tried to login with it I got the failure message. However, I figured out how to get into that account and saw that the password fields were blank (I know at one time you could leave the password blank, but apparently Microsoft closed that up). I added the password to the original account and tried the remote connection and this time it worked! So I will go back and remove the other account I created since it is no longer going to be used.

Thank you for your help!

Dale

DaleC said:

I added the password to the original account and tried the remote connection and this time it worked! So I will go back and remove the other account I created since it is no longer going to be used.

Thank you for your help!

Click to expand...

Good news!

I would leave the second account. You never knows when you may need another way in. I always create a second local admin account on all my PCs, just in case. I may never need to use it, but it's nice to know it's there if I need it.