the specified path (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
KEY VALUE - fClientDisableUDP SET TO 1 ) is not available
is there any other work around?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
the specified path (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
KEY VALUE - fClientDisableUDP SET TO 1 ) is not available
is there any other work around?
Well,
After my fix working for about a month, I've completely lost remote desktop for a second time. This time it doesn't even work on the network level. This is incredibly frustrating.
Hi everyone and hello Jeff,
I seem to have the same issue, though a bit different, where RDP takes forever to connect but end up with error code 0x10b.
The message starts with "The connection to the remote computer was lost, possibly due to network connectivity problems. ...".
I'm actually away from home working on a Win11 Home 22H2 laptop connected via RDP with 5 different pcs at home.
1 is Win Server 2012 R2 and host the RD Gateway Server. No problem to connect.
3 are Win10 22H2. No problem to connect.
1 is Win11 Pro 22H2 and has stopped working.
The pcs are not joined to the domain.
I'm saying "has stopped", because I was able to RDP to the Win11 Pro 22H2 computer over the past 2 weeks.
In the beginning, I was able to RDP the pc but it stopped responding to RDP after a week with the error code 0x10b.
I tried to remotely restart the pc from another pc on the local network via RDP, but constantly got access denied.
So I asked a friend to enter my home and perform a hard reset on the pc.
Once rebooted, I was able to RDP to this Win11 Pro 22H2 pc, again for another week.
I can always call my friend again, but I prefer not unless it's absolutely neccessary.
In order to modify the files or registry, I need access to the pc.
How can I do that remotely?
Via RDP, I have access to all other pcs on my local network.
As I said, I tried to remotely restart the pc but got access denied.
Anyone has a solution to suggest?
Thanks
Thank you for this. You saved my work day!
I have the same issue. I purchased the windows 11pro online yesterday. Could microsoft not at least acknowledge receipt of
payment and inform me that it has or will be downloaded?