RDP session disconnecting after 1 minute and 5 seconds

Question

RDP session disconnecting after 1 minute and 5 seconds

Minuano 20

Hello, I'm trying to make an RDP connection between a Windows 11 24H2 and a Windows Server 2012 Standard and a disconnection occurs every 1 minute and 5 seconds, approximately.

I noticed that if I force the client to connect via TCP by inserting the fClientDisableUDP key with a value of 1 in the registry "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" the problem disappears.

In the client's event viewer I find the following messages:

RDP ClientActiveX disconnected (Reason=2308)
Multitransport connection disconnected.
The server is using version 0x80004 of the RDP graphical protocol (client mode: 0, AVC available: 0).
The client is using hardware memory for the frame buffer.
The client has established a multitransport connection with the server.
The server supports SSL = supported
Connected to domain (SRVXXX) with session 2.
RDP ClientActiveX disconnected (Reason=263)
RDPClient_SSL: Error transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to TsSslEventHandshakeContinueFailed (error code 0x80004005)

I can't find anything in the server's event viewer regarding RDP connection problems with the server.

Any tips on what might be happening?

Pierre-Yves Andri 20 Reputation points

2025-02-21T19:06:33.1066667+00:00

I have been experiencing exactly the same issue for the past few days, from a Windows 11 24H2 to a Windows Server 2012 R2. The connection drops after a little over a minute and automatically restores itself within 5 seconds. I added a DWORD value fClientDisableUDP with a value of 1, as mentioned earlier. And it works perfectly. I didn't investigate further. A warm thank you to Minuano.
Davis Best 5 Reputation points

2025-02-21T19:55:29.67+00:00

Can confirm the fClientDisableUDP did fix the issue. I tried all other methods to disable UDP and non worked except this one. Windows 11 RDP to 2012R2. Also can confirm that this is happening on multiple windows 11 machines, so the issue must be on Microsoft's side
Mario Giannini 0 Reputation points

2025-02-22T15:27:04.7366667+00:00

Same issue here, and the fClientDisableUDP fix resolved the issue.

For more background, I am using ProxMox in order to test Windows 2012 server upgrades and MobaXterm as my RDP client. The last time I tried this all seemed to work fine, but trying again for another client has all the Win2012 machines disconnecting.

I implemented the fClientDisableUDP fix on my Win11 machine, and also set each Win2012 server firewall to block UDP 3389, just in case.

I stumbled through numerous and multiple recomendations to check group policies, timeouts, Remote licenses, and so on, but the fClientDisableUDP was the fix for me.

Thanks for your post.
Glen Palmer 0 Reputation points

2025-03-12T19:44:46.11+00:00

If you used the Registry hack to allow your Remote Desktop to connect, then that is fine - however it's a bit of a dangerous change if you have to get multiple people in the company to make the change.

The solution, we found, is a lot easier - and you just need to create a step-by-step guide (or video) for your staff to follow.

All the people we found that are having this issue, especially after 24H2 updates, are using the legacy Remote Desktop app (we were included in that group) - the one that appears like this in your start menu

In order to fix the issue without any changes to the registry, go to the Microsoft Store and install the latest Remote Desktop App from Microsoft. This is the one with the red icon.

Once we started using the new app, the issue did not exist any longer.

3 answers

Your answer

Pierre-Yves Andri 20 Reputation points

2025-02-21T19:06:33.1066667+00:00

I have been experiencing exactly the same issue for the past few days, from a Windows 11 24H2 to a Windows Server 2012 R2. The connection drops after a little over a minute and automatically restores itself within 5 seconds. I added a DWORD value fClientDisableUDP with a value of 1, as mentioned earlier. And it works perfectly. I didn't investigate further. A warm thank you to Minuano.
Davis Best 5 Reputation points

2025-02-21T19:55:29.67+00:00

Can confirm the fClientDisableUDP did fix the issue. I tried all other methods to disable UDP and non worked except this one. Windows 11 RDP to 2012R2. Also can confirm that this is happening on multiple windows 11 machines, so the issue must be on Microsoft's side
Mario Giannini 0 Reputation points

2025-02-22T15:27:04.7366667+00:00

Same issue here, and the fClientDisableUDP fix resolved the issue.

For more background, I am using ProxMox in order to test Windows 2012 server upgrades and MobaXterm as my RDP client. The last time I tried this all seemed to work fine, but trying again for another client has all the Win2012 machines disconnecting.

I implemented the fClientDisableUDP fix on my Win11 machine, and also set each Win2012 server firewall to block UDP 3389, just in case.

I stumbled through numerous and multiple recomendations to check group policies, timeouts, Remote licenses, and so on, but the fClientDisableUDP was the fix for me.

Thanks for your post.
Glen Palmer 0 Reputation points

2025-03-12T19:44:46.11+00:00

If you used the Registry hack to allow your Remote Desktop to connect, then that is fine - however it's a bit of a dangerous change if you have to get multiple people in the company to make the change.

The solution, we found, is a lot easier - and you just need to create a step-by-step guide (or video) for your staff to follow.

All the people we found that are having this issue, especially after 24H2 updates, are using the legacy Remote Desktop app (we were included in that group) - the one that appears like this in your start menu

In order to fix the issue without any changes to the registry, go to the Microsoft Store and install the latest Remote Desktop App from Microsoft. This is the one with the red icon.

Once we started using the new app, the issue did not exist any longer.

Answer 1

Minuano 20

Apparently, removing the KB5051987 and KB5050094 updates solves the problem temporarily.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 2

Keep Using TCP (Quick Fix) thats probably why is working for you

Since disabling UDP (fClientDisableUDP = 1) works, you can consider keeping this setting as a permanent fix. However, this might slightly increase latency in certain environments.

Test UDP Connectivity

If you want to diagnose the UDP issue rather than just switch to TCP, try the following:

Run a network test using PowerShell:

powershell
CopyEdit
Test-NetConnection -ComputerName <server_IP> -Port 3389 -UDP

If the test fails, it confirms a UDP connectivity problem.

Check for packet loss using pathping:

cmd
CopyEdit
pathping <server_IP>

Look for high packet loss on intermediary network nodes.

Review Windows Server 2012 RDP Settings

On the server:

Open Group Policy Editor (gpedit.msc) Go to:

rust
CopyEdit
Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections

Ensure “Allow Remote Desktop connections only with Network Level Authentication” is enabled.
- Ensure “Select RDP transport protocols” is set to Use both TCP and UDP.

Restart the Remote Desktop Services:

 cmd
 CopyEdit
 net stop termservice /y

If your network has a firewall, VPN, or proxy, ensure it allows UDP traffic on port 3389.
If there’s a router doing aggressive NAT or session timeouts, try extending UDP session timeout values.

Keep Using TCP (Quick Fix)

Since disabling UDP (fClientDisableUDP = 1) works, you can consider keeping this setting as a permanent fix. However, this might slightly increase latency in certain environments.

2. Test UDP Connectivity

If you want to diagnose the UDP issue rather than just switch to TCP, try the following:

Run a network test using PowerShell:

    powershell
    CopyEdit
    Test-NetConnection -ComputerName <server_IP> -Port 3389 -UDP

If the test fails, it confirms a UDP connectivity problem.

Check for packet loss using pathping:
```
    cmd
    CopyEdit
    pathping <server_IP>
```
Look for high packet loss on intermediary network nodes.

3. Review Windows Server 2012 RDP Settings

On the server:

Open Group Policy Editor (gpedit.msc)
Go to:

  rust
  CopyEdit
  Computer Configuration

Ensure “Allow Remote Desktop connections only with Network Level Authentication” is enabled.
Ensure “Select RDP transport protocols” is set to Use both TCP and UDP.

Restart the Remote Desktop Services:

    cmd
    CopyEdit
    net stop termservice /y

If your network has a firewall, VPN, or proxy, ensure it allows UDP traffic on port 3389.
If there’s a router doing aggressive NAT or session timeouts, try extending UDP session timeout values.Keep Using TCP (Quick Fix) thats probably why is working for you Since disabling UDP (fClientDisableUDP = 1) works, you can consider keeping this setting as a permanent fix. However, this might slightly increase latency in certain environments.
1. Test UDP Connectivity
If you want to diagnose the UDP issue rather than just switch to TCP, try the following: Run a network test using PowerShell:
```
    powershell
    CopyEdit
    Test-NetConnection -ComputerName <server_IP> -Port 3389 -UDP
```
If the test fails, it confirms a UDP connectivity problem. Check for packet loss using pathping:
```
    cmd
    CopyEdit
    pathping <server_IP>
```
Look for high packet loss on intermediary network nodes.
1. Review Windows Server 2012 RDP Settings
On the server: Open Group Policy Editor (gpedit.msc) Go to:
```
    rust
    CopyEdit
    Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections
```
- Ensure “Allow Remote Desktop connections only with Network Level Authentication” is enabled.
  - Ensure “Select RDP transport protocols” is set to Use both TCP and UDP. Restart the Remote Desktop Services:
```
         cmd
         CopyEdit
         net stop termservice /y
```
```
         
```
- If your network has a firewall, VPN, or proxy, ensure it allows UDP traffic on port 3389.
- If there’s a router doing aggressive NAT or session timeouts, try extending UDP session timeout values. Keep Using TCP (Quick Fix) Since disabling UDP (fClientDisableUDP = 1) works, you can consider keeping this setting as a permanent fix. However, this might slightly increase latency in certain environments. 2. Test UDP Connectivity If you want to diagnose the UDP issue rather than just switch to TCP, try the following:
  - Run a network test using PowerShell:
```
```powershell
    powershell
    CopyEdit
    Test-NetConnection -ComputerName <server_IP> -Port 3389 -UDP
```

If the test fails, it confirms a UDP connectivity problem.
```
  - Check for packet loss using pathping:
```
```yaml
    cmd
    CopyEdit
    pathping <server_IP>
```

Look for high packet loss on intermediary network nodes.
```
    3. Review Windows Server 2012 RDP Settings On the server:
  - Open Group Policy Editor (gpedit.msc)
    Go to:
```
          rust
          CopyEdit
          Computer Configuration 
```
  - Ensure “Allow Remote Desktop connections only with Network Level Authentication” is enabled.
  - Ensure “Select RDP transport protocols” is set to Use both TCP and UDP.
  - Restart the Remote Desktop Services:
```
```yaml
    cmd
    CopyEdit
    net stop termservice /y
```


```
    
```
```
  - If your network has a firewall, VPN, or proxy, ensure it allows UDP traffic on port 3389.
  - If there’s a router doing aggressive NAT or session timeouts, try extending UDP session timeout values.

Minuano 20 Reputation points

2025-02-19T19:29:24.52+00:00

Hello,

There is no firewall/router/nat between the client and the server.

Both the client and the server are on the same network.

There is no packet loss

RDP transport protocols are set to both TCP and UDP

The "Allow Remote Desktop connections only with Network Level Authentication" option is enabled

I found another message in the client event viewer:

RDPClient_SSL: Error transitioning from TsSslStateHandshakeInProgress to TsSslStateDisconnecting in response to TsSslEventHandshakeContinueFailed (error code 0x80004005).
John Lim 0 Reputation points

2025-03-12T16:05:24.3366667+00:00

I have the fClientDisableUDP in my registry but still getting disconnected, I'm not gettign disconnected when I logged in as administrator though. Help!
vinixwu 41 Reputation points

2025-03-27T03:38:56.0433333+00:00

Hi Jose Benjamin Solis Nolasco,

Your post seems like copied from the response of ChatGPT or other LLM directly.

There is no -UDP parameter for Test-NetConnection.

Enabling "Allow Remote Desktop connections only with Network Level Authentication" policy may block connections to servers without SSL certificate or kerberos and hense cause another problem.

There are "<language><Line Break>CopyEdit" in every Inline Code block.

Please check your answer, you will find there are more problems.

Back to the problem itself, set fClientDisableUDP = 1 solved mine, and all other suggestions I found are failed.

Answer 3

vinixwu 41

According to revision history of cumulative updates, this problem seems solved since KB5052093:

[Remote Desktop]
Fixed: There are display rendering issues when you connect to certain PCs.
- Fixed: It stops responding.

The latest cumulative update on my PC is KB5053598. The problem didn't happen after I removed fClientDisableUDP and Group Policy.

Share via

RDP session disconnecting after 1 minute and 5 seconds

3 answers

Your answer