Problems · Slowness
Why is my MacBook slow after a macOS update?
The first day after a macOS update is housekeeping: Spotlight rebuilds its index, Photos re-analyses the library, iCloud reconciles, and on a fanless Air all of that also makes heat. Plugged in and idle overnight clears most of it.
Slowness into day three has left the housekeeping story: look at login items the update re-enabled, third-party tools not yet updated for the new OS, and free disk space, which major updates consume.
First, notice when it happens
The causes, ranked
1. Indexing and media analysis, still running
most commonHow to confirm it
Activity Monitor sorted by CPU: mdworker_shared, photoanalysisd, mediaanalysisd busy. Spotlight searches returning odd results is the same story from the front.
The fix
Power connected, lid open, a quiet evening. Interrupting indexing restarts it; letting it finish ends it.
2. Free space consumed by the update
commonHow to confirm it
Major versions want tens of gigabytes through the process; a Mac that entered the update nearly full exits it slow, because macOS degrades noticeably without breathing room.
The fix
Clear back to comfortable headroom (10 to 15% free minimum). This one masquerades as an update bug and is pure arithmetic.
3. Third-party tools not yet at home on the new OS
commonHow to confirm it
Login items and background extensions written for the previous version can misbehave expensively: security tools, cleanup utilities and audio drivers lead the list. Activity Monitor names the stranger.
The fix
Update them all, and uninstall the ones you kept out of habit. After a major update is the natural amnesty for accumulated utilities.
4. The battery-health pause after big updates
occasionalHow to confirm it
Some post-update hours include battery recalibration and optimisation passes; unplugged performance judgements in that window mislead.
The fix
Judge performance plugged in, after the first quiet night.
5. The update raised the floor on an old Mac
occasionalHow to confirm it
On machines near the bottom of the supported list, each major version genuinely asks more; if everything is updated and idle is calm but it all feels heavier, the floor moved.
The fix
The honest response is measurement: a sustained run before and after tells you whether capability changed or just the feel. Sometimes the right move is staying a version behind on old hardware, deliberately.
Measure it instead of guessing
Run the test once the indexing is quiet and compare with any earlier run: if the settled level matches, the update cost you nothing real and the heavy week was housekeeping. If it dropped, you have a number to bring to the is-it-the-OS-or-the-Mac question instead of a hunch.
What software cannot tell you here
- We cannot see Spotlight's progress or which daemon is busy; Activity Monitor is the honest window.
- Whether to roll back is a data-safety decision beyond any benchmark; back up before major updates and the question loses its teeth.
Asked, in people’s own words
- How long does a Mac stay slow after an update?
- Hours of visible heaviness, up to a day or two of background settling on large photo libraries. Beyond that, stop waiting: the persistent causes (space, stale tools, login items) are checkable in minutes and fix faster than another night of hoping.
- Why is my MacBook hot after updating macOS?
- The same indexing that makes it slow makes it warm, and on fanless Airs noticeably so. It is the one time a hot idle MacBook is expected behaviour; a quiet plugged-in evening ends it.
- Should I skip macOS updates on an older Mac?
- Security updates, never. Major versions on hardware near the support floor: measuring before and after is the adult answer, and staying one major version behind (while patched) is a legitimate choice on machines the new version visibly taxes.