Kill a windows service using its Service Name

windows service "stop pending"
taskkill service name
force stop service command line
the service is starting or stopping. please try again later
service hung on starting
wmi service stuck in stopping state
windows update service stuck stopping
unable to kill process

I am looking for a way to kill a windows services using its service name rather than the process name, or PID. The two obvious choices are pskill or taskkill, but I cannot seem to find a way of using either of these methods to kill the service by name.

Is it possible to do it by the service name? If so, is anyone able to provide a quick example?

You can use taskkill to filter by service name and kill the service you're looking for.

taskkill /F /FI "SERVICES eq yourservice"

Kill a windows service using its Service Name, How do I kill a service in Windows Server 2012? Here’s what you need to do: Step 1. Find out the Service Name. Step 2. Find out the PID of the service. Step 3. Kill the PID.

Do you actually want to KILL the process (e.g. if it is frozen) or do you want to STOP the service?

If you want to kill it stick to SomethingDark's answer (taskkill /F /FI "SERVICES eq yourservice").

If you want to stop it use SC STOP "servicename".

How to stop a hung service (Windows), To kill the service you have to know its PID or Process ID. To find this just type the following in at a command prompt: sc queryex servicename. Replace  The easiest way to stop a stuck service is to use taskkill. First of all, you need to find the PID (process identifier) of the service. As an example, let’s take Windows Update service, its system name is wuauserv (you can check the name in the service properties in the services.msc console).

In case you have multiple services with the same image name, using the SERVICES filter may not be sufficient. In this case, you need to use more filters like IMAGENAME, PID, STATUS or more.

See my related answer here

How to manually force a service to stop if not , If you have a service that is not responding or showing pending in Windows Look for the service and check the Properties and identify its service name; Once​  Sometimes when an application in Windows hangs, freezes and stops responding the only way to terminate it is to kill from the command-line. The taskkill command in Windows serves for terminating tasks by name or by process id (PID).

Manually Forcing a Service to Stop If Not Responding – GFI Support, If you have a service that is not responding or showing pending in Windows services that you are unable to stop, use the following directions to Look for the service and check the Properties and identify its service name. The Stop-Service cmdlet sends a stop message to the Windows Service Controller for each of the specified services. You can specify the services by their service names or display names, or you can use the InputObject parameter to pass a service object that represents the service that you want to stop.

Kill stuck Windows service using sc queryex and taskkill, Kill stuck Windows service using sc queryex and taskkill. Properties on the offending Windows Service in order to find the actual Service Name. up the Distributed Transaction Coordinator service, we find that it is actually named MSDTC. But it won't work for applications that have multiple top-level windows, unless they've been specifically designed to close the entire app after the closing of a single top-level window. Otherwise, you need to send WM_CLOSE to each of the top-level windows to ensure that the app gets closed.

Killing a Windows Service that Hangs on Stopping or Not , As an example, let's take Windows Update service, its system name  To kill the service you have to know its PID or Process ID. To find this just type the following in at a command prompt: sc queryex servicename . Replace 'servicename' with the services registry name. For example: Print Spooler is spooler. (See Picture)

Comments
  • Perhaps this is what you are looking for http://www.jasonn.com/enable_windows_services_command_line
  • Thank you, just what I needed
  • I wanted to kill it. I have a service that sometime cannot be stopped with NET STOP <Service> and in that instance need to kill it before restarting it.