1 Reply
· · ·
Thai Pepper
OP
Best Answer
Jan 26, 2015 at 23:39 UTC
I figured out how to do it...
Use tasklist:
Text
tasklist /s servername /svcLook at all the svchost.exe processes listed and then look at the services associated with them. You can check the service names by looking at the services msc for a particular service or just google the service listed.
In my case the service was UmRdpService and shared a process with Netman [Network Connections], UxSms [Desktop Window Manager Session Manager] and wudfsvc [Windows Driver Foundation].
Once I found the process ID, I used taskkill:
Text
taskkill /s servername /pid 1204 /fThis didn't allow me access to my server yet but it did force the stoppage of the "Remote Desktop Services UserMode Port Redirector" service.
2
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Archived Forums
>Remote Desktop Services [Terminal Services]
Question
-
0
Sign in to vote
Hello Everybody!
I tried to restart Remote Desktop service on my Windows 10, and strange error occurs:
"Event 20501: Remote Desktop Services failed to shutdown within the time allocated"
Remote Desktop service still stay in state = stopping, and TaskManager shows PID=340 for TermService.
How to restart RDS without restart a PC ?
Friday, June 3, 2016 12:14 PM
General Remote Desktop connection troubleshooting
- Article
- 12/23/2021
- 8 minutes to read
- 8 contributors
Is this page helpful?
Yes No
Any additional feedback?
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Submit
Thank you.
In this article
Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.
How to restart RDP without rebootingwindows
May 16, 2013 10 Comments
WARNING: Test this process before you try it on an production system, to make sure you like the results and have the process down.
Problem:
RDP has stopped working but your server still work just users can’t connect to modify applications
The most common fix is to reboot windows, because “Remote Desktop Services” aka TermService can’t be restarted at least thats the case on 2003 as the option is grayed out. This will also create an outage just for a remote control issue and thats not always desirable.
The fix: [remotely]
from command line
- tasklist /s \\servername /svc /fi “imagename eq svchost.exe” [locate PID for TermService]
- taskkill /s \\servername /pid xxxx [may need /f to force, UAC might give problems as well]
- sc \\servername start TermService
The Fix: [local, using remote admin card/other remote control software/other remote command line]
From command line
- tasklist /svc /fi “imagename eq svchost.exe” [locate PID for TermService]
- taskkill /pid xxxx [may need /f to force, UAC might give problems as well]
- sc \\servername start TermService
more helpful RDP troubleshooting
//support.microsoft.com/kb/2477176
Rate this:
Share this:
- Click to email this to a friend [Opens in new window]
- Click to print [Opens in new window]
- Click to share on LinkedIn [Opens in new window]
- Click to share on Facebook [Opens in new window]
- Click to share on Twitter [Opens in new window]
Like this:
Like Loading...
Filed under 2000, 2003, 2008, Microsoft, Windows Tagged with 2000, 2003, 2008, Microsoft, Windows