End Task on a Mac: how it works compared to Windows

On a Mac, End Task is a two-step idea: ask the app to quit, and force it only if it will not. macOS has no End Task button of its own, but Quit (Command-Q) is the polite first step and Force Quit (Option-Command-Escape) is the forced second one. On Windows, End Task is the one button, and for a stuck program it ends it. On a Mac the first step gives the app a chance to ask whether you want to save, which is why it is worth doing in that order.

Here is how each step works, what “Not responding” means, and how Foreman puts both steps behind one End Task button.

Quit first: what Command-Q really does

When you press Command-Q, you do not kill the app. You send it a request to quit. The app receives the request and runs its own shutdown. That is when it checks for unsaved work and shows “Do you want to save the changes?”, closes its files in order and then exits.

That is the point of quitting first: the app has a say, so nothing is lost if you wait for it. The cost is that an app that is stuck cannot answer, and so the request sits there.

Force Quit: when the app does not answer

Force Quit does not ask the app. It tells macOS to end the app’s process, and the app gets no chance to save or tidy up. Anything you had not saved is gone. Apps that save automatically, such as many macOS apps, may bring your work back when you open them again, but you cannot count on it.

You reach it in a few ways. Option-Command-Escape opens the Force Quit window, where you pick the app and click Force Quit. You can also choose Force Quit from the Apple menu, which opens the same window, or hold Option while you right-click an app’s Dock icon, and Quit turns into Force Quit. Quit vs Force Quit on a Mac: what you lose with each is the one to read before you force quit something with unsaved work.

What “Not responding” means

In the Force Quit window, macOS writes “(not responding)” beside an app it has found to be hung. That means the app has stopped handling its own events for a while: it is not reading clicks or redrawing its windows. You usually see the spinning beach ball first.

The label does not always mean the app is dead. An app that is busy with a long task, such as exporting a video or opening a huge file, can look hung and then recover. What “Not responding” means on a Mac, and how long to wait covers how long to give it. A good rule is to wait a minute or two first if the Mac is working hard, and force quit if nothing changes.

How Foreman’s End Task works

Foreman is a Task Manager for macOS, and its End Task button follows the two-step idea. It is on the Processes page toolbar, in the right-click menu and in the Process menu, where it is Quit (Command-Delete) and Force Quit (Option-Command-Delete).

  • End Task asks the app to quit the normal way, as Command-Q does, so it can offer to save your work.
  • Press End Task again, within a minute, and Foreman force quits the app.
  • If macOS has marked the app “Not responding”, End Task force quits it at once, because the app cannot answer a polite request anyway.
  • If the app is still open after a moment, Foreman brings it forward, in case it is asking about unsaved changes, and offers Force Quit.

Force Quit on an app with windows asks first: “You’ll lose any unsaved changes”. You confirm, and then it goes. While an app shuts down, its row on the Processes page reads “Quitting…”.

So on a busy Mac, you press End Task and wait. If the app saves and goes, you are done. If it does not, a second press finishes the job. You get the Windows result when you need it, with the Mac’s polite step first.

Things Mac and Windows treat differently

A few more differences are useful to know.

Apps are groups of processes. On a Mac one app can have many processes, such as a browser with a helper for each tab. When the app quits, its helpers normally go with it, and Force Quit ends the app and its helpers. Foreman groups them under the app, so you act on the row, not on each helper.

Parts of macOS are protected. Foreman never offers to end kernel_task or launchd, because they are the core of macOS. Before it ends something like WindowServer or loginwindow, it warns you what will happen: you are logged out. Processes that belong to macOS or to other users need an administrator password, and Foreman asks for it first.

A suspended app wakes first. If you have frozen an app with Suspend, End Task wakes it before it asks it to quit, so it can act on the request.

Some apps come back. After you end an app, something may start it again. A login item or a background helper can do this, and macOS restarts many of its own processes by itself. Why an app keeps reopening after you quit it on a Mac explains the cause.

Restart is its own action. Foreman’s Restart quits an app and opens it again, behind Foreman, so you stay where you were. It is useful for an app that has gone slow but is not stuck.

What not to end

On Windows and on a Mac alike, a process you do not recognise is not a process to end. Look up the name first. The processes macOS needs are the ones that make the Mac work: if you end one, the Mac may log you out, or macOS may simply start it again. Many of them show a plain-English name in Foreman, which makes it easier to tell what you are about to end.

If an app is simply slow, you do not have to end it at all. Foreman’s Efficiency Mode runs an app you are not using at background priority until you switch back to it, and How to pause an app on a Mac instead of quitting it shows the other way to take the pressure off.

Foreman opens from any app with Control-Shift-Escape. It needs macOS 14 Sonoma or later and is free for 24 hours, then $12 once for up to 3 Macs.