8

Steps like

  1. Copy service name from service properties
  2. In administrator's command line run: sc queryex {here paste service name}, mark PID
  3. Run taskkill /f /pid {here paste PID}

do not work, because process is not started yet (stuck at starting), so has no PID.

Any solution except server restart?

avj
  • 183
  • 1
  • 1
  • 4
  • To prevent misunderstandings: I'm not concerned with getting an accepted answer. I give only an explanation how Serverfault works. Serverfault is a Q & A platform and the accepted answer should fit the question. This ensures that someone with a similar problem receives a correct answer. Your accepted answer fits your problem but not the question you asked. – marsh-wiggle Nov 02 '18 at 13:54

2 Answers2

7
  • Retrieve the command line of your service from the service properties (services.msc)
  • Start Process Explorer
  • In Process Explorer make the command line visible (View / Select Columns / Command line)
  • locate the process and kill it (Del)

Example command line: C:\Windows\system32\svchost.exe -k netsvcs

marsh-wiggle
  • 2,145
  • 5
  • 29
  • 45
  • Thank you for sharing this tool and info on how to use it! For my particular case, unforunately, service kept coming back again and again – avj Nov 02 '18 at 12:43
  • @avj In that case, try rebooting your box and then kill the exe. – RBT Feb 05 '20 at 09:55
-2

Change the startup type of that service to Manual - that can resolve your issue

RBT
  • 251
  • 1
  • 3
  • 12
Ario
  • 32
  • 1
    Although, this particular thing did not help, it gave me a clue on changing startup type, and setting it to Disabled helped. – avj Nov 02 '18 at 12:43
  • In my scenario, the service was stuck in starting because it was configured in the recovery tab to restart indefinitely. I typed in the wrong password, and that locked the account in AD. Switching startup type to manual stopped the indefinite restart loop allowed me to unlock the account in AD and correct the credentials. – Mark Iannucci May 06 '20 at 17:18