Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

macOS Monterey may be bricking some Macs - but there is a fix

Last updated

Reports are circulating that macOS Monterey is causing problems with a small quantity of upgraders and new MacBook Pro owners — but the issue appears to be less prevalent than in previous years, and there is a user-executable fix for most recent machines.

Apple's macOS updates, especially new releases, contain one or more firmware updates to assorted chips in the Mac including GPU, storage, the T1 or T2 chips, and more. If interrupted, or if impacted by other factors, a firmware update can fail, and leave a machine in an unusable condition.

This has been happening off-and-on for years, and is most common with new macOS versions that launch in the fall.

Based on AppleInsider collated service data, the problem with Monterey to date is less prevalent than in previous years versus an equivalent time after release. It isn't clear if macOS Monterey's adoption rate is any different than other years, which could impact the estimate — but it would require half the rate of Monterey adoption versus Big Sur to make a swing to upgraders in 2021 being impacted at a higher rate than any OS of the last five years.

The problem also seems to impact T1-equipped Macs at a higher rate than T2-equipped models.

All of this is, of course, cold comfort to those impacted.

First reported by MacRumors on Monday, users are reporting completely dead machines following a macOS Monterey update. Apple is being asked to step in and help — but there is already a troubleshooting procedure in place.

Apple has a restoration process for T2 machines, if the user has access to a second Intel-based Mac. Apple's Configurator tool can revive the firmware on a security chip, without erasing data, making any changes to the startup volume, the user's data volume, or any other associated internal storage volumes.

Apple has specific restoration instructions for T2 machines in a support document. A similar document and procedure exists for Apple Silicon, should the problem arise with future macOS revisions, or following the macOS 12.0.1 update on a new machine.

At present, AppleInsider suggests that T1-based machines should be brought in to an Apple Store for evaluation. Apple stores are replacing machines impacted by the problem that are under warranty, without performing the revivification through Configurator or any kind of data migration.



15 Comments

Fred257 5 Years · 259 comments

Always best to wait a while before updating software.

Sebiak 3 Years · 2 comments

My 2019 MacBook Pro with Touch Bar has been bricked while applying Mac 11.8.1, last Tuesday.
A local certified retailer told me I've to change mother board + Touch ID module. I refused.
Anyway, after discussing with Apple Support and following its suggestion, I took an appointment to an Apple Store.
So I still have hope. 

Mike Wuerthele 8 Years · 6906 comments

Sebiak said:
My 2019 MacBook Pro with Touch Bar has been bricked while applying Mac 11.8.1, last Tuesday.
A local certified retailer told me I've to change mother board + Touch ID module. I refused.
Anyway, after discussing with Apple Support and following its suggestion, I took an appointment to an Apple Store.
So I still have hope. 

I'd try the Configurator solution first, if Apple Support didn't tell you to do so.

miah 3 Years · 3 comments

My 2019 MacBook Pro was bricked while updating to 11.6.1. I'm still under AppleCare and called Apple. They said I'd have to take the computer into my local 3rd-party Apple dealer for evaluation. That dealer found that the T2 was "stuck," but they were able to "reset" it. I presume they used the Configurator method mentioned here, but I'm not sure. The problem is, they charged me $75 for their half-hour of time, a fee I don't feel I should be responsible for since it was Apple's software/hardware that caused the problem. I will take this up with Apple and hopefully get reimbursed. NOTE: Fix restarted my bricked machine and no data was lost.

Mike Wuerthele 8 Years · 6906 comments

miah said:
My 2019 MacBook Pro was bricked while updating to 11.6.1. I'm still under AppleCare and called Apple. They said I'd have to take the computer into my local 3rd-party Apple dealer for evaluation. That dealer found that the T2 was "stuck," but they were able to "reset" it. I presume they used the Configurator method mentioned here, but I'm not sure. The problem is, they charged me $75 for their half-hour of time, a fee I don't feel I should be responsible for since it was Apple's software/hardware that caused the problem. I will take this up with Apple and hopefully get reimbursed. NOTE: Fix restarted my bricked machine and no data was lost.

I'm sure they used Configurator to fix it.

Do try to get reimbursed, but don't count on it.