Force Stop Windows Service via Command Prompt

This guide shows you how to force stop a Windows service using Command Prompt. This is useful when a service is stuck, unresponsive, or won’t stop through the Services console. You’ll need to run Command Prompt as an administrator, and know the exact service name (not the display name) of the service you want to stop.

What You’ll Need

A Windows PC (Windows 10, 11, or Server versions).
Administrator access to the computer.
The exact service name (e.g., “Spooler” for the Print Spooler). You can find it in the Services console (services.msc) under the “Service name” column, or by running sc query in Command Prompt.

Step-by-Step

Open Command Prompt as Administrator. Press Windows + R, type cmd, then press Ctrl + Shift + Enter. Click “Yes” on the User Account Control prompt. Alternatively, search for “Command Prompt” in the Start menu, right-click it, and select “Run as administrator.”
Identify the exact service name. In the Command Prompt, type sc query and press Enter. This lists all running services with their service names. Find the one you want to stop. If you already know the service name (e.g., “wuauserv” for Windows Update), skip this step.
Try a normal stop first. Type net stop <service name> and press Enter. For example: net stop wuauserv. This sends a stop request to the service. If it stops, you’re done. If you get an error like “The service is not responding to the control function,” proceed to the next step.
Force stop the service. If the normal stop fails, use the sc command with the stop option and the force flag: sc stop <service name> force. For example: sc stop wuauserv force. This sends a more forceful stop request that often works when the service is hung.
If the service still doesn’t stop, kill the process. Some services run as a separate process. Use tasklist | findstr <service name> to see if a process with that name is running. If you find the process ID (PID), use taskkill /F /PID <PID> to force kill it. For example: taskkill /F /PID 1234. Be careful: only kill the process if you’re sure it’s the service you want to stop.
Verify the service is stopped. Run sc query <service name> and check the “STATE” field. It should say “STOPPED”. If it still shows “RUNNING” or “STOP_PENDING,” wait a few seconds and try again, or consider restarting the computer.

Common Mistakes

Using the display name instead of the service name. The display name (e.g., “Windows Update”) is what you see in the Services console, but the command line requires the short service name (e.g., “wuauserv”).
Not running as administrator. If you get “Access denied” or “System error 5,” you’re not elevated. Close the Command Prompt and reopen it as administrator.
Typing the service name with spaces or quotes. Service names never contain spaces. If you copy a name with spaces, remove them. Do not include quotes unless the name is part of a path (which is rare).
Killing the wrong process. The process name may not match the service name. Always verify the PID before using taskkill.

Tips

Use sc query to list services. This shows the service name, display name, and state. It’s a quick way to find the exact name.
Combine sc stop with force only when needed. The force flag can cause data loss if the service is writing files. Use it only when a normal stop fails.
Consider restarting the service after stopping it. If you stopped a service to fix a problem, you’ll likely want to start it again with net start <service name>.
Write down the service name. If you frequently need to stop a particular service, note the name in a text file for quick reference.

Troubleshooting

“The specified service does not exist as an installed service.” This means the service name is wrong. Double-check the spelling and case. Use sc query to see the exact names.
“System error 5 has occurred. Access is denied.” You’re not running as administrator. Right-click Command Prompt and select “Run as administrator.”
“The service is not responding to the control function.” This happens when the service is hung. Try the sc stop <name> force command. If that fails, you may need to kill the process as described in step 5.
“The service cannot be stopped because it is dependent on other services.” Other services are using this service. You may need to stop those dependent services first, or stop them all together. Use sc queryex <service name> to see dependencies.
Service stops but then restarts immediately. Some services have recovery options set to restart automatically. You can disable this in the Services console (right-click the service, Properties, Recovery tab) or use sc failure <service name> reset= 0 actions= restart/0/restart/0/restart/0 to change the recovery settings (but this is advanced and not recommended unless you know what you’re doing).

Frequently Asked Questions

What’s the difference between `net stop` and `sc stop`?

net stop is a simpler, older command that sends a stop request. sc stop offers more options, including the force flag, and gives more detailed output. For most cases, net stop is enough; if it fails, use sc stop ... force.

How do I find the service name if I only know the display name?

Open the Services console (services.msc), find the service in the list, and look at the “Service name” column. Alternatively, run sc query and look for the display name in the output—the service name is listed just above it.

Can I force stop a service without admin rights?

No. Stopping a service requires administrative privileges. You must run Command Prompt as administrator, or you’ll get an access denied error.

What happens if I force stop a critical system service?

It can cause system instability, data loss, or a crash. Only force stop services you know are safe to stop. If you’re unsure, research the service first or contact your IT department.

Will the service restart automatically after I force stop it?

It depends on the service’s recovery settings. Some services are set to restart automatically. If you want to prevent that, you can change the recovery options in the Services console or use sc failure command, but do so carefully.

Is there a way to force stop multiple services at once?

You can write a batch script that loops through service names and runs sc stop for each. For example: for %s in (Service1 Service2 Service3) do sc stop %s force. But be cautious—stopping multiple services can have cascading effects.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →