How to Force Quit an App on Windows

There is a proper escalation order here and it is worth following rather than leaping straight to the end. Each step is more forceful than the last, and each one costs you a bit more. Starting at the top occasionally saves the document you had open, which is not nothing.

First, check whether it is actually frozen

Windows slaps "Not responding" on a window when it has not collected messages from its queue for a few seconds. That is not at all the same thing as crashed, and the distinction matters. A spreadsheet recalculating, a photo editor grinding through a filter on a huge image, or a program waiting on a slow network share will all earn the label while working away perfectly happily. Give it a minute before you kill it.

Give it thirty seconds. If the disk light is active, or Task Manager shows the process using CPU, it is doing something. Killing it at that point discards the work it was in the middle of, and in the case of a save operation can leave a half-written file.

Alt + F4, the polite request

Click the window to focus it, then press Alt + F4. This sends a polite close message. A program that is merely busy rather than broken will act on it the moment it catches up, and usually offer to save your work first, which is exactly the outcome you want.

Task Manager: End task

taskkill, when Task Manager is not enough

Occasionally End task just fails silently: you click it, nothing happens, the process is still sitting there. The usual explanation is permissions. The process is running at a higher integrity level than your Task Manager, so your request is quietly denied rather than refused out loud. Running the kill from an elevated command line clears most of these, and the guide on opening a terminal in Windows covers getting one.

PowerShell has an equivalent: Stop-Process -Name notepad -Force, or Stop-Process -Id 4812 -Force. Either is fine. PowerShell's version gives more usable errors, which matters when something is not working.

When a process will not die at all

Sometimes taskkill /F cheerfully reports success and the process is still right there in the list. This is not a bug in taskkill. The termination has genuinely been requested and accepted, but the process cannot finish exiting because one of its threads is stuck inside a kernel-mode call, usually a driver waiting on hardware that has stopped answering. At that point nothing in user space can help you.

• A failing or disconnected drive. A program that opened a file on a network share or a dying disk will sit in an uninterruptible wait until the I/O times out, which can take minutes.
• A USB device that has stopped responding. Unplugging it often releases the process immediately.
• Antivirus or backup software holding a file handle open. Real-time scanners are a frequent cause.
• A buggy driver. Nothing in user space can help here. A restart is the only route.

If it is the taskbar or desktop that has frozen

A frozen taskbar, a missing Start menu or a dead desktop is a completely different problem, and reaching for End task on the wrong thing will not help. Those three are not an application at all: they are explorer.exe, which is both the file manager and the Windows shell. Restarting it fixes all three in about two seconds, and it is one of the most useful things to know about Windows.

Why one process does all three jobs is covered in the guide on what Windows Explorer actually is. It is the single most useful piece of background knowledge for diagnosing a Windows machine that has gone strange.

If the same program freezes repeatedly

Force-quitting is a workaround, not a fix, and if you are doing it to the same program every day something else is wrong. A few things are worth checking before you accept it as just how that application behaves.

1. Look at Event Viewer. Press Win + R, run eventvwr, and check Windows Logs → Application around the time of the hang. Application Error and Application Hang entries name the faulting module, which is often a specific DLL or a graphics driver.
2. Update or roll back the graphics driver. A large share of application hangs come from the GPU driver, particularly in browsers and anything that renders with hardware acceleration.
3. Turn off hardware acceleration in that program as a test. If the hangs stop, you have confirmed the cause.
4. Check the disk. Run chkdsk C: /scan from an elevated prompt. A drive with pending sector reallocations produces exactly this symptom.
5. Check available memory. A machine paging heavily looks frozen at the application level. Task Manager's Performance tab shows whether memory is the constraint.