Microsoft Edge auto-updates to 151/152 on macOS 12 (Monterey) and then won't launch

Question

Microsoft Edge auto-updates to 151/152 on macOS 12 (Monterey) and then won't launch

Liu Dongmiao 0

On a Mac running macOS 12.7.6 (Intel), Microsoft Edge was automatically updated from 150.0.4078.105 to 152.0.4191.53. After the update, Edge no longer launches.

Environment

macOS 12.7.6 (Intel, x86_64)
Microsoft Edge, Stable channel, machine-wide install
Version before update: 150.0.4078.105
Version after update: 152.0.4191.53
Installed automatically by EdgeUpdater, no user action

What happened

The machine was running Edge 150.0.4078.105.
EdgeUpdater ran an update check and installed 152.0.4191.53.
Edge no longer opens.

Edge 151 and later require macOS 13. This Mac cannot be upgraded past macOS 12, so any 151+ build leaves it without a working browser.

What I have tried

Reinstalling 150.0.4078.105 from the official package. This restores a working browser, but the machine is offered 152 again on the next update check.

Questions

Why are 151+ updates offered to a macOS 12 machine when those builds do not support macOS 12?
Is there a supported way to keep Edge on the 150 branch on macOS 12?

0 comments

2 answers

Your answer

Answer 1

Alex-L 12,575 Microsoft External Staff Moderator

Hi Liu Dongmiao

Since the issue occurs immediately after upgrading from Edge 150 and reinstalling Edge 150 restores functionality, the problem may be related to compatibility between newer Edge builds and macOS 12.

As forum participants, we do not have access to Microsoft Edge engineering systems and cannot determine why a specific update was offered to your device or whether this behavior is expected.

I recommend contacting Microsoft Edge Support and providing:

macOS version: 12.7.6 (Intel)
Last working Edge version: 150.0.4078.105
Version that stopped launching: 152.0.4191.53
Confirmation that the Mac cannot be upgraded beyond macOS 12

You can start here: Microsoft Edge Support

Only Microsoft support or the Edge team can confirm the intended update behavior and whether a servicing issue exists.

Hope you'll get this cleared out, feel free to update here if anything comes up!

Liu Dongmiao 0 Reputation points

2026-08-31T05:31:05.7066667+00:00

Thanks. The last version of Microsoft Edge supports mac OS 12.X is 150.X (https://learn.microsoft.com/en-us/deployedge/microsoft-edge-supported-operating-systems#macos). The problem is, auto update always update Microsoft Edge on macOS 12.X from 150.X to 151/152, event it's unsupported in macOS 12.X.

Answer 2

Harshith Ashok 80

Hi @Liu Dongmiao

You're not doing anything wrong here. Edge 150 was the last version that runs on macOS 12 (Monterey). Starting with 151, Edge needs macOS 13 (Ventura) or newer, per Microsoft's own docs.

The problem is the updater on Mac it doesn't check your macOS version before installing anything. It just grabs the latest release, even if it can't run on your machine. That's why it pushed you to 152, and Edge stopped opening.

There's no setting that keeps you on version 150 specifically. The closest thing is to turn off automatic updates entirely, which has the same practical effect. You do this by installing a small preference file that tells the updater not to check for updates. If your Mac is managed through something like Jamf or Intune, this is straightforward. If it's not centrally managed, it's harder to get it to stick reliably.

Keep in mind that freezing on 150 also means no more security updates for Edge on that Mac, since Microsoft has already ended macOS 12 support past that version. It'll get you working again in the short term, but it's not really a fix.

It's also worth checking whether that specific Mac model can actually take a newer macOS version than you think.

Liu Dongmiao 0 Reputation points

2026-08-31T15:50:53.7566667+00:00
Thanks. Currently, I use two ways:

a: mock as an enterprise device, then use managed preferences

b: add uchg flag to apps and crx_cache directory of EdgeUpdater directory

However, IMO, Microsoft Edge team should prevent Edge update to a version cannot launch.
Harshith Ashok 80 Reputation points

2026-09-01T00:08:28.7066667+00:00

Thanks for sharing both approaches, the uchg flag on apps and crx_cache is a neat one I hadn't seen documented before, and it's good to have as a fallback that doesn't depend on the managed preferences plist actually being read correctly.

One question on the uchg method: have you found it causes any side effects when Edge itself tries to write to those directories during normal operation (crash reporting)?

Trying to figure out whether this is safe to leave in place long-term or if it's better treated as a temporary lock to be removed periodically for manual maintenance.
Liu Dongmiao 0 Reputation points

2026-09-01T06:51:38.3133333+00:00

@Harshith Ashok I have checked to updater.log, it would still download the 151/152 edge, however, it cannot save to crx_cache or apps due to uchg flags, then cannot update.