Windows 11 has encountered a notable issue affecting Remote Desktop Protocol (RDP) sessions, particularly during the login phase. The root cause remains uncertain, with speculation surrounding the Windows 11 24H2 base release or two recent security updates, KB5050094 and KB5051987. These updates have raised questions about the functionality of RDP sessions in the latest version of the operating system, likely tied to its network handling capabilities.
Since the rollout of the Windows 11 24H2 update, numerous administrators have reported complications with establishing RDP connections. For those unfamiliar, RDP allows users to control a computer remotely, a feature predominantly utilized by enterprises for managing Windows installations on both physical PCs and virtual machines. However, post-update, many systems are experiencing difficulties in initiating RDP connections.
In tests conducted by Windows Latest, it was observed that RDP connections fail to establish even when the RDP service is operational. Users can verify the service status through the built-in Services manager. Interestingly, this issue persists despite proper firewall configurations and successful connectivity tests, such as ping commands executed in the command prompt.
Feedback from users indicates that they are not alone in facing these challenges. One Reddit user shared their experience with two identical PCs from the same manufacturer, both running the same Windows 11 Pro 24H2 update, yet only one could successfully connect via RDP. They discovered that changing the default RDP port from 3389 to another number resolved their issue, although this workaround is not universally effective.
Further complicating matters, reports have surfaced detailing another bug where RDP sessions hang during the login process. Users experiencing this issue often find their sessions freezing or hanging, particularly when attempting to reconnect to previously disconnected sessions. One user recounted a scenario where their connection appeared stable until the session unexpectedly froze, displaying a “please wait” screen or a non-responsive top bar.
These problems seem to stem from the way Windows 11 24H2 manages network detection. As one user pointed out, their team has encountered similar issues where users could connect initially, but if the session dropped, they faced difficulties reconnecting. The only solutions appeared to involve logging onto the PC with a different account or having an administrator intervene.
How to fix Windows 11 24H2’s RDP issues
To address the hanging issue when reconnecting to disconnected RDP sessions in Windows 11 24H2, users can make adjustments through the Group Policy Editor:
- Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
- Open Select network detection on the server.
- Set this policy to Enabled, and select Turn off Connect Time Detect and Continuous Network Detect.
A system reboot is not necessary to apply these Group Policy changes, but executing the gpupdate /force command is recommended. Some users have reported that simply disabling Continuous Network Detect suffices to resolve the issue.
For those who prefer a Windows Registry solution to automate the process across multiple devices running Windows 11 24H2, the following script can be utilized:
# Define registry path
$RegPath = "HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal Services"
Ensure the registry path exists
if (!(Test-Path $RegPath)) {
New-Item -Path $RegPath -Force | Out-Null
}
Set the registry values
Set-ItemProperty -Path $RegPath -Name "fServerNetworkDetect" -Type DWord -Value 1
Set-ItemProperty -Path $RegPath -Name "fTurnOffTimeDetect" -Type DWord -Value 1
Set-ItemProperty -Path $RegPath -Name "fTurnOffNetworkDetect" -Type DWord -Value 1
Confirm changes
Write-Host "Network detection policies applied. A reboot may be required for changes to take effect.
To implement the Registry script, simply open Notepad, save the content with a .reg extension, and execute the script.
As of February 21, Microsoft has yet to officially acknowledge the network issues associated with Windows 11 24H2, despite the fact that these problems are impacting a significant number of users. Observations from Windows Latest suggest that implementing the aforementioned changes can restore RDP functionality in Windows 11 24H2. Users are encouraged to share their experiences in the comments should they continue to encounter difficulties.
Windows 11 24H2 RDP hangs on login, RDP session connecting issues reported
Windows 11 has encountered a notable issue affecting Remote Desktop Protocol (RDP) sessions, particularly during the login phase. The root cause remains uncertain, with speculation surrounding the Windows 11 24H2 base release or two recent security updates, KB5050094 and KB5051987. These updates have raised questions about the functionality of RDP sessions in the latest version of the operating system, likely tied to its network handling capabilities.
Since the rollout of the Windows 11 24H2 update, numerous administrators have reported complications with establishing RDP connections. For those unfamiliar, RDP allows users to control a computer remotely, a feature predominantly utilized by enterprises for managing Windows installations on both physical PCs and virtual machines. However, post-update, many systems are experiencing difficulties in initiating RDP connections.
In tests conducted by Windows Latest, it was observed that RDP connections fail to establish even when the RDP service is operational. Users can verify the service status through the built-in Services manager. Interestingly, this issue persists despite proper firewall configurations and successful connectivity tests, such as ping commands executed in the command prompt.
Feedback from users indicates that they are not alone in facing these challenges. One Reddit user shared their experience with two identical PCs from the same manufacturer, both running the same Windows 11 Pro 24H2 update, yet only one could successfully connect via RDP. They discovered that changing the default RDP port from 3389 to another number resolved their issue, although this workaround is not universally effective.
Further complicating matters, reports have surfaced detailing another bug where RDP sessions hang during the login process. Users experiencing this issue often find their sessions freezing or hanging, particularly when attempting to reconnect to previously disconnected sessions. One user recounted a scenario where their connection appeared stable until the session unexpectedly froze, displaying a “please wait” screen or a non-responsive top bar.
These problems seem to stem from the way Windows 11 24H2 manages network detection. As one user pointed out, their team has encountered similar issues where users could connect initially, but if the session dropped, they faced difficulties reconnecting. The only solutions appeared to involve logging onto the PC with a different account or having an administrator intervene.
How to fix Windows 11 24H2’s RDP issues
To address the hanging issue when reconnecting to disconnected RDP sessions in Windows 11 24H2, users can make adjustments through the Group Policy Editor:
A system reboot is not necessary to apply these Group Policy changes, but executing the gpupdate /force command is recommended. Some users have reported that simply disabling Continuous Network Detect suffices to resolve the issue.
For those who prefer a Windows Registry solution to automate the process across multiple devices running Windows 11 24H2, the following script can be utilized:
To implement the Registry script, simply open Notepad, save the content with a .reg extension, and execute the script.
As of February 21, Microsoft has yet to officially acknowledge the network issues associated with Windows 11 24H2, despite the fact that these problems are impacting a significant number of users. Observations from Windows Latest suggest that implementing the aforementioned changes can restore RDP functionality in Windows 11 24H2. Users are encouraged to share their experiences in the comments should they continue to encounter difficulties.