Mac Care

Mac Slow After an Update? A Step-by-Step Troubleshooting Guide

Most post-update slowness is background catch-up. Use Activity Monitor, Safe Mode, and install history to tell it from a real fault, and know when to reinstall.

By Editorial team

Published 14 min read

Ask this guide

Answers come straight from this guide’s text. Nothing is generated, and nothing you type leaves your browser.

0 of 4 doneSaved on this device only.

Your Mac updated, and now it stutters. Typing lags, the fans spin while you do nothing, and Activity Monitor lists processes you have never heard of. macOS 27 (Golden Gate) shipped on 14 September 2026 and 27.0.1 followed on 28 September, so many Macs have just been through a major update.

Usually the cause is dull: the system is doing deferred work, such as rebuilding its search index, and it stops on its own. Sometimes it is not. A nearly full disk, a login item that does not suit the new system, or a hardware fault all look the same from the chair. This guide gives you an order of operations that separates them, from free checks to reinstalling macOS, with a decision table near the end.

The steps follow Apple's published instructions as of October 2026. Some of those pages were last revised before macOS 27, so menu wording may differ slightly. Apple's release list shows macOS 27 only for Apple silicon Macs, so Intel Macs stay on Tahoe 26 or earlier.

Sort the slowdown into four buckets before you fix anything

Slowness after an update is four different problems that need opposite responses:

  • Catch-up. Deferred work: re-indexing, image analysis, scheduled scans. Fix: wait, plugged in.
  • Crowding. No headroom in RAM, storage, or thermal margin. Fix: free it or stop the load.
  • Conflict. A login item, extension, or helper misbehaves under the new system. Fix: update, disable, remove.
  • Fault. A damaged volume, failing hardware, or a broken installation. Fix: repair, service, reinstall.

Apple's slow-Mac page lists five causes (low disk space, memory shortage, incompatible apps, idle apps, disk problems) that map onto crowding, conflict, and fault. It never mentions catch-up work, which is why it feels unhelpful right after an update.

The three-day rule. Give catch-up three days of ordinary use, plugged in and awake a few hours a day, before concluding anything. Three days is our rule of thumb; we found no Apple-published duration. Howard Oakley, who writes the Eclectic Light Company blog on macOS internals, reports that several recent upgrades appear to have prolonged startup indexing, in some reports for days, though sparse logs make that hard to confirm. He prefers letting maintenance finish with the Mac awake, so a responsive but busy Mac can reasonably get longer. Heat and a full disk get no grace period.

Install pending updates first (System Settings > General > Software Update); Apple's safe-mode guidance asks for the same. To see what is pending from Terminal:

softwareupdate --list

Log a 30-second snapshot once a day

"It tapers" needs evidence. Run this at the same time each day:

ps -Aco pcpu,pid,comm -r | head -6        # top CPU users
sysctl vm.swapusage                       # swap in use
memory_pressure | grep "free percentage"  # share of memory free
df -h /System/Volumes/Data                # free space for your files
pmset -g therm                            # recorded thermal warnings

Note the top three processes, whether the Mac was plugged in, the Memory Pressure colour, and free storage. Catch-up shows as md* processes fading toward idle; trouble shows as the same process on top every day.

The background work macOS does after an update

Spotlight indexing. Spotlight keeps an index of your files, and an upgrade can leave it with work to do. Look for mdworker (often several copies), mds_stores, and mds. Oakley says slow indexing after an upgrade is not uncommon, and that rebuilding every volume's index can take many hours or days. On Apple silicon it runs almost entirely on efficiency cores, so Window > CPU History shows those busy while the performance cores stay mostly quiet (image analysis can use them).

Image analysis. mediaanalysisd, which Oakley's logs on macOS 26.2 show extracting text from images in the style of Live Text, and photoanalysisd appear in the first minutes after login. For scale, Oakley logged about 11 minutes of high Spotlight activity after an ordinary login on a Mac mini M4 Pro, with mediaanalysisd running repeatedly for about 6 minutes. That is one machine on a normal login, not an upgrade, and we have seen no published figures for after a major upgrade.

Routine upkeep. Time Machine backups wait five minutes after startup, and XProtect Remediator scans run about every 24 hours, only on mains power and under light load, per Oakley's write-up of macOS Tahoe.

How to tell catch-up from trouble

Catch-up: the busy processes are mdworker, mds_stores, mediaanalysisd, photoanalysisd, or backupd (Time Machine); Spotlight work sits mostly on efficiency cores; the app in front of you still responds; and it tapers across days.

Trouble: one process stays near the top of % CPU day after day while you are idle and plugged in; foreground apps are slow while background work runs; or mdworker keeps crashing and restarting. Oakley says that can happen when there is a bug or an importer meets a malformed file, and the log shows repeated crashes of the same process. His post covers Monterey and Ventura, so treat it as a lead; mdimport -L lists installed importers.

Warning: Do not rebuild the Spotlight index to hurry it along. Oakley writes that forcing a re-index is likely to take longer than letting maintenance complete, and the only good reason to rebuild is an index known to be damaged. mdutil -E / forces exactly that by erasing the Data volume's index.

Reading Activity Monitor, one tab at a time

Open Activity Monitor, choose View > All Processes, click a column heading to sort, and use the search field to filter by name. Then work through the tabs.

Tab Read this Apple's meaning Act when
CPU % CPU, high to low System: macOS's own processes. User: your apps. Idle: spare capacity One process stays on top for hours while you are idle
Memory Memory Pressure graph, Swap Used Green: RAM used efficiently. Yellow: might eventually need more. Red: needs more Yellow or red for long stretches, with Swap Used growing
Energy Energy Impact, Preventing Sleep Energy Impact is relative; lower is better An app you never use ranks high, or something keeps the Mac awake
Disk and Network Reads and writes; data received How much data moves md* or backupd writes confirm catch-up; a download you did not start is a Conflict suspect

Two details trip people up. Apple says free or unused RAM does not necessarily improve performance, so Memory Used near your total RAM is not a symptom; the pressure colour and swap are. Apple gives no percentage cut-offs for the colours, so read the trend. Reading Swap Used as a trend is our heuristic, not an Apple threshold, because one reading can mislead: a Mac running macOS 26.5.2 showed 16.6 GB of 17.4 GB swap in use while memory_pressure reported 37% of memory free.

kernel_task is the thermostat, not the culprit

Apple describes kernel_task as a process that helps manage CPU temperature. When the chip gets too hot, it makes the CPU less available to processes that use it intensely, which shows as high CPU use and more fan noise. It responds to heat rather than causing it, eases off as temperatures drop, and can respond "even if your Mac doesn't feel hot to you", so trust the command output, not the chassis.

A big number means look elsewhere: sort by % CPU, find the heavy process underneath, and quit it. Those are Apple's two steps. To see whether macOS has recorded throttling:

pmset -g therm

A Mac that has not been throttled reports that no thermal warning level has been recorded (the man page notes the command is not available on all platforms).

If kernel_task stays high with nothing heavy running and no warning recorded, Apple's article gives no further steps. Our suggestion is to test the hardware with Apple Diagnostics. Put the Mac on a hard, flat, ventilated surface and unplug everything except keyboard, mouse, display, Ethernet, and power. On Apple silicon, hold the power button until Options appears, release it, then hold Command-D until the Mac restarts; in macOS Tahoe 26 and later you then choose which diagnostic to run. On Intel, hold D at startup (Option-D if that fails).

Rule out a nearly full disk, login items, and browser extensions

Storage headroom. Apple lists low startup-disk space as a cause of slowness; check System Settings > General > Storage. Apple gives no minimum free-space figure, so we will not offer one. Our decision rule: if Memory Pressure is yellow or red, Swap Used is growing, and Storage shows little free, fix storage first. What's using space and what's safe to delete covers the clean-up.

Login items. Go to System Settings > General > Login Items & Extensions. Apple's guide describes Open at Login, where you select an item and click Remove, and App Background Activity, which lets apps perform tasks when they are not open, such as checking for updates or syncing data. Apple frames these settings for administrators of the Mac. Under Extensions, the Endpoint Security, Network, and File Providers categories cover security agents, VPN or content filters, and cloud-file providers; note them rather than switching them off blindly. Remove software you no longer use; leave the rest for the Safe Mode test.

Browser extensions. Quit your browser completely and watch whether CPU settles in Activity Monitor. If it does, relaunch with extensions off and re-enable them one at a time. The tab-overload system helps if the real problem is dozens of open tabs.

Isolate the cause with Safe Mode, then read the install history

Start in Safe Mode

Apple's safe mode instructions differ by chip. First install the latest macOS and app updates and unplug nonessential devices, as Apple recommends.

Apple silicon: shut down fully, then hold the power button until "Loading startup options" appears. Select your startup disk (usually Macintosh HD), hold Shift, click Continue in Safe Mode, and log in; you may have to log in twice.

Intel: turn on or restart the Mac, immediately hold Shift until the login window appears, then log in (possibly twice).

To confirm, look for "Safe Boot" in red in the login window, or hold Option, choose Apple menu > System Information, select Software, and check that Boot Mode reads Safe. Restart normally to leave. Safe Mode blocks login items and unneeded extensions, runs a basic startup-disk check, and clears some system caches, which Apple notes can temporarily free storage. Some features may not work as expected, including graphics performance, Wi-Fi, audio, and USB or Thunderbolt devices, so judge the test on basic responsiveness (typing, Finder, opening a document).

  • Fast in Safe Mode, slow normally. Something Safe Mode skips is responsible. Restart normally first, since the disk check or cache clearing may itself have helped. If slowness returns, disable login items in halves, restart, and keep halving. Apple also suggests a new user account (below).
  • Still slow in Safe Mode. Third-party startup items are off the suspect list, but a nearly full disk or too little RAM still counts, so rule those out. Apple's page points to reinstalling here; cheaper tests come first. A new user account is our addition for this branch, then First Aid and Apple Diagnostics.

Test a fresh user account

A new account starts without your login items, helpers, or app data.

  1. Open System Settings > Users & Groups, click Add User (you may be asked for your password), and choose Standard.
  2. Log in and wait about 15 minutes (our judgment, based on Oakley's roughly 11), since the account does its own first-login Spotlight work.
  3. Repeat the same slow task and compare the top process in Activity Monitor.

Our reading, not Apple's: fast there means the cause lives in your account, so prune login items and test apps one at a time. Slow there too points to the system or hardware: First Aid, Apple Diagnostics, then reinstalling. Delete the account afterwards; Apple's Add a user page points to the Info button beside a user's name for changes.

Match the slowdown date to the install history

Slowness has a start date, so compare it with what was installed. Hold Option, choose Apple menu > System Information, then Software > Installations (on macOS 26, the same list that system_profiler SPInstallHistoryDataType prints). Terminal offers two views:

softwareupdate --history
system_profiler SPInstallHistoryDataType

softwareupdate --help documents --history (by default only updates installed by softwareupdate), though the man page omits it on macOS Tahoe 26.5.2. system_profiler is fuller: it listed Apple and third-party installs, oldest first. We have not checked these commands on macOS 27.

Say the Mac turned sluggish on Tuesday, and the history shows macOS 27.0.1 at 08:12 and a VPN client's helper at 08:31. Those are your two suspects, in order; check the VPN vendor's update page first. We kept coming back to this "what changed, and when" question while building Tend's Timeline, which explains what changed across apps, startup items, storage, drives, battery, and backups. You do not need it for this step; the commands above work on their own.

Symptom to next step: a decision table

What you see Bucket Next step
md*, mediaanalysisd, or photoanalysisd busy after the update Catch-up Plug in, apply the three-day rule, do not rebuild the index
kernel_task high, Mac warm, fans loud Crowding (heat) Quit the heavy process underneath; run pmset -g therm
kernel_task high, nothing heavy running, pmset -g therm clean Fault (possible) Run Apple Diagnostics (our suggestion, not in Apple's kernel_task article)
Memory Pressure yellow or red, Swap Used climbing Crowding (RAM) Quit heavy apps and browser windows; check free storage
Memory Pressure green, laggy, little free storage Crowding (disk) Free space, then re-check
Slow for the first 10 to 15 minutes after login, then fine Catch-up or Conflict If mdworker, mediaanalysisd, backupd, or softwareupdated lead Activity Monitor, it is catch-up. If third-party helpers lead, trim Login Items & Extensions
Fast in Safe Mode, slow normally Conflict Disable login items in halves; try a new user account
Slow in Safe Mode too, storage and Memory Pressure ruled out Fault (possible) New user account, First Aid, Diagnostics, then reinstall
Slow in one app or browser only Conflict Update the app; disable extensions

When to reinstall macOS, and what to back up first

Reinstall when the cheaper steps are exhausted: catch-up has run its course, the Mac is still slow in Safe Mode and in a new user account, First Aid finds nothing, and Apple Diagnostics finds no fault. If Diagnostics returns a reference code other than ADP000 (Apple's "No issues found"), look it up in Apple's reference-code list and go to service instead.

For First Aid, follow Apple's Disk Utility guide: choose View > Show All Devices, then run it on each volume, each container, then the device. For the startup disk, do this from macOS Recovery and include "Macintosh HD - Data".

Apple says reinstalling does not remove your apps or personal data, but recommends a backup anyway. Before you start:

  • A backup finished recently.
  • The Mac is plugged in (our advice), lid open, sleep prevented (Apple's).
  • You know your login password; Recovery may ask for it.
  • You have Wi-Fi or Ethernet that uses DHCP. Apple says captive-portal logins, 802.1X, and PPPoE can block installation from Recovery.

On Apple silicon, shut down, hold the power button until "Loading startup options" appears, then click Options and Continue. On Intel, restart holding Command-R. Choose Reinstall macOS and expect several restarts and minutes of blank screen.

A reinstall does not roll you back. On Apple silicon it installs the current version of the most recently installed macOS, so a slowdown that comes from macOS 27.0.1 itself returns with 27.0.1. On Intel, Command-R does the same, Option-Command-R may install the latest macOS compatible with the Mac, and Shift-Option-Command-R the version that came with it, or the closest still available.

Warning: Because a reinstall keeps your apps and data, it cannot cure a problem caused by one of them, and it cannot fix a bug in the macOS build itself.

The short version

The order, from free checks to the last resort:

  1. Install pending updates.
  2. Plug in and log the daily snapshot for up to three days, unless the Mac is hot or the disk is full.
  3. Sort Activity Monitor by % CPU and read Memory Pressure.
  4. Free storage; prune Login Items & Extensions; test the browser.
  5. Test in Safe Mode, then a fresh user account.
  6. Match the slowdown date to the install history.
  7. Run First Aid, then Apple Diagnostics.
  8. Back up, then reinstall.

Tend is a free macOS app from LearnHubPlay for seeing what changed on a Mac. Everything above works with the tools built into macOS.

Frequently asked questions

Will a newer update fix this, or should I wait?

Apple's Safe Mode page calls installing the latest macOS and app updates the step most likely to fix a problem, so check Software Update first. As of 9 October 2026, Apple's release list shows 27.0.1 as the latest macOS, with Tahoe 26.7.1 and Sequoia 15.8.1 for earlier versions. None of the pages we used documents a known performance bug in a specific build, so treat such claims as unverified.

Can I keep working while macOS catches up?

Generally yes on Apple silicon. Oakley notes that Spotlight's maintenance runs mainly in the background on efficiency cores, so the impact on foreground work should be limited. A slow app in front of you is a trouble signal, not catch-up.

Activity Monitor shows nothing high, but the Mac is slow. What next?

Check Memory Pressure and Swap Used, then free storage and run First Aid, since Apple lists disk problems as a cause. Then test in Safe Mode and a fresh user account; if both are still sluggish, Apple Diagnostics is next.

Sources and further reading