Windows 11 24H2 has issues with RDP after recent updates

There's a reported issue in Windows 11 24H2 where Remote Desktop Protocol (RDP) sessions fail to work properly after logging in. It's not yet known what exactly causes the bug. Some users blame recent security patches, such as KB5050094 and KB5051987. These updates seem to have introduced changes that affect how RDP interacts with the network.

RDP allows users to remotely control another computer, which is commonly used by businesses for managing physical or virtual machines. Despite the RDP service running correctly and firewall settings being properly configured, some 24H2 systems are unable to maintain or establish these remote connections.

During testing, it was observed that even though the RDP service appears active in the Services manager and network tests are successful, the connection still fails. Multiple users have encountered this issue, with some mitigating the bug by changing the default RDP port number from 3389 to another value. However, this solution doesn't resolve the problem for everyone.

Another common issue involves RDP sessions freezing during the login process, especially when reconnecting to a previously disconnected session. Users report seeing a "please wait" message or experiencing a frozen interface at the top of the screen.

In some cases, users can initially connect successfully. But everything will freeze shortly afterward. Reconnecting becomes problematic, with the system getting stuck on a "spinning wheel" or displaying an "other user" message. The only workaround in such cases is to log in again with a different account or have an administrator intervene to reset the session.

Fix RDP in Windows 11 version 24H2

To address this issue you need to change the following Group Policy settings. If you are affected, navigate to gpedit.msc > Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. Here, you'll find an option labeled "Select network detection on the server."

You need to enable this policy and set it to turn off both Connect Time Detect and Continuous Network Detect. Applying these changes doesn't require a system restart; instead, running the command gpupdate /force will apply the updated policies. Some users have found that disabling Continuous Network Detect is sufficient to fix the issue.

Method 2: Using a batch file and Registry tweak

Alternatively, you can create the following batch file:

@echo off

:: Set the registry values
reg add "HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services" /v fServerNetworkDetect /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services" /v fTurnOffTimeDetect /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services" /v fTurnOffNetworkDetect /t REG_DWORD /d 1 /f

:: Update group policy
gpupdate /force
echo Done.

pause

How to Use the Batch File

1. Open a text editor (e.g., Notepad).
2. Copy and paste the above code into the editor.
3. Save the file with a .bat extension, such as SetRDPRegistry.bat.
4. Run the batch file as an administrator to ensure it has the necessary permissions to modify the registry.

You are done. This batch file achieves the same functionality as the original Group Policy tool, but uses the REG.EXE tool instead.

Source

Support us

Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options: