Mac maintenance
How to Update macOS the Right Way (Without Bricking Anything)
Step-by-step guide to updating macOS safely. Pre-update prep, the actual update process, what to do during, and the post-update audit that catches problems early.
A macOS update fails in some way maybe 1 in 50 times — stuck progress bar, login screen loop, lost preferences, broken VPN. The good news: most of those failures are preventable with 20 minutes of prep beforehand. The other good news: of the failures that do happen, almost all are recoverable if you have a backup.
Here’s the actual sequence I follow on every Mac I update.
Before you start: the four prerequisites
Run through these before clicking Update:
- Take a Time Machine backup. Full backup, completed successfully, on an external drive. Verify it actually finished — don’t trust “yesterday’s backup.”
- Check disk space. You need 30–35GB free, not the 12GB the installer is. macOS stages the entire update.
- Plug in. Don’t update on battery alone, even on a laptop.
- Pick a time you can afford to lose. Two hours minimum, possibly more. Friday evening is ideal — if something breaks, you have the weekend.
If any of those four aren’t true, fix them before proceeding.
Optional but smart: clone backup
A Time Machine backup is good. A bootable clone is better.
Tools like Carbon Copy Cloner or SuperDuper create an exact bootable copy of your current macOS on an external drive. If the update goes badly, you can boot from the clone in five minutes and be back to work. Time Machine restore is more like a 30–60 minute operation.
For Apple Silicon Macs, “bootable clone” is more limited than it used to be — Apple Silicon needs to boot from internal storage for OS-level operations. But the clone is still useful as a complete file backup beyond Time Machine.
What kind of update are you doing?
Two distinct types, with different stakes:
Point release (e.g., 15.4 → 15.4.1)
Small. Usually security and bug fixes. Low risk. Often takes 15–25 minutes total. The pre-flight checklist still applies but you can be less paranoid.
Major version (e.g., Sonoma → Sequoia)
Big. Replaces the OS. Higher risk. Takes 60–120 minutes. Needs the full pre-flight checklist.
Be more careful with major version upgrades. Apple’s marketing pushes you toward the new version aggressively; your prep should be proportional.
Pre-update steps in order
Step 1: Check current version
Apple menu → About This Mac. Note the version (e.g., “Sonoma 14.7.2”). Useful if you need to roll back.
Step 2: Run a Time Machine backup now
System Settings → General → Time Machine → Back Up Now.
Wait for it to finish. Verify in Time Machine’s interface that the backup completed without errors.
If you don’t have a Time Machine drive, get one. A $40 1TB external SSD over USB-C is the cheapest insurance against losing your data.
Step 3: Check disk space
System Settings → General → Storage. The “Available” number at the top is what matters.
If you’re under 30GB free for a major upgrade or under 15GB free for a point release, clear space first. Quick wins:
- Empty Downloads
- Empty Trash
- Delete old iOS backups in
~/Library/Application Support/MobileSync/Backup/ - Trim Time Machine local snapshots:
for snap in $(tmutil listlocalsnapshots / | awk -F. '{print $4}'); do tmutil deletelocalsnapshots $snap; done
Step 4: Disable third-party security software
If you have a third-party VPN, antivirus, or endpoint security tool, temporarily disable or uninstall it. These commonly conflict with macOS updates and can cause boot loops or login failures post-update.
Specifically watch for:
- Cisco AnyConnect, GlobalProtect, Pulse Secure (corporate VPNs)
- Norton, McAfee, Sophos, Malwarebytes (consumer security)
- Cylance, CrowdStrike, SentinelOne (endpoint security on work Macs)
You’ll re-enable after the update.
Step 5: Quit everything
Save your work. Quit all apps via Cmd+Q (not just close windows). Close all Finder windows.
The update will force-quit anything running, but a clean shutdown beforehand is safer.
Step 6: Plug in
If laptop, plug into power. Don’t run an update on battery.
If you’re on a less-than-fully-stable internet connection (hotel Wi-Fi, mobile hotspot), wait until you have something better. Updates download large files and a dropped connection mid-download can produce a corrupted installer.
The actual update
System Settings → General → Software Update.
Click Update Now for a point release or Upgrade Now for a major version.
Enter your password when prompted. The Mac will:
- Download the installer (10–15 minutes for a point release, 30–60 minutes for a major upgrade, depending on connection).
- Verify the download.
- Restart and begin installation.
- Multiple progress bars at multiple stages.
- Restart again. Possibly multiple times.
- First-boot setup tasks.
Walk away. Don’t poke at the Mac while it’s working. macOS updates do real work after the visible progress bar finishes, and the timer estimate is famously unreliable.
What to do if the update appears stuck
Definition of stuck: no visible progress for over two hours, no fan activity, no caps lock LED response.
If the Mac is truly frozen:
- Apple Silicon: hold the power button for 10 seconds to force shutdown. Wait 10 seconds. Press power once.
- Intel: same. Hold power for 10 seconds.
When it boots back up, the update typically picks up where it left off and finishes. Don’t panic-restart at the first sign of slowness; only restart after extended unresponsiveness with no signs of life.
For more depth on this, see our guide on unsticking a stuck macOS update.
Post-update: the audit
After the update completes and you log in:
Step 1: Wait an hour
Plug in, leave the Mac alone for an hour. macOS does background work after first boot:
- Spotlight reindex
- Photos analysis
- iCloud Drive sync
- Apple Intelligence model downloads (if applicable)
- Mail content reindex
If you start using the Mac immediately, everything feels slower than normal. That’s not the update’s fault; it’s the post-install work.
Step 2: Audit login items
System Settings → General → Login Items & Extensions. Two lists:
- Open at Login
- Allow in Background
Major macOS upgrades sometimes re-enable third-party background helpers you’d previously disabled. Adobe, Microsoft, Google, Dropbox, and similar updaters are common offenders.
Turn off anything you don’t need running.
Step 3: Check critical apps
Launch each app you depend on for daily work. Confirm:
- It opens without errors
- It can read your existing files
- Plugins (in DAWs, video editors, browsers) still work
- Network features (VPN, sync) still function
If something broke, the vendor usually has a guidance page within days of a major macOS release.
Step 4: Re-enable security software
Turn back on the antivirus or endpoint security tool you disabled before the update. Update it to the latest version first if available.
Step 5: Verify backups still work
Run a manual Time Machine backup to confirm it completes successfully on the new macOS. Do this within the first 24 hours so you have a clean post-update backup.
Common post-update issues and fixes
Login screen rejects password
Most often: the keychain didn’t migrate cleanly. Restart in Safe Mode (hold Shift on Intel, hold power button on Apple Silicon then choose drive while holding Shift). Log in. Then restart normally.
App won’t launch
Quit and relaunch. If it still fails, reinstall the app. If still failing, check the vendor’s macOS compatibility page.
Wi-Fi or Bluetooth flaky
System Settings → Network → click the (i) next to your Wi-Fi → Forget. Reconnect with password.
For Bluetooth, often resolves on second restart.
Mail won’t sync
Mail → Window → Connection Doctor. Often shows what’s broken.
Performance worse than before
Almost always cache-related. Clear Slack/Chrome/Xcode caches, audit login items, restart. See our version-specific speed guides for your macOS.
External monitor not working
System Settings → Displays. Hold Option, click “Detect Displays.” If still nothing, restart with the monitor connected.
When to roll back
If post-update problems persist beyond a day of troubleshooting, rolling back is reasonable. See our rollback guide for the procedure.
The decision to roll back vs. troubleshoot longer comes down to:
- How much time you’ve spent already
- Whether the issue is blocking essential work
- Whether the next macOS point release is imminent (might fix it)
For most users, giving it 48 hours and one .x.1 release before deciding to roll back is sensible.
What I do every September
My personal cadence on a Mac I depend on:
- Read the launch coverage week one.
- Read the issue reports week two.
- Wait for the .x.1 release (usually mid-October to early November).
- Take a verified Time Machine backup that morning.
- Update Friday evening.
- Audit login items and run cleanup Saturday morning.
- By Monday, back to normal work.
That cadence has avoided most early-version pain over the last several macOS releases.