Windows could not start the Remote Desktop Services service on Local computer

RDP service will not start Server 2008 R2. Windows could not start the Remote Desktop Services Service on Local Computer. Error 2: The system cannot find the file specified.

Archived Forums

>

Remote Desktop Services (Terminal Services)

• Question

• 0

  Sign in to vote

  Hey All
  
  I really need some help here, I am officially stumped.
  
  
  
  I have a Windows Server 2008 R2. Very basic setup with 1-2 people using RDP. It has been a solid stable machine, until a few nights ago. I applied updates through Windows update. When the computer came back, the RDP Service would not start. It says 'Windows could not start the remote Desktop Services Service on Local Computer. Error 2: The system cannot find the file specified'. Ive tried reinstalling RDP.
  
  
  
  Any help is highly appreciated.

  
  

  
  
  • Edited by Partsdude Saturday, August 23, 2014 2:05 AM

  Saturday, August 23, 2014 2:04 AM

Answers

• 0

  Sign in to vote

  Hi Partsdude,

  I have a few suggestions to try.

  
  

  1. Run Regedit and Navigate toHKLM\System\CurrentControlSet\Services\TermService\Parameters

  Check the serviceDLL key, for example the value I see is%SystemRoot%\System32\termsrv.dll. Makes sure the entry is valid and that the file exists. See if its the same version and size as one from a known working server with the same patch level.

  2. Do a system file check to see if finds and files damaged or missing. From an Administrative command prompt (Click Start, type cmd, right click and select “Run as Administrator”, click Yes on the UAC prompt)

  Enter this -> SFC /scannow

  3. Try starting the service from an administrative command line.

  C:\windows\System32\svchost.exe -k termsvcs

  4. Check the dependencies in Services Administrative tool for the Remote Desktop Service and make sure they are started.

  • Marked as answer by Partsdude Sunday, August 24, 2014 3:32 PM

  Saturday, August 23, 2014 6:59 PM

All replies

• 0

  Sign in to vote

  Hi Partsdude,

  I have a few suggestions to try.

  
  

  1. Run Regedit and Navigate toHKLM\System\CurrentControlSet\Services\TermService\Parameters

  Check the serviceDLL key, for example the value I see is%SystemRoot%\System32\termsrv.dll. Makes sure the entry is valid and that the file exists. See if its the same version and size as one from a known working server with the same patch level.

  2. Do a system file check to see if finds and files damaged or missing. From an Administrative command prompt (Click Start, type cmd, right click and select “Run as Administrator”, click Yes on the UAC prompt)

  Enter this -> SFC /scannow

  3. Try starting the service from an administrative command line.

  C:\windows\System32\svchost.exe -k termsvcs

  4. Check the dependencies in Services Administrative tool for the Remote Desktop Service and make sure they are started.

  • Marked as answer by Partsdude Sunday, August 24, 2014 3:32 PM

  Saturday, August 23, 2014 6:59 PM

• 0

  Sign in to vote

  Hey Jeremy

  Thank you for the suggestions. MyHKLM\System\CurrentControlSet\Services\TermService\Parameters wascompletelyempty. I added theentriesfrom a working server and now everything is ok!

  I really appreciate your help. Thank you.

  • Proposed as answer by Vitali_ST Thursday, January 16, 2020 3:31 PM

  Sunday, August 24, 2014 3:32 PM

• 0

  Sign in to vote

  The serviceDLL key was entirely absent on the computer I was working on....

  Very helpful. Thank you!

  Tuesday, January 23, 2018 7:51 PM

• 0

  Sign in to vote

  Thanks for your answer! It hepled me.

  1. I deleted the entire registry branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\TermService\ from problem server.

  2. I exportedthe entire registry branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\TermService\ from normal server.

  3. I imported thisregistry branch inproblem server fromnormal server.

  4. Remote desktop service (RDS) started good.

  Thanks!

  • Proposed as answer by Vitali_ST Thursday, January 16, 2020 3:35 PM

  Thursday, January 16, 2020 3:35 PM

5 Replies

· · ·

Mace

OP

JitenSh

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 18, 2020 at 14:45 UTC

set blank password and restart services

Click the Start button on the Taskbar and type in the search box regedit.Click Regedit listed at the top under Programs.The Registry Editor opens. Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ remote desktop management service name .Verify the Eventlog folder is highlighted. On the right side pane, double-click ObjectName.Under Value data, type the following: NT AUTHORITY\LocalService and click ok.Close the Registry Editor and restart the system.

0

· · ·

Thai Pepper

OP

kindofageek

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 18, 2020 at 14:58 UTC

JitenSh wrote:

set blank password and restart services

Click the Start button on the Taskbar and type in the search box regedit.Click Regedit listed at the top under Programs.The Registry Editor opens. Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ remote desktop management service name .Verify the Eventlog folder is highlighted. On the right side pane, double-click ObjectName.Under Value data, type the following: NT AUTHORITY\LocalService and click ok.Close the Registry Editor and restart the system.

I'll give this a try. It'll be tonight before I can reboot.

0

· · ·

Sonora

OP

jakebreakwell

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Dec 18, 2020 at 16:35 UTC

Hi

Any luck on this? I have just encountered this issue after our whole infrastructure including the RDS farm was moved to a new IAAS.

0

· · ·

Thai Pepper

OP

kindofageek

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Dec 18, 2020 at 17:12 UTC

jakebreakwell wrote:

Hi

Any luck on this? I have just encountered this issue after our whole infrastructure including the RDS farm was moved to a new IAAS.

We ended up moving the RDS Gateway role to a dedicated server.

1

· · ·

Sonora

OP

jakebreakwell

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

Dec 21, 2020 at 15:25 UTC

Sounds like a good idea!

0

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Windows 10: Remote Desktop Service is not working - Error 126

Discus and support Remote Desktop Service is not working - Error 126 in Windows 10 BSOD Crashes and Debugging to solve the problem; Good afternoon, Remote Desktop on Windows 10 Pro it's not working anymore. After reviewing the problem I have detected that the "Remote Desktop... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Aitor Morales Hernández, Jul 30, 2020.

How to resolve common problems with Windows Remote Desktop

Janne Ruostemaa

staff

Troubleshooting Updated on 2021-03-30 72

If you have problems using Remote Desktop (RDP) with your Windows server, there are a couple of things you can fix. This troubleshooting guide aims to help rule out some of the most common causes for poor functionality.

Try UpCloud for free! Deploy a server in just 45 seconds