Issues with Remote Desktop on Windows 11 after Update 22H2

Anonymous

All of our Remote Desktop Users using Windows 11 are having problems connecting to Remote Desktop after installing this update. It just hangs at connecting.

We have found that there is a bug in the Remote Desktop client so that it is only trying the UDP connection and not trying TCP connection. We only allow the port 443 connection through on our firewall.

The only workaround we have found is to make the following change on the Windows 11 computer.

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

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

KEY VALUE - fClientDisableUDP SET TO 1

Otherwise the Remote client just keeps trying to connect via UDP.

This issue did not start until the Windows 11 update was installed over the last couple days.

Jeff

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

125 answers

Anonymous

2023-01-12T10:08:11+00:00

This fix worked for me in my upgraded Win11.

Now I can able to connect to remote server using RDC. Thank for the info..
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-10T17:51:58+00:00

The reg fix does not work for me- are there any other solutions to the W11 22H2 bug? In my case, the rdp connection just fails with the error "The login attempt failed" after a couple of seconds. (it does use an RD Gateway server.) I have also tried replacing the mstsc program files from a working windows 11 version- no change. It seems like there is another element to this bug that no one has addressed yet. I have all the recent windows 11 22h2 updates, and rdp has never worked (when traffic is via rd gateway server) since October!
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-28T14:37:45+00:00

As an FYI, this fix worked for me also. I would just get stuck on "Loading Virtual Machines" but with this Regedit it works just fine.

Just to add:

You're wanting to add a DWORD, call it fClientDisableUDP and change ITS value to 1.
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-08T16:03:03+00:00

Thanks Randall for the registry export solution.

But I still have to remotely restart the computer.

So far, I'm not able to remotely restart it.

If I RDP to one of my local network pc (Win10 Pro) and I try a "shutdown /m \IP_ADDRESS /r /f" from within an elevated prompt, I get an "access denied".

The pc I want to restart is not joined and only have one local user.

In the previous instance of this problem, I remember coming across an error message stating something to the effect that the local user had been used to many times. I didn't copy the actual error message because I had someone on site able to perform a physical hard reboot. After the reboot, the pc seemed to be back in working condition until a few days ago.

Is it possible that the problem we're facing is more a question of how many times we open/close a RDP session? As if the RDP sessions we close remain open in the background thus preventing new ones to be opened?
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-08T15:08:35+00:00

One way would be to create the fix on a different computer, then use the export function in the registry editor to export just that key, then get the export to the user if they have local admin rights they can just import the the fix then restart. That way they dont have to go into the registry.

I have a number of users having this issue where we use published apps that was my quick fix. Today i am going to look at using group policy to push the registry fix out as this has been going on for a while now.

Hope that helps make it easier.
Was this answer helpful?

0 comments No comments