[Solution] Error updating the Minecraft Launcher on macOS 26

When the Minecraft Launcher on a Mac fails with “unable to update the launcher” (or the older “Unable to update the Minecraft Native Launcher”), the cause is almost always one of two things: a corrupted update cache the launcher can't overwrite, or macOS blocking the launcher from modifying itself. Both take about two minutes to fix.

What's actually going wrong

The launcher updates itself by downloading a new copy of its UI bundle into ~/Library/Application Support/minecraft/launcher and swapping files inside it — including a large embedded browser framework (Chromium Embedded Framework). If an update is interrupted halfway, or macOS refuses the file swap, the folder is left in a state the updater can't repair, and every launch after that fails with the same error. You can see it yourself: the folder ~/Library/Application Support/minecraft keeps logs named nativeUpdaterLog.txt, and the failing line is typically an update error on the Chromium framework inside launcher.bundle.

Fix 1: Quit the launcher completely

A background launcher process keeps the broken files locked. Press Cmd + Q with the launcher focused (closing the window is not quitting on macOS), and if it was mid-update, open Activity Monitor and force-quit anything named Minecraft. Then relaunch once — sometimes a clean restart is all the updater needed.

Fix 2: Delete the stuck update cache

This is the fix that works for most people. In Finder:

• Press Shift + Cmd + G to open “Go to Folder”.
• Type ~/Library/Application Support/minecraft and hit Enter.
• Delete the folder named launcher — it's only the launcher's own bundle and update cache.
• Open Minecraft.app again. It downloads a clean copy of itself and starts normally.

Prefer the terminal? Same thing in one line:

rm -rf ~/Library/Application\ Support/minecraft/launcher

Deleting the launcher folder never touches your worlds. Saves live in the saves folder and installed game versions in versions, both siblings of the folder you just removed. Worst case, you sign in to your Microsoft account again.

Fix 3: Check App Management permissions

Recent macOS versions gate “one app modifying another app” behind a permission — and a self-updating launcher is exactly that. Open System Settings → Privacy & Security → App Management and make sure the Minecraft Launcher is listed and enabled, then retry the update. On macOS 26 this list is stricter than it used to be (non-bundled tools like a bare Java install can't even be added), so a launcher that updated fine last year can start failing after an OS upgrade.

Fix 4: Reinstall the launcher fresh

If the update still fails, stop fighting the updater and replace the app wholesale: drag Minecraft.app from Applications to the Trash, download the current macOS installer from minecraft.net, open the .dmg, and drag the new app into Applications. You get the latest launcher directly instead of asking the broken one to update itself. Your data folder is untouched, so worlds, versions, and settings are all still there.

Still stuck?

The long tail, roughly in order of likelihood: your disk is nearly full (the updater needs room to stage the new bundle); an antivirus tool is quarantining the downloaded update mid-swap (add an exception for the launcher); or a school/office network is blocking the download (try a different network once to confirm). If the error mentions the Native launcher on a genuinely old macOS, the reinstall in Fix 4 is the reliable path — the modern launcher replaced that updater entirely.

And if the reason you're fixing the launcher is to get back on a server with friends — that part doesn't have to live on anyone's Mac. A hosted server stays online and up to date on its own, whatever your local launcher is doing.