Home / Guides / Command Prompt Fixes

Using tasklist and taskkill to Find and Close Frozen Programs

Intermediate Command Prompt Fixes Applies to: Windows 7, Windows 10, Windows 11

A faster, more precise alternative to Task Manager when a program won't close normally.

Before you start: save any open work and note down what you were doing when the problem started — that context helps if you need to search further or ask for help.
  1. Type tasklist to see every running process with its exact name and Process ID (PID) — useful for identifying exactly what you're dealing with before closing anything.
  2. Narrow the list with tasklist /fi "imagename eq chrome.exe" (swap in the process name you're looking for) if the full list is too long to scan through.
  3. Close a specific program with taskkill /im programname.exe (using the exact name from tasklist) — this works even when a program is too frozen to close normally.
  4. For a program that resists a normal close, add /f to force it: taskkill /f /im programname.exe.
  5. If you know the specific Process ID rather than the name, taskkill /f /pid 1234 targets exactly that one process, which is safer than closing by name if multiple processes share it.
Still not fixed? Send us the details and we'll help you dig further, or browse related guides in Command Prompt Fixes.

Frequently Asked Questions

Is taskkill safer than using Task Manager to end a process?
They accomplish the same thing — taskkill is just the command-line equivalent, useful when Task Manager itself won't open or when you want to end a process by script rather than manually.
Can I accidentally close something important with taskkill?
Yes, if you force-close a critical system process, it can cause instability or a crash — using tasklist first to confirm exactly what you're targeting before running taskkill is worth the extra step.

Related guides

Command Prompt Won't Open

Typing "cmd" into the Start menu does nothing, or Command Prompt flashes open and immediately closes.

Beginner

How to Run Command Prompt as Administrator (and Why It Matters)

Many repair commands fail silently or refuse to run unless Command Prompt has administrator privileges.

Beginner

sfc /scannow Explained: What It Does and How to Read the Results

The most common Windows repair command — here's what it actually checks and what its output means.

Beginner