# How to Force Quit on Windows: Alt+F4, End Task and taskkill

To force quit on Windows, press `Ctrl + Shift + Esc` to open Task Manager, select the frozen app on the Processes tab and choose **End task**. Before that, try `Alt + F4`, which closes the active window the normal way, and give the app a moment if it was saving, exporting or syncing: a window marked "Not Responding" is often busy rather than dead.

Each step below is stronger than the one before it and gives the app less chance to save its work. Start at the top and move down only when the gentler step does nothing.

## Wait, then close it the normal way

Windows declares a window hung when it has not processed messages for 5 seconds. Microsoft's [hang documentation](https://learn.microsoft.com/en-us/previous-versions/windows/win32/win7appqual/preventing-hangs-in-windows-applications) explains that the desktop then swaps in a "ghost" copy of the window with "Not Responding" in the title bar. You can still move, minimize or close the ghost, but you cannot change anything inside the app. Five seconds is short, though. A large save, a slow network drive or a long calculation can block the window and then recover on its own; Microsoft's [Outlook troubleshooting page](https://support.microsoft.com/en-us/outlook/getstarted/outlook-for-windows-not-responding-hangs-freezes-or-stops-working) suggests waiting two or three minutes when another process is shown running in the status bar.

So before forcing anything:

1. Wait a minute if the app was in the middle of saving, exporting, copying or syncing.
2. Click another window. If the rest of Windows responds, the problem is limited to that app.
3. Switch back and press `Alt + F4`, which Microsoft's [keyboard shortcuts list](https://support.microsoft.com/en-us/accessibility/windows/keyboard-shortcuts-in-windows) describes as "Close the active window." If no window is open, the same keys bring up the shutdown prompt, so check which window is in front first.
4. If the app shows a save prompt, answer it. That is the app working again.

A normal close and a forced end are different actions, not one action at two speeds. A close request lets the app write its documents and settings in a consistent state. A forced end stops the process where it is.

## End task from the Windows 11 taskbar

Windows 11 can add **End task** to the menu you get when you right-click an app's taskbar button. It is off by default. Microsoft lists it as a Taskbar setting described as "Enable end task in taskbar by right click" on the [Advanced settings page](https://learn.microsoft.com/en-us/windows/advanced-settings/).

Where the toggle lives depends on your Windows 11 version:

- Windows 11, version 25H2 and later: **Settings › System › Advanced**, then turn on **End task** under Taskbar.
- Earlier Windows 11 versions: **Settings › System › For developers**, the same toggle. Microsoft notes that the For developers page was renamed Advanced in 25H2.

Organization-managed PCs may have this toggle disabled by policy. Once it is on, right-click the frozen app's taskbar button and choose **End task**. On Windows 10, use Task Manager instead.

## Task Manager: End task and End process tree

Press `Ctrl + Shift + Esc`, or right-click Start and choose **Task Manager**. Microsoft's [Task Manager overview](https://support.microsoft.com/en-gb/accessibility/windows/use-a-screen-reader-to-navigate-windows-support-tools) says the Processes tab groups everything into apps, background processes and Windows processes, and that End task "enables you to swiftly terminate unresponsive or resource-hogging processes." On Windows 10, choose **More details** first if Task Manager opens as a short list.

1. On the **Processes** tab, find the app under **Apps**. A hung one shows "Not responding" in its status.
2. Select it and choose **End task**.
3. Wait a few seconds. An app talking to a server can take a moment to disappear.

If the app's row is gone but something is still running, right-click the app and choose **Go to details**. The **Details** tab lists individual executables with their PID, the number Windows uses to tell processes apart. There you can end one process, or right-click it and choose **End process tree** to end it together with the processes it started.

| Where | What it ends | When to use it |
| --- | --- | --- |
| Processes › End task | The app and the processes grouped under it | First choice for a frozen app |
| Details › End task | One executable, by PID | A leftover helper after the window closed |
| Details › End process tree | That process and its child processes | A launcher or browser with helpers that keep running |

Expand an app's group on the Processes tab before ending it. A browser, for example, runs separate processes for pages and extensions, so ending one row inside the group closes a tab or extension, not the browser.

## taskkill in Command Prompt

When Task Manager itself will not draw, a command still works. First look up the image name without changing anything:

```cmd
tasklist /fi "STATUS eq NOT RESPONDING"
tasklist /fi "IMAGENAME eq notepad.exe"
```

Then end it. Microsoft's [taskkill reference](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/taskkill) defines `/im` as the image name, `/pid` as the process ID, `/f` as "processes be forcefully ended," and `/t` as ending "the specified process and any child processes started by it":

```cmd
taskkill /im notepad.exe
taskkill /f /im notepad.exe
taskkill /f /t /pid 1234
```

Run the first form before adding `/f`. `/im` matches every process with that name, so if two windows of the same app are open, both go. When only one of them is frozen, use the PID from `tasklist` instead. The [tasklist reference](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/tasklist) lists the other filters, such as `WINDOWTITLE` and `USERNAME`.

## What you lose, and what comes back

A forced end gives the app no chance to tidy up. Microsoft's [process termination documentation](https://learn.microsoft.com/en-us/windows/win32/procthread/terminating-a-process) says threads are "terminated immediately with no chance to run additional code," so anything still in memory is lost: typed text that was never saved, the last few seconds of a recording, a half-written settings file. The same page notes that ending a process does not end the child processes it created, which is why End process tree and `/t` exist.

Some apps keep their own recovery copies:

- **Microsoft Office.** AutoRecover saves recovery information on a timer set in **File › Options › Save**. Microsoft's [crash protection guide](https://support.microsoft.com/topic/551c29b1-6a4b-4415-a3ff-a80415b92f99) suggests a short interval such as 5 or 10 minutes and still recommends pressing `Ctrl + S` often, because AutoRecover only covers what it caught at its last save. When you reopen Word, Excel or PowerPoint after a crash, a Document Recovery pane may list the recovered files; save the one you want right away.
- **Microsoft Edge.** Edge restores your tabs when it reopens. If they do not come back, Microsoft's [Edge help](https://support.microsoft.com/en-us/edge/automatically-update-microsoft-edge-when-your-device-is-idle) says to right-click the title bar and choose **Restore window**, or press `Ctrl + Shift + T`. Text typed into a web form is usually not part of that.

For other apps, check the vendor's documentation for an autosave or recovery folder before you end the process, not after.

## When the whole desktop is frozen

If no window responds, not even the taskbar, the problem is no longer one app. Work through these in order:

1. Press `Ctrl + Alt + Del`. Microsoft describes it as switching to the security screen "where you can lock the desktop, switch user, sign out, change a password, or open Task Manager." If that screen appears, Windows itself is still running.
2. From there, open Task Manager and end the app, or restart Windows Explorer. Microsoft's [blank screen troubleshooting page](https://support.microsoft.com/en-us/help/14106) suggests exactly this: launch Task Manager and restart Windows Explorer.
3. If the screen is black or stuck, press `Win + Ctrl + Shift + B`. The same Microsoft page says it resets the graphics driver, and "you should hear a beep or see a screen flicker if successful."
4. If nothing helps, choose **Sign out** on the security screen. Signing out closes every app in your session, so unsaved work in all of them is at risk.
5. Holding the power button is the last step, for when even `Ctrl + Alt + Del` does nothing.

## Why an app comes back after you end it

Ending a process stops it once. It does not change what starts it. If the app reappears, one of these usually launches it again:

- **A tray icon or background mode.** Many chat, sync and launcher apps keep running after their window closes. Quit them from the tray icon's menu rather than ending them in Task Manager. Edge has its own setting for this; see [why Edge keeps running in the background](/windows/blog/edge-running-in-background).
- **A startup entry.** Apps listed in **Settings › Apps › Startup** or Task Manager's **Startup apps** tab start at every sign-in, as Microsoft's [startup apps guide](https://support.microsoft.com/en-us/windows/experience/startup-boot/configure-startup-applications-in-windows) shows. The [startup review guide](/windows/blog/manage-windows-startup) covers which ones to turn off.
- **A service or updater.** A service can restart a helper process on its own. Ending the helper repeatedly does not fix that; the app's settings, or uninstalling it, does.

If the same app freezes over and over, look at what it is doing when it hangs. [High CPU usage](/windows/blog/windows-high-cpu-usage) and [high memory usage](/windows/blog/windows-high-memory-usage) cover how to read those numbers.

## What not to end

Some processes in Task Manager are Windows itself. Microsoft's [CRITICAL_PROCESS_DIED reference](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died) names csrss.exe, wininit.exe, smss.exe, services.exe and winlogon.exe among the built-in critical system processes, and a critical process that terminates makes Windows stop with a blue screen. Leave these alone, along with **System**, **Registry** and anything grouped under Windows processes, even when the number next to them looks high.

explorer.exe is a special case. It draws the taskbar, Start and File Explorer windows, and ending it leaves you with an empty desktop until it starts again. When the taskbar or File Explorer is stuck, select **Windows Explorer** on the Processes tab and use its **Restart** action instead of End task, which closes and reopens it in one step.

## Where Mole fits

Mole for Windows has a Status tab that lists running processes grouped by the app they belong to, so a background helper shows up as part of its app instead of as an unfamiliar name. Each row's menu offers **Terminate** and **Force Quit**, and both ask for confirmation first. Terminate asks the app's windows to close, which gives the app a chance to save or show its own prompt. Force Quit ends the processes immediately and warns that unsaved data may be lost. Rows for services, programs running from the Windows folder, processes Windows will not identify, and Mole itself show "System" in place of those actions.

As the [Mole help](/windows/help) puts it, save your work before ending a process, confirm it belongs to the app you intend to close, and keep system processes and processes shared with other apps. Mole cannot help when the desktop itself is frozen; that needs the keyboard steps above.

## FAQ

### What is the fastest way to force quit on Windows?

Press `Ctrl + Shift + Esc` to open Task Manager directly, select the app and choose **End task**. `Ctrl + Alt + Del` also works, but it goes to the security screen first, where Task Manager is one of the options.

### Is End task the same as Alt+F4?

No. `Alt + F4` asks the active window to close, the same as clicking its X, so the app can save or ask you first. End task in Task Manager is meant for an app that no longer responds to that request.

### Does taskkill without /f force the app to close?

`/f` is the switch Microsoft documents for ending processes forcefully, so without it the app is not forced. Try it first; add `/f` when the process is still listed afterwards.

### Why does an app say "Not Responding" and then recover?

Windows marks a window as not responding after 5 seconds without processing messages, even if the app is busy working rather than stuck. A long save, export or network operation often finishes and the window comes back.


Canonical: https://mole.fit/windows/blog/force-quit-app-windows