How to Kill a Process by Name Using Command Prompt
Ending a misbehaving program by its name from the Command Prompt is quick and does not require opening Task Manager. Windows 11’s `taskkill` command stops processes by name, which is useful when an application YYGACOR has frozen or you want to close it from a script.
The Command
taskkill /IM notepad.exe /FWhat It Does
`taskkill` ends processes, `/IM` specifies the image name (the executable’s name), and `/F` forces the process to close. So this example forcibly ends all running instances of Notepad. The `/F` flag ensures the process closes even if it is not responding, which is often the reason you are ending it in the first place.
When You’d Use This
Reach for this when a program has frozen and will not close normally, or when you want to close all instances of an application from the terminal or a script. It is quicker than opening Task Manager to end a task, and targeting by name closes every instance at once, which is useful for programs that spawn multiple processes.
Useful Variations
To end a process more gently without forcing, leave off `/F`, which asks the program to close and allows it to save. To target a single instance by its ID instead of name, use `/PID` followed by the number. To end a process and any child processes it started, add `/T` to the command.
If It Doesn’t Work
If the process will not close, ensure you included `/F` to force it, and run the terminal as administrator for processes owned by the system or another user. If it reports the process is not found, check the exact image name, including the .exe. Be careful with system process names, since forcing essential Windows processes to close can destabilize the system until you restart.
Good to Know
Forcing a process to close with `/F` means any unsaved work in that program is lost, so use it mainly for frozen or unresponsive applications. Be careful with system process names, since forcibly ending essential Windows processes can cause instability or require a restart.
Putting It Together
Once you have run it once or twice, this becomes second nature. As part of understanding and controlling what runs on your PC, this command is one you will return to whenever the system feels slow or a program misbehaves. Paired with the related process commands, it gives you a full command-line alternative to Task Manager for diagnosing and managing what is running. Like anything in the terminal, the real value comes from trying it on your own system and adapting the variations above to what you actually need, so it is worth experimenting with in a safe, low-stakes situation before relying on it in a script or during troubleshooting. Keeping a note of the commands you find most useful, along with the variations that fit your workflow, turns scattered one-off tricks into a personal reference you can draw on whenever a similar task comes up again.