Mac slow after a macOS update? Why it happens (and what helps)
Mac slow after a macOS update? It's usually temporary background work (Spotlight reindexing, Photos re-analyzing, iCloud re-syncing), not a broken Mac.
Your Mac just finished a macOS update, and now it feels slower than before: laggy, warm, fans up, everything a beat behind. Here's the reassuring part: a Mac that's slow after an update is usually not a Mac the update broke. It's a Mac that's still finishing the update. For a few hours after a big upgrade, sometimes the better part of a day, macOS runs a pile of catch-up work in the background, and until that settles, everything on top of it feels sluggish.
Why your Mac is slow after a macOS update
An update doesn't end when the progress bar does. Once you're back at the desktop, macOS quietly kicks off a batch of one-time housekeeping that it front-loads to get out of the way. It's CPU- and disk-heavy while it runs, which is exactly why the machine feels slow: the work is real, it's just temporary. The usual jobs:
- Spotlight reindexing. After an upgrade, macOS often rebuilds or revalidates its search index, so
mds,mds_stores, andmdworkerchurn through your files. This is the single most common cause of post-update sluggishness. Here's why mds_stores pegs the CPU after an update and how to tell it's progressing. - Photos re-analyzing your library.
photoanalysisdandphotolibrarydre-scan your photos for faces, scenes, and search, and a big library after an update can keep them (and the fans) busy for hours. - iCloud re-syncing.
birdandclouddreconcile your iCloud content after the update, pulling and checking files in the background. - System housekeeping. macOS recompiles caches, and the App Store may pull updated versions of your apps in the background so they're rebuilt for the new OS.
The single best thing you can do is nothing. Plug into power, leave the Mac awake and idle for a few hours (overnight is even better) and let these finish. They're doing finite work, and they wind down on their own once caught up. Fighting it by force-quitting these processes just makes them start over.
How long it should take
Usually a few hours. A large Photos library, a lot of iCloud content, or a slower or nearly-full disk can stretch it toward a day. The way to tell it's actually finishing rather than stuck: open Activity Monitor, and if the busy processes are high but drifting down over time, that's a backlog clearing; leave it alone. If your fans are roaring through all this, that's the cooling system responding to the extra work, not a fault; here's what to check when the fans are loud.
When it's not just temporary
Most of the time, patience is the fix. But a few things can make a Mac slow after an update and stay that way. If it hasn't settled after a day or two of light use, check these:
- Incompatible login items or old extensions. Something that loaded fine on the old macOS (a menu-bar helper, a VPN or antivirus agent, an old third-party kernel extension or driver) may not be compatible with the new version and can drag the whole system down or hang at login. If your Mac is also slow to start up, that's a strong tell; see how login items slow down startup and how to prune them.
- A nearly-full disk. Updates need real headroom to unpack and install, and macOS needs free space afterward to breathe. Guidance varies, but installers commonly want on the order of 20 GB or more of temporary space, and keeping roughly 10–15% of the disk free is a sensible rule of thumb. A disk that's almost full both slows the update's cleanup and leaves macOS thrashing. Free up some space and give it another few hours.
- A genuine bug. Occasionally a specific macOS version ships a regression that hits some Macs: a runaway process, a sync loop, or a broken index. These are real, but they're the exception, not the default explanation. A pending point release (for example x.x.1) often fixes them.
What to actually check, in order:
- Activity Monitor (Applications → Utilities → CPU tab, sorted by % CPU). Is one process stuck high for a long time while you're doing nothing? A recognizable catch-up process trending down is fine. An unfamiliar name pinned at the top for hours is worth chasing.
- Free disk space (Apple menu → System Settings → General → Storage). If you're near full, that alone can explain the drag.
- A safe-mode test. Restart into safe mode, which loads a minimal macOS and skips third-party login items and some extensions. If your Mac is smooth in safe mode but slow when you boot normally, something you installed, not the update itself, is the culprit.
Normal vs. worth checking
| Looks like | Usually |
|---|---|
| Slow, warm, fans up for a few hours after updating | Normal: background catch-up work finishing |
| Still settling overnight with a big Photos or iCloud library | Normal: larger backlog, give it a day |
| One unfamiliar process pinned high for a day-plus at idle | Worth checking: stuck process or bad login item |
| Slow and nearly-full disk | Free up space first, then re-check |
| Slow from the moment it starts, especially at login | Check login items / old extensions in safe mode |
The frustrating part of a post-update slowdown is that you can't easily tell which story you're in. Is macOS quietly finishing its work, or is something actually stuck? By the time you open Activity Monitor, a spike has often already passed. Plumby keeps a live readout of CPU, memory, and temperature in your menu bar and holds that history across reboots, so you can see whether the post-update processes are trending down and finishing or stuck, and which one is actually driving the heat. It measures and reports; it never deletes your files or force-quits your work to "speed things up," so you know whether to simply wait or actually act.
