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,