Issues with Remote Desktop on Windows 11 after Update 22H2

Anonymous
2022-09-22T13:54:07+00:00

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

Windows for business | Windows Server | User experience | Remote desktop clients

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

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-02-10T15:36:39+00:00

    You have to create the KEY VALUE, then assign it a value.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-10T14:20:29+00:00

    You have to create the value. Right-click "New" and then select "DWORD Value".

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-02-10T14:15:18+00:00

    I did try to set the default value to 1 but that didn't work.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-02-10T14:14:14+00:00

    In the client file, I don't have the KEY VALUE - fClientDisableUDP . The first says (Default), the others start as fEnable

    Image

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-02-10T00:07:45+00:00

    Yup, confirming above - I have already had the Registry fix enabled since the issue first arose. Today a user contacted me to say it wasn't working again. When I tested I was getting the original error again. I had to toggle the fClientDisableUDP to 0 again - didn't work, back to 1 - started working again

    Come on MS - fix your stuff properly.

    Was this answer helpful?

    0 comments