Mac settings that revert after a macOS update

17 September 2026 · 7 min read

After a major macOS update, most of your settings survive. The ones that appear to have reverted usually fall into three groups: new features that arrive switched on, preferences written to keys Apple has renamed or removed, and permissions the system asks for again. Each group has a different fix, and only one of them is worth doing anything about in advance.

A minor update (the third number changing) rarely touches settings at all. A major one, where the version name changes, is where this happens.

What genuinely changes, and why

New features default to on. An update that introduces a feature has to pick a default, and the default is usually enabled. Suggestion and lookup features, new Siri behaviors, new Safari options and new sharing defaults all arrive switched on regardless of what you disabled last year, because last year’s setting did not exist for this year’s feature. Nothing was reset; something new was added.

Preference keys move. Settings you changed with defaults write live in preference files keyed by name. When Apple reworks a feature, the old key can be ignored or removed. The old value is often still sitting in the file, which is why re-running your notes sometimes appears to do nothing: the command succeeds and the system no longer reads that key. What defaults write does, and how to undo one safely covers how to check whether a key is still live.

Permissions get re-asked. Accessibility, Full Disk Access, Screen Recording and input monitoring grants are sometimes cleared or invalidated for apps whose signature or version changed across the update. The app is not broken, it simply lost the grant and has to ask again. Reading a macOS permission prompt before you click Allow is worth a minute if you are about to click through several.

Login items reappear. Apps that install helpers often re-register them at their next launch, so a background item you disabled comes back.

What usually does not revert: Finder view options, Dock size and position, screenshot location, keyboard and trackpad settings, display arrangement, wallpaper, Safari bookmarks and extensions, and almost everything reachable through System Settings that existed before the update. If one of those looks wrong, the more likely cause is a different user account or a settings sync from another Mac.

A ten minute check after the update

Do this once, in this order, rather than discovering things over three weeks.

System Settings, Apple Intelligence and Siri, and Spotlight. Look for suggestion and lookup options that arrived enabled. Turning off Siri suggestions and lookups that send data off your Mac lists the ones that matter for privacy.
System Settings, General, Login Items and Extensions. Check what is set to open at login and what background items reappeared.
System Settings, Privacy and Security. Walk down Accessibility, Full Disk Access, Screen Recording and Input Monitoring. Anything unchecked that you rely on will silently misbehave until you notice.
Your own defaults write list. Re-run it and then verify one or two with defaults read, rather than assuming the write took effect.
Sharing and firewall. Check System Settings, General, Sharing and the firewall state, since a service you turned off can be on again after a rebuild.
Default apps. Browser, mail and the app that opens PDFs occasionally return to the Apple defaults.
Notifications for one or two noisy apps. New notification categories arrive enabled.

Keep the list itself somewhere durable. Writing down which settings you deliberately changed, and why, converts every future update from an archaeology exercise into a checklist. The first ten minutes of a new Mac makes a good starting list: see the Mac settings worth changing in the first ten minutes.

The Terminal checks worth knowing

To see the current value of a specific key rather than trusting memory:

defaults read com.apple.dock autohide-delay

If the key has been removed, the command reports that the domain or key does not exist, which is the answer you wanted. To see everything in a domain:

defaults read com.apple.finder

That output is long, so pipe it to grep for the setting you care about. After changing a Dock or Finder key, the change applies once the app restarts, with killall Dock or killall Finder.

For permissions, System Settings is the only reliable place to look. Editing the database behind it by hand is not supported.

Putting a set of changes back in one action

Re-applying a dozen settings by hand after every update is the part people stop doing by the second year. There are two reasonable ways to avoid that.

Write a shell script containing your defaults write lines and the killall commands at the end, keep it with your documents, and run it after an update. It is free, it is yours, and its weakness is that it silently does nothing when a key has been renamed, which is exactly the failure mode described above.

Or use something that treats the settings as a set. Mainspring exposes more than ninety of these hidden macOS settings as plain-English power-ups, each snapshotted before it changes so it flips back in one click. The relevant part after an update is Recipes, which are curated bundles applied as a set and reverted as a set (Snappier Mac, Privacy and Security, Finder Power, Screenshot Studio and others), and Scenes, which are your own mix of power-ups that can apply themselves on triggers such as time of day, connecting a display or an app opening.

For this specific problem, the value is that re-applying your preferences is one action rather than a dozen, and that each power-up is labeled by what it does rather than by a preference key you have to look up. It runs on macOS 13 Ventura or later, is local only apart from a license check, and is not on the Mac App Store because some power-ups need access the sandbox forbids. It is $29 once for up to three Macs with a free one-day trial. Everything it does is a real macOS setting you can also change yourself with the steps above.

When something looks reverted but is not

Before you re-apply anything, rule out these.

You are in a different user account. Settings are per-user. A Mac that was set up with a second admin account during troubleshooting can drop you into the wrong one at login.
Another Mac pushed a change. If two Macs share an Apple Account, some settings sync. Setting up a second Mac so both feel like the same machine covers what travels.
A managed Mac re-applied policy. On a work Mac, a configuration profile can enforce settings and quietly restore them.
The setting moved. Apple reorganizes panes between versions. Use the search field at the top of System Settings rather than the sidebar.

Questions

Should I delay a major update to avoid this? Waiting a few weeks after a major release lets the first round of fixes land and gives third-party apps time to catch up, which is a better reason to wait than settings. Security updates should not be deferred.

Will a clean install avoid the problem? No, it guarantees it. A clean install starts from every default. It solves different problems, as what a clean install actually fixes explains.

My screenshot folder went back to the Desktop after an update. Is that normal? It is uncommon but it happens, usually when the preference file for the screenshot service is rebuilt. Setting it again takes a moment: change where a Mac saves screenshots.

Is there a way to see what the update actually changed? Not directly, and no reliable log lists it. The practical substitute is to note your own deliberate changes beforehand, then check that list afterward.