RDP Issue After System Update

Question

RDP Issue After System Update

Techloom ServiceDesk 0

Hello Microsoft Support,

I am experiencing an issue with Remote Desktop (RDP) on my Windows 11 Pro system.

On July 11, 2026, my computer installed Windows updates. Before the update, RDP was working perfectly without any issues. However, immediately after the update, RDP stopped working completely, and I have been unable to connect ever since.

A couple of important points:

My Windows updates are managed and deployed through Action1.

I have already uninstalled the latest update that I suspected was causing the issue, but the problem persists.

I have spent a considerable amount of time troubleshooting this issue and have already tried almost every solution I could find, including:

Checking Windows Firewall settings.

Uninstalling and reinstalling the antivirus software.

Applying the recommended registry changes from Microsoft's documentation.

Deleting and allowing Windows to recreate the Remote Desktop certificate.

Following numerous troubleshooting guides and recommendations available online.

The only solution I have not attempted is reinstalling Windows, as I would like to avoid that if at all possible.

I would greatly appreciate your assistance in identifying the root cause of this issue and recommending any additional troubleshooting steps or known fixes.

Thank you for your time and support.

Kind regards,

0 comments

2 answers

Your answer

Answer 1

Hello Harry,

Thank you for your response.

I have already performed the troubleshooting steps you suggested.

The Remote Desktop Services (TermService) service is running normally.
The system is not listening on TCP port 3389, even though Remote Desktop is enabled.
I checked the TerminalServices-RemoteConnectionManager and TerminalServices-LocalSessionManager event logs, but I could not find any events that explain why the RDP listener is not being created.
I also tested disabling the RDP UDP transport and forcing RDP to use TCP only, but the issue remained the same.

In addition, I have already:

Uninstalled the Windows update that appears to have triggered the issue.
Checked Windows Firewall settings.
Completely removed and reinstalled the antivirus software.
Applied the recommended registry changes.
Recreated the RDP certificate.
Ran both SFC and DISM, which completed successfully with no integrity violations.
Verified that all required Remote Desktop services are running.

The error I receive is:

"Remote Desktop can't connect to the remote computer."

The issue started immediately after the Windows update. Although I removed the update, the problem persists.

Since the RDP service is running but no listener is created on TCP port 3389, could you please advise what component or service is responsible for creating the RDP listener and what additional diagnostics I can perform? I would like to resolve this issue without reinstalling Windows.

Thank you for your assistance.

Kind regards,

Answer 2

Hello!

Since RDP stopped working immediately after a Windows update and uninstalling the update did not help, I would focus on validating whether the issue is with the RDP service, listener, or transport layer, rather than the update itself. Recent Windows 11 updates have introduced RDP transport and security changes that may persist even after rollback.

Please verify that Remote Desktop Services (TermService) is running and that the system is listening on TCP 3389:

sc query termservice

netstat -ano | findstr :3389

Also check the Event Viewer under Applications and Services Logs > Microsoft > Windows > TerminalServices-RemoteConnectionManager and TerminalServices-LocalSessionManager for errors at the time of a connection attempt.

If the service is running but connections still fail, a worthwhile test is to temporarily disable RDP UDP transport and force RDP to use TCP only, as several RDP issues after Windows 11 updates have been linked to the UDP transport layer.

To identify the root cause, please provide the exact RDP error message and the results of the commands above, especially whether TCP port 3389 is listening and whether Event Viewer logs any Terminal Services errors during a connection attempt.

Harry.