What a clean install actually fixes, and what it does not
· 5 min read
“Just do a clean install” is the standard advice for a Mac behaving badly, and it is right often enough to survive as folklore. It is also an evening of work that frequently fixes nothing, because the problem was hardware, or a setting that gets restored along with everything else.
Knowing which class of problem you have saves the evening.
What a clean install genuinely fixes
Accumulated configuration nobody can find. Preference files from software removed years ago, launch agents pointing at missing programs, permissions granted and forgotten. This is the real case, and it is common on a Mac migrated across three or four machines.
A macOS installation that is damaged. Rare, and it happens: an interrupted update, a failing drive that has since been replaced, a system volume in an odd state.
Software you cannot remove cleanly. Occasionally something installs deeply enough that removing it by hand is unreliable.
A machine changing hands. Not a fix, and the right reason to do it. Erasing a Mac properly covers that case.
What it does not fix
Hardware. A failing drive, a swollen battery, a bad display cable, a machine that overheats. A clean install will feel better for a day because the machine is idle and unindexed, then the problem returns. Run Apple Diagnostics first. Apple Diagnostics covers it.
Not enough memory or storage. A Mac struggling because it has 8 GB and you run heavy applications will struggle identically after a reinstall.
A slow machine that is simply old. Newer macOS versions ask more of the hardware. Reinstalling the same version changes nothing.
Anything you then restore from a backup. This is the one people walk into. Clean install, then restore everything from Time Machine, and the configuration causing the problem comes straight back. If you are restoring the account wholesale, you have not done a clean install; you have reinstalled macOS.
Diagnose before you decide
Half an hour of narrowing beats an evening of reinstalling.
Try a different account. System Settings, Users & Groups, create a test account, log in to it, and use the machine. If the problem is gone, it lives in your account’s configuration and a clean install would help. If it persists, it is system-wide or hardware, and a clean install probably will not.
This single test is the most useful thing in this article and it takes five minutes.
Try Safe Mode. Boots with third-party extensions and login items disabled. If the problem vanishes, something you installed is responsible, and finding it is faster than reinstalling. Safe Mode covers what it proves.
Check the hardware. Apple Diagnostics, and check drive health and battery condition.
Look at what is running. A single misbehaving background process explains a great many “slow Mac” complaints. A Mac that is suddenly slow covers finding it.
If you do it, do it properly
The version that actually helps: erase, reinstall, and set up as a new Mac. Reinstall applications by hand. Copy your files back from a backup, but not your Library folder, and not your settings.
That is the whole point. Bringing ~/Library back brings the configuration you were trying to leave.
Expect a fortnight of small friction as you rediscover settings you had forgotten changing. This is the real cost and it is consistently underestimated.
Should you migrate or start clean covers the same trade-off when the machine is new rather than misbehaving.
The lighter version that often works
Before erasing anything, try the middle option: keep macOS and your files, and clear out the accumulated background clutter.
Go through System Settings, General, Login Items and remove what you do not recognise. Then check for launch agents:
ls -1 ~/Library/LaunchAgents /Library/LaunchAgents 2>/dev/null
Anything belonging to software you no longer have can go. Login items on a Mac covers doing this safely.
This resolves a decent share of the cases people reach for a clean install to solve, in twenty minutes rather than an evening.
Questions
Does reinstalling macOS erase my files? Reinstalling over the top does not; it replaces system files and leaves your data. Erasing first does. They are different operations and the menus do distinguish them. Reinstalling macOS without losing your files covers the safe version.
How often should I do a clean install? Never, on a schedule. Do it when you have a specific problem it addresses, or when a machine changes hands.
Will it make an old Mac faster? Briefly, and mostly because indexing has not run yet. If the machine is slow because it is old, this is not the fix. Getting another two years out of an ageing Mac covers what does help.
Should I reinstall the same macOS version or the latest? The latest your machine supports, unless you depend on software that needs an older one. Recovery offers different versions depending on how you enter it.