Mike Peterson-xl.jpg)
Apple has resolved an issue that could brick some Intel-based Mac models equipped with T2 chips upon installation of macOS Monterey.
The company says that it has identified and addressed an issue with the firmware on the T2 security chip that prevented "a very small number of users" from booting their Macs after updating to macOS Monterey.
In a statement to Rene Ritchie, Apple says that the updated firmware is now included in existing macOS updates.
Statement from Apple on macOS issues. Full text in alt description: pic.twitter.com/zmSIjoUT48
— Rene Ritchie (@reneritchie) November 5, 2021
Apple also advises users who have been affected by the problem to contact Apple Support.
Earlier in the week, reports began circulating that macOS Monterey was causing some Intel-based Macs to become unresponsive after updating. The issue appeared to be related to the T2 security chip on Intel-based Macs, which drives features like Touch ID.
Mac models equipped with Apple's M1 were unaffected by this specific issue, since they lack T2 chips. Any firmware update involves some level of risk, though, and the issue can be rectified using Apple's Configurator utility, if it pops up.
In addition to the boot problem, a small number of users have also complained about memory leaks after updating to macOS Monterey.
Marko Zivkovic
Christine McKee
Andrew Orr
Malcolm Owen
Amber Neely
1 Comment
So far both: Big Sur and Monterey bricked both Ethernet ports on MacPro 2013. People reported this for last years, but no action taken.I worked with Apple support and they asked me... to run diskutility. Well my disk is new (OWC upgraded this year so to be able to move business with fresh installation of Big Sur and then Monterey and avoid potential loss of older system to avoid publishing business trouble - you have to have backup plans in business). Then I got bright idea from support people to create another user account and see if this is only on one account (for Pete sake if traceroute and ping low level tools have problem then it is system/hardware issue and not user account or applications!). Not so with any other macs or computers in this network. When installing 3rd part USB to Ethernet dongle with proper drivers the same happened. So resorting to Apple own Thunderbolt to Ethernet adapter still had the same issue, but this time not so frequently.
Apple needs to start paying attention to testing and stop pushing fault on customer hardware or applications. At minimum, train tech support on proper procedures to troubleshoot rather than evasive moves that do not give essential troubleshooting answers. After all some of us users spent in IT far more years than some of Apple hired people age.