The macOS 27 upgrade checklist for power users: what resets, and the order to fix it
macOS 27 "Golden Gate" arrives on September 14, 2026. Every macOS 27 upgrade checklist you'll find says the same three things: back up, free up space, stay on power. That advice is correct and it is also the easy half. The hard half is what a major upgrade does to a Mac that has been configured — the accessibility grants your window tools depend on, the menu-bar utilities that quietly stop launching, the global hotkeys that something else has now claimed. None of that shows up as an error. It shows up as a shortcut that does nothing on Tuesday morning.
Here's the other half of the checklist.
Before you upgrade: five minutes that save an hour
Do this while the old system is still running, because afterwards you won't remember what was there.
- Photograph your permission lists. Open System Settings → Privacy & Security and screenshot three panes: Accessibility, Screen Recording, Input Monitoring. These are the lists that every keyboard utility, window manager, switcher, clipboard tool and text expander lives in. If an upgrade drops an entry, this screenshot is the only record you have of what used to be there.
- Screenshot your login items. System Settings → General → Login Items & Extensions, both the "Open at Login" list and the "Allow in the Background" list underneath it.
- Write down your global hotkeys. Not the ones inside apps — the ones that work everywhere: your launcher, your clipboard history, your window shortcut, your screenshot keys. Golden Gate claims at least one new system-wide chord (below), and a system shortcut always wins the argument against a third-party one.
- Check what you run that is still Intel-only. Apple has said Golden Gate is the last macOS that fully supports Rosetta 2. This upgrade is fine; it is the next one you should be planning for. Any x86-only app, plug-in, audio unit or command-line tool you rely on now has a visible clock on it.
Then do the ordinary part: a full backup you have actually verified, somewhere in the region of 50 GB free, mains power, and an evening rather than a Monday morning.
What macOS 27 changes that a power user will notice
Most of the Golden Gate coverage is about Siri. These are the bits that touch a keyboard-first setup.
- Intel Macs stop here. macOS 27 requires Apple silicon — M1 or later, plus the MacBook Neo. There is no partial tier. If you're not sure where your Mac lands, we covered the full list in macOS 27 supported Macs.
- ⌘Space is now "Search or Ask". Spotlight becomes a combined search-and-Siri field. If you have remapped ⌘Space to a third-party launcher, nothing about that breaks — but if you have not, the thing that appears is no longer the thing you were expecting.
- Visual Intelligence takes a new chord. Apple's release notes name ⇧⌘Space; coverage of the betas reports ⇧⌘6 as well, which was previously the Touch Bar screenshot shortcut. Either way that is a new global grab, and if one of them is a hotkey you already use, your app will simply stop receiving it.
- Rosetta 2 is on its last full release. Worth repeating, because it is the only item on this list with a deadline attached.
- Window management is essentially untouched. We went through this in detail in macOS 27 window management: the tiling system is the same one Tahoe shipped.
The macOS 27 upgrade checklist, in restoration order
Work down this list rather than across it. Permissions first, because almost everything else that looks broken is actually a missing grant.
| Check | Where | What it looks like when it's wrong |
|---|---|---|
| Accessibility grants | Privacy & Security → Accessibility | Shortcut fires, nothing moves or focuses |
| Screen Recording | Privacy & Security → Screen Recording | Window previews go blank or fall back to icons |
| Input Monitoring | Privacy & Security → Input Monitoring | A global hotkey is simply never seen |
| Login items | General → Login Items & Extensions | A menu-bar app is missing until you launch it by hand |
| Background items | Same pane, lower list | App runs but its helper doesn't |
| Global hotkeys | Keyboard → Keyboard Shortcuts | Your chord now triggers something of Apple's |
| Default browser / mail | Desktop & Dock, Mail settings | Links open in Safari again |
The failure mode people lose the most time to is the first row, and it is genuinely counter-intuitive: the toggle can still look enabled while the grant behind it is stale. The cure is to switch it off, switch it back on, and relaunch the app — or, when that doesn't take, remove the entry with the minus button and let the app ask again. We wrote the long version of that diagnosis in window manager not working on Mac, and the specifics of the Input Monitoring list in Input Monitoring on Mac.
Why keyboard window tools are the first casualty
There's a reason the tools that break first are the ones that move and focus windows: they are the ones that need Accessibility at all times, not once. A tiler that can't read the frontmost window can still draw its interface — it just can't do anything with it. A switcher that lost Accessibility can still be summoned and still can't raise the window you pick.
That is exactly the shape of it in our own apps, which is why they're a useful example rather than a sales pitch. Let's Tile needs Accessibility to read and move your focused window — without it the grid appears and nothing snaps. Let's Switch needs it to see your open windows and raise the one you choose; its Screen Recording grant is optional and only draws the live thumbnails, so if previews come back as names and icons after the upgrade, that's the pane to visit. Both list a single required permission on purpose: the fewer grants a tool needs, the fewer things an upgrade can quietly take away.
If you're rebuilding the keyboard layer from scratch anyway, the upgrade is a reasonable moment to check that the shortcuts you're re-entering are ones nothing else wants — Mac keyboard shortcut conflicts covers how to find out what already owns a chord.
Frequently asked questions
Should I upgrade to macOS 27 on day one? If your work depends on a stack of third-party utilities, wait a week and let those developers ship their compatibility builds. If your Mac is mostly Apple's own apps, day one is low risk. The thing that actually bites on day one is a niche plug-in or driver, not the OS.
Does upgrading macOS erase my settings? No — an upgrade is not a clean install, and your files, apps and most preferences carry across. What it can invalidate is the privacy database that stores per-app permission grants, plus the occasional login item. That's why this checklist is about grants and hotkeys rather than data.
Will my window manager still work after the upgrade? Almost certainly, once its Accessibility grant is healthy again. Check that first before assuming the app itself is incompatible — a stale grant and a broken app look identical from the outside.
Can I go back to macOS 26 if I don't like it? Not without erasing the Mac and restoring from a backup made before the upgrade. That is the real argument for the boring first step: downgrading isn't an undo button, it's a restore.
What happens to Rosetta 2? It still works fully in macOS 27. Apple has said this is the last release where that's true, so treat the coming year as the window to find Apple silicon replacements for anything x86-only you still depend on.