Mac slow after a macOS update — quick fixes

You installed the latest macOS update last night and the Mac has been sluggish ever since — fans up, apps slow to launch, battery worse than yesterday. This is almost always temporary, but knowing why helps you decide whether to wait it out or actively fix something.

What’s actually happening

After a macOS update, the system rebuilds a lot of caches and re-indexes a lot of data. Specifically:

• Spotlight reindexes the entire drive (mds, mds_stores)
• iCloud Drive re-validates synced files (bird, cloudd)
• Photos re-analyses the library (photoanalysisd)
• The dynamic linker rebuilds its shared cache
• Time Machine often does a fresh comparison snapshot

All of these run with low priority, but together they can keep CPU at 50%+ for hours, especially on the first day after a major version upgrade. On the second day it’s usually gone.

Check whether that’s what you’re seeing

1. Open Activity Monitor, CPU tab. Sort by %CPU.
2. Look for the usual post-update processes: mds_stores, mdworker, photoanalysisd, bird, cloudd, backupd.
3. If any of them are sustained at high CPU, the slowdown is post-update indexing. Plug in to power and leave the Mac open overnight. Photos analysis and most indexers pause on battery and resume on power.
4. If none of those are the culprit, look for third-party processes. Sometimes an app's helper or kernel extension is incompatible with the new OS and pegs CPU.

If it doesn’t settle

After 24-48 hours of being plugged in, indexing should be done. If the Mac is still slow:

• Check Activity Monitor again — what’s running now?
• Restart. Some caches don’t fully take effect until reboot.
• Check for app updates. Some apps need updates after a macOS release.
• Run sudo periodic daily weekly monthly in Terminal to force the usual cleanup scripts.
• For graphics-related slowness, reset NVRAM (Intel Macs only — Apple Silicon doesn’t have user-resettable NVRAM in the same way).

The kernel extension trap

If you have any old kernel extensions or system extensions (some VPNs, old backup tools, old audio drivers), they sometimes block boot or cause severe slowdowns after major updates. Check System Settings - General - Login Items & Extensions to see what’s loaded.

Watching it recover

Indexing finishes in stages — Spotlight first, then photos, then sync agents. A menubar monitor lets you see CPU drop process by process so you know when you’re past the worst of it. Beacon shows CPU load and the top processes in the menubar — $14.99 lifetime. Download Beacon if you’d like the trend visible.

When to be concerned

If a fresh boot, plugged in, with nothing running shows CPU above 30% from system processes alone after 48 hours, something is stuck. Look in ~/Library/Logs/DiagnosticReports/ for crash logs from the same daemon repeatedly — that’s usually a smoking gun. A clean reinstall is the nuclear option and rarely needed.