Windows 10: RDP between two windows 10 21H2 machines fails

I have two Windows 10 Pro 21H2 machines a laptop and a desktop. I have always been able to RDP from the laptop to the desktop without a problem until I installed the 21H2 update. After the update, I get the message: "The credentials that were used to connect to DESKTOP_NAME did not work. Please enter new credentials." Has anyone else had this problem with RDP between two 21H2 machines?After every windows update is installed, I had always gotten a "warning" that the credentials for the machine I was connecting to had changed and I've always assumed this had to do with the OS update, but I wa

:)

 

Windows 10 fails to update


When you finish testing the Avast suggestion, make sure that you restart your machine.

Then if the issue persists, please return to the trouble shooting list in post# 89

I think there are three steps that remain; the WU troubleshooter, reset WU components, and manual WU reset.

 

Slow RDP connection to host machine after updates

Hello,



Thank you for writing to Microsoft Community Forums.



I understand that the RDP connection to the host machine is slow after the updates.



As the issue is related to RDP connection on Virtual Machines, I suggest you to post your query on

TechNet forums, where we have experts who have more knowledge on Virtual Machines and RDP connections.



Hope it helps.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

RDP: failed to reconnect to your remote session after creators update

Hi Guys,

After the creators update last week, i'm unable to reconnect using RDP.

I'm able to login in once via RDP. When i reconnect, the RDP client just gives the error: Failed to reconnect to your remote session.

On the target machine, a corresponding error is logged in the event viewer:

Event-ID: 4005 (qualifier: 49152)

Message: The Windows log-on process has unexpectedly terminated.

I'm able to physically login on the target machine, so it seems something practically wrong with RDP.

Currently the machine is running version 1703 (build 15063.483) win 10 pro

I’ve seen some posts with similar issues, which suggest following resolutions

- to reset the font-scaling to 100% (as I’m running on 150%)

- disable new loginUI via the registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\TestHooks\Threshold=0 (which didn’t exist). Also tried adding the key DUIMode=0
and disabling XamlCredUIAvailable

But unfortunate none of these suggestions seem to resolve the issue.

I’ve also contact Support, which suggested to run a windows repair, which seems a last resort, and provides no guarantees this issue will be resolved. For reference they gave me this id: 1393780111

Any suggestions are appreciated. If any important info is missing, please ask.

Thanks Olaf

***Post moved by the moderator to the appropriate forum category.***