Issues with Remote Desktop on Windows 11 after Update 22H2

I was having a nightmare with the RDP connection from a fully patched Windows 11 to a Windows 10 through a VPN, until I tried a combination of the articles on here.

First I added the fClientDisableUDP registry key and it did not work, then somebody suggested setting it to 0 and then back to 1, doing this, I was prompted for credentials and I thought it had worked, but still no joy!

I did the same again set it to 0 then rebooted and I then ran Remote Desktop Connection as an administrator, was prompted for credentials and it then connected!!!!

I then set the fClientDisableUDP back to 1 so that it continued to work.

After the initial connection was made, I could open the VPN and run RDC as normal not needing to elevate it again, so all is well again.

Thanks for the combination of suggestions!!

BIG UPDATE

The system worked after reboot for a few minutes and then reverted, so I chased delayed start services and by shutting down the Dell Optimiser service, I found it worked and if I started it again NO RDP!

Most of the people here report having RDP problems with Windows 11, BUT I am monitoring RDP issues with Windows 10 21H2 for the past 2 months.

• connections are droppin at random (sometimes 2 minutes apart, then few hours it is fine and then again 5-20 minute drops
• connections dropped were to direct IP, but also over VPN
• when RDP connection breaks, it can take a VPN connection with it. (KerioVPN, PPTP, IPSec all have issues)
• ping to WAN of the remote site is 100% fine and yet VPN/RDP does break.
• the issues are not related to the internet connection - I've seen it on multiple locations (ADSL, FTTH, FTTB)

The information gathered so far is that the client side connection simply stops providing data to the sever side which then drops the connection.

I am still trying to figure out more. I just applied the fClientDisableUDP = 1 fix and will see if it helps.

For those having trouble entering the fix - run CMD as admin and enter:

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f

I haven't started this yet, but I just went through the entire thread & copied all instructions I found and pasted them in a word doc. There was a 2nd post where someone gave the steps following steps.

Also, there was another post on steps to take if after you do this, you get a 204 ERROR.

Have to set this value to 1 in the registry for Windows 11 to work outside the network

Location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

KEY VALUE:  fClientDisableUDP SET TO 1

You need to right-click and create a new DWORD value called fClientDisableUDP

Then, change the actual value to 1. 

Restart the computer after you're done.

Best of luck to you & me right now...

& Thanks Microsoft.

I am getting the 204 error. I put the recommended fix in the registry and still getting the same error. Can anyone please help

Yes there id s RD Gateway. There is an RDS Farm, the Windows 11 build is already in the description 22H2.

The RD Gateway is Windows 2012. The problem is with the client, not the Gateway since all clients on all versions of windows 7,10,11 work except those with Windows 11 build 22H2.

That specific event path does not exist.