This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 31%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJG%3C/text%3E%3C/svg%3E)
Hi:
I have a Windows 11 Pro machine version 23H2 where the service 'Remote Desktop Services' (TermService) is running but when I run >netstat -a -o there are no listeners for port 3389. Windows Remote desktop is turned on and Windows reports the Remote desktop port is 3389. All firewalls on the machine are turned off.
Any suggestion appreciated, thanks
Run this from an admin powershell prompt and see if termservice is listening on any port.
$termsvc = Get-CimInstance -Class Win32_Service -Filter 'Name="Termservice"' | Select Name, ProcessID
$listen = Get-NetTCPConnection | Where-Object {$_.OwningProcess -eq $termsvc.processid} | select LocalAddress, Localport
"{0} is pid {1} and listening on these ports/addresses." -f $termsvc.Name, $termsvc.ProcessID
$listen
I get this on Win10 Pro.
Hello,
See if this fix helps you (works with Windows 11):
https://www.kapilarya.com/fix-rdp-port-not-listening-in-windows-10
Let us know if this helps!
Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.
Thanks you for your replies, I appreciate it!
I tried the powershell script, and below is the result:
(the print in the graphic is small...the script results are...
TermService is PID 12812 and it listening on these ports/addresses
PS C:\temp\Microsoft\RDP> $listen
PS C:\temp\Microsoft\RDP>
so it appears that it is not listening on any ports but it is running.
Next I will try the link from Kapil and report results....
The link from Kapil is very similar to https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/rdp-error-general-troubleshooting
which I have already tried, and did not solve the problem.
Note using certmgr.msc, I could not locate the Remote Desktop certificate. But even on a Windows 10 machine where remote desktop was working, I could not locate the Remote Desktop certificate. On the problem machine, the permissions of the folder C:\Program Data\Microsoft\Crypto\RSA\MachineKeys is as specified in the above article.
Use the event viewer and check the Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational log for errors.
In the Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational log there arent any errors but two informational level messages. One is...
The "Limit the size of the entire roaming user profile cache" Group Policy setting has been disabled
The other is:
RD Session Host Server role is not installed
Note the same message of "RD Session Host Server role is not installed" is also on a Windows 10 Machine log where RDP is working.
But there is no message in the log "Listener RDP-cp has started listening" on the problem machine
This Win10. Are these 4 services running?
The service "Remote Desktop Configuration" was stopped so I started it and now all four of your mentioned services are running. Still no listeners on 3389 (using netstat or qwinsta) - even tried restarting "Remote Desktop Services"
One would expect to see an error logged somewhere. I'm kinda into "educated guess" mode at the moment.
A while back I wrote a PowerShell script that reads through all event logs and puts them into a time-of-day sequence.
Maybe reboot and then run my RecentEvents.ps1 script from an admin PS prompt.
https://learn.microsoft.com/en-us/answers/questions/102481/eventlog-madness
Look for an error that occurs at about the same time that you see terminal services initializing. That's about the best that I can tell you.
It should look like this. You can use the "Filter" field to search for text.
Is Windows Update working ok? Are the quality updates getting installed successfully?
Thank you for all of your advice and help!!!
The machine was offline so I reconnected it to the internet and after a couple rounds of updates and rebooting, the machine started to listen on 3389, and RDP is back up and working!
Great.