Failed to update macOS 12.3

I have the same problem.

It is the second time that this issue happened when I tried to update my MacBook Pro 2021 with a M1 Max. The first time they replaced the logic board. I now have again an appointment at the local Apple support. I cannot believe it.

Michael

My MacBook Pro (16-inch, 2021) was yet another victim of a coffee spill (someone else's!) and had almost every component replaced (including the main logic board) when it was repaired. I saw the news about macOS 12.3 failing to install on these models if the logic board had been replaced, before I had time to install that update, so I did not even try, and waited to hear further news.

With macOS 12.3.1 mentioning an install problem had been fixed, I decided to risk it. After doing two backups, I updated from macOS 12.2.1 to 12.3.1 via Software Update. Worked just like a normal update, no strange problems at all.

Unfortunately the Mac could not be revived. It would enter the same cycle like 12.3 - not installing it.

But, I ended up restoring it (losing all data - good thing is I had all important things on backup but I lost some not important stuff) and I installed 12.3.1 - all through DFU Mode - and thankfully is now working.

Apple Support wanted to have my logic board replaced (with me paying it), thank God I waited for the next version and didn't do it. It is unbelievable they don't even inform their Support and Stores and didn't even give a heads up to people..

Problem solved with 12.3.1 - my MBP 14" is successfully updated with this version, the logic board was replaced twice and didnt solve it, but 12.3.1 did the job!

Revive or restore a Mac with Apple silicon using Apple Configurator 2

The Apple Configurator 2 is available on the apple Apps Store

Should it fail again, I would get to an Apple Store for evaluation.

Thanks for the update! Yeh, the main issue is none of us (even Genius Bar techs) can get full debug logs of why the firmware fails to load - that’s going to require specialist hardware they only have somewhere they actually design the hardware I think.

All we can see if that the firmware update gets submitted and when it boots to do that update, clearly fails.

I’ve got a Genius Bar appointment tomorrow but based on other reports they’ll offer to do a logic board replacement and if that still fails do a full machine swap given it only affects the new macs, the oldest are only going to be 6 months old and this is a failure related to a previous repair.

Was able to connect with Apple Support. Was told on Saturday (apologies for the delay in posting) that Apple engineering is aware of this issue and are working on a fix. It does seem to be related to those of us that have had logic boards replaced. No ETA on a fix, but I was told I would get a call/email letting me know a fix was available. My support contact said he believed it would come in the form of a new software update, perhaps 12.3.1 or a patch to 12.3, but the issue would be called out in release notes. It appears a fix is on the way.

Hope this is helpful.

THIS IS A FAILURE OF APPLE'S!!! The update of death has been known for a couple of weeks now. Not only is Apple not warning folks about it:

• 12.3 still appears as an update option for my MBP with a replaced logic board - I was lucky, I only got into an upgrade loop...it didn't brick my machine...but the upgrade is still showing up as available!
• I was in the mall this weekend and asked the guy checking people in about it. His response, and I admire his honesty, was 'Yes, you're right; it's a huge problem and Apple hasn't told us anything. Nothing. So wait for a new version.'

What is so bad, Apple, that you're choosing to knowingly brick machines, not warn your customers about it and you're leaving the update for unsuspecting users who will suffer the same fate???

For me, this is a huge trust issue...Apple, it's time to do the right thing.

Oh I forgot that Intel Macs are different. I believe you could first try reinstall in recovery mode, or revive it in Apple Configurator 2. If those won't work, then try making a USB installer.

If you search "macOS Monterey InstallAssistant.pkg" on search engine, you could find some websites providing links to download specific versions of macOS. Use your other Mac to download and open it, it will extract "Install macOS.app".

Then create a bootable installer: How to create a bootable installer for macOS - Apple Support

And try installing using it.

You can definitely have a try of 12.3.1, it is said to fix the issue with M1 Pro/Max, but worth trying.

Go to Apple Store if you still can't restore it.

[Edited by Moderator]

I'm in the same situation. Sending it to Genius Bar will not resolve the issue, I believe now the only thing that users could do is to wait until Apple release a new version that is able to install on those Macs that have this issue. I don't think the this will damage the hardware, in fact, this only happens if I try to install macOS 12.3, if I use Apple Configurator 2, I am able to install all previous versions of macOS, but not 12.3. Just don't do updates anymore and wait, cause some people reported that system won't boot after updates and require a restore, and in this case you basically have to erase it so all data is gone.

12.3.1 has just been released... hopefully this solves the problem!

Have run Beta software previously?

Has the user ( you ) un-enrolled from Beta Testing ?

The Beta software could have done something negative to the iBridge ROM which is showing up with a failed Public Released version of Monterey 12.3.

If after downloading the Full Released Version of 12.3 and attempting the installation - should it fail again, I would get to an Apple Store for evaluation.

I suspect all an Apple Store will do is call it a logic board replacement, which won't actually help as it will just fail to update to 12.3 again until they ship with 12.3 on them, and just leave you without your Mac for a few days... the only way this issue is resolved is with a subsequent update from Apple.

But the first step needs to be someone there being aware of the issue to organise the fix - though I get people going to the Apple Store might be how they start noticing this pattern as I doubt they read these forums.