Mac Won't Shut Down or Restart Properly
Short answer
macOS asks every app to quit and waits for each one to agree, so a single app with an unsaved document or a hung process stalls the whole shutdown. Quit apps manually first, then use Force Quit (Option-Command-Escape) on anything that will not close. As a last resort hold the power button for about ten seconds, accepting that unsaved work is lost.
On this page
Choose Shut Down, and nothing happens. The screen stays put, the cursor still moves, and ten minutes later the Mac is exactly where it was.
macOS does not force applications to close. It asks them, politely, one at a time, and waits for each one to say it is finished. Any app that does not respond holds the entire sequence open. That is the mechanism behind almost every case of this, and it tells you where to look.
Find what is blocking it
Before forcing anything, spend thirty seconds identifying the cause.
Look for a dialogue hiding behind other windows. The most common blocker by a wide margin is an app asking whether to save a document. Word, Preview, a text editor — the shutdown is waiting for an answer to a question you cannot see. Press Command-Tab through open apps and look for one with an open sheet.
Check Force Quit. Press Option-Command-Escape. Any app listed as not responding is a candidate. Select it and click Force Quit.
Check Activity Monitor. Applications → Utilities → Activity Monitor, with View set to All Processes. Processes shown in red are not responding. Anything pinned at high CPU is also worth suspicion.
| Symptom | Likely blocker |
|---|---|
| Hangs immediately, one app still visible | Unsaved-document dialogue |
| Hangs after all windows close | A background process or daemon |
| Hangs with a spinning wheel for minutes | An unmountable network volume |
| Restarts instead of shutting down | Scheduled startup, or a panic |
| Only hangs when a drive is attached | External drive failing to unmount |
The usual suspects
Unsaved documents
The fix is boring: save or discard before shutting down. If an app does this repeatedly even with nothing unsaved, it is misreporting its own state and quits cleanly if you close it manually first.
Network volumes
A mounted server share that is no longer reachable makes macOS wait for a response that will never arrive. Eject every network volume in Finder before shutting down. If one refuses to eject, disconnecting from Wi-Fi first often releases it, because macOS stops pretending the server might reply.
External drives
A drive with pending writes, or one that an app still has a file open on, blocks the unmount. Close the app using it, then eject properly. A drive that will not eject with no app obviously using it is often held by Spotlight indexing or a Time Machine backup in progress.
Login items and background agents
Menu bar utilities, VPN clients, antivirus tools and backup agents all install background components that can hang. System Settings → General → Login Items & Extensions lists both the login items and the background items apps have installed.
Turn off anything you do not recognise and restart. Disabling a background item does not uninstall the app, so this is reversible.
Forcing it off safely
When the above has not worked and you need the machine off:
- Try Control-Option-Command-Power (or Control-Option-Command-Eject on older keyboards). This asks apps to quit and shuts down, bypassing some of the polite waiting.
- Hold the power button for about ten seconds until the screen goes black.
The second option cuts power without letting apps save, so anything unsaved is gone. APFS handles the interruption well and the Mac will start up normally, but it is not something to do routinely. If you find yourself forcing shutdown every day, the background item causing it is still there and still worth finding.
On startup after a forced shutdown, let the Mac sit for a few minutes. It runs filesystem checks and may re-index, which makes the first boot slower than usual. A Mac that then runs hot for an hour is finishing that work rather than developing a new fault, as an idle Mac with loud fans explains.
Test in safe mode
If the hang keeps returning, safe mode separates macOS from everything you have installed. It loads a minimal set of extensions, runs no login items, and clears some system caches on the way in.
- Apple silicon: shut down, hold the power button until startup options appear, select your disk, then hold Shift while clicking Continue.
- Intel: hold Shift immediately after the startup chime until the login window appears.
Shut down from safe mode. If that works cleanly, the cause is something you installed, and the login items list is where to start. If it hangs in safe mode too, the problem is in macOS itself or in a failing disk, and reinstalling macOS over the top becomes a reasonable step.
What does not help
- Resetting NVRAM. It stores display, volume and startup disk settings. None of those block a shutdown.
- Resetting the SMC. Only exists on Intel Macs, and shutdown hangs are almost always a software blocker rather than a power controller fault.
- Running a cleaner app. Clearing caches does not make an app respond to a quit request.
- Disabling the shutdown confirmation dialogue. Cosmetic. The wait is happening after that point.
Realistic expectations
Most cases end with one app force-quit and never recur. A Mac that hangs on every shutdown has something persistent — usually a VPN client, a backup agent or an antivirus extension — and the login items list plus one safe mode test identifies it within an hour.
One honest limit: a failing internal disk can produce the same symptom, with shutdown hanging while macOS waits on a write that is not completing. If First Aid in Disk Utility reports errors it cannot repair, no amount of software troubleshooting is the answer, and the first priority becomes getting a backup off the machine rather than fixing shutdown.