How to kill a frozen process

Find and stop an unresponsive process safely: identify the PID, send a graceful signal first, and force-kill only when necessary.

Beginner · about 4 min · Linux, Windows, macOS

A hung application still holds memory, files and ports. Stopping it correctly means asking it to exit first so it can flush data, and reserving the force option for when it refuses.

What this guide covers

• Find the process
• See what it is consuming
• Ask it to stop
• Force only if it ignores you
• Windows: find and stop by name or PID
• PowerShell equivalent

Common pitfalls covered

• kill -9 on a database or file-sync process risks corruption — always try a graceful stop first.
• A process in state D (uninterruptible sleep) ignores even KILL; the underlying disk or network mount is the real problem.
• For services, use … rather than killing the PID, or the supervisor will restart it immediately.

Questions answered

• What is the difference between kill and kill -9?
• How do I kill a process by name?
• The process comes back after I kill it — why?

This is a limited preview. The full walkthrough, command syntax and copy-ready examples are available to signed-in users.

Sign in to read the full page