User profile for user: xaxin
xaxin Author
User level: Level 1
14 points

Failed to upgrade to macOS Monterey

I'm upgrading my 2019 16 inch MacBook Pro from Catalina to Monterey seems that it failed and returned error at "14 minutes left"


Here's the log :


Mar 27 09:38:46 MacBook-Pro osinstallersetupd[548]: Using product PKSecureNetEnabledProduct <file:///System/Volumes/Data/macOS%20Install%20Data/> at distance 5
Mar 27 09:38:46 MacBook-Pro osinstallersetupd[548]: Extracting /Volumes/Shared Support/UpdateBrain.zip -> /System/Volumes/Data/macOS Install Data/UpdateBrain
Mar 27 09:38:46 MacBook-Pro osinstallersetupd[548]: Finished extracting: succeeded
Mar 27 09:38:46 MacBook-Pro osinstallersetupd[548]: Extracting /Volumes/Shared Support/com_apple_MobileAsset_MacSoftwareUpdate/a05f12dcce7b8581e814c3e73a7d5a72fa9e87e8.zip -> /System/Volumes/Data/macOS Install Data/UpdateBundle
Mar 27 09:39:01 MacBook-Pro osinstallersetupd[548]: Finished extracting: succeeded
Mar 27 09:39:01 MacBook-Pro osinstallersetupd[548]: Syncing extracted data to disk
Mar 27 09:39:01 MacBook-Pro osinstallersetupd[548]: Could not verify trust (5) using MobileSoftwareUpdate policy. Will try basic X509.
Mar 27 09:39:03 MacBook-Pro osinstallersetupd[548]: **** /System/Volumes/Data/macOS Install Data/UpdateBundle/AssetData/./payloadv2/basesystem_patches/arm64eBaseSystem.dmg != ./payloadv2/basesystem_patches/arm64eBaseSystem.dmg ****
Mar 27 09:39:03 MacBook-Pro osinstallersetupd[548]: Operation queue failed with error: Error Domain=com.apple.OSInstallerSetup.error Code=1004 "An error occurred loading the update." UserInfo={NSLocalizedDescription=An error occurred loading the update.}
Mar 27 09:39:03 MacBook-Pro InstallAssistant[539]: Stopped operation queue with Error Domain=com.apple.OSInstallerSetup.error Code=1004 "An error occurred loading the update." UserInfo={NSLocalizedDescription=An error occurred loading the update.}


Anyone has any idea on this?

Posted on Mar 26, 2022 8:00 PM

Reply
Question marked as Top-ranking reply
User profile for user: Gorilla
Gorilla
User level: Level 1
19 points

Posted on Apr 26, 2022 8:21 AM

Guys i am just coming over here from another discussion about this problem and also encountered this problem on my 2019 macbook pro 16" laptop. Went to genius bar did all fresh installs for weeks, had same problems of fresh installs not going through until i finally got lucky with a Big Sur install finishing. A week later still the same error. I finally found a developer thread in my developers forums that was discussing the same problem and one of the guys was suggesting to not run the apple diagnostics, but the standard memtest86. It is a command line tool, but there is a OSX compiled easy GUI version, called "Rember", that you can freely download here: http://www.kelleycomputing.net/Rember/

Please run this test and i am 99% sure it will show up with a memory error. So did mine and so did a bunch of others who ran the test. Unfortunately my laptop is out of warranty, so I would have to do a motherboard swap and pay the 680 bucks for that, which makes no economical sense. But the i realized, that this is somewhat weird??? How come that all these 2019 macbooks have this problem and all apparently upon upgrading either to the beta version of Monterey (which is the issue that came up in the developer forums) or upon upgrading to the release version of Monterey (if you are a regular customer). There has to be some sort of low level firmware that has to have triggered something within our machines, since it seems to only happen upon upgrading to Monterey. I feel there are probably some batches of faulty Memory chips soldered onto our Motherboards, which were fine under Catalina or even Big Sur, but once Monterey went onto our laptops, something triggered these to encounter the error we all encounter. Honestly i am more than mad that Apple seriously is not starting to acknowledge this and offers free repair. I can just smell a class action suit coming on and for my part i will not buy anymore of the soldered RAM or SSD laptops from them. Its a disgrace to go back and have these often failing RAM chips not replaceable, putting huge burden on environment and consumers pockets (and absolutely unnecessary). Please email to apple and complain. If enough people will do so, they will change their products. Thanks

View in context

Similar questions

19 replies
User profile for user: scrogers
scrogers
User level: Level 1
4 points

Apr 1, 2022 6:33 AM in response to dordal

Thanks dordal for the update. As you can see from my last post to P. Phillips, it sounds like you an I are in the exact same boat... and this Air will likely be going into Apple as well.


I do find it odd (or quite a coincidence) that there are three (at least) reports of essentially the exact same thing in a relatively recent and short period of time that is apparently damaging (or at least partially damaging) these computers, but stranger things have happened.


We shall see.

Reply
User profile for user: dordal
dordal
User level: Level 1
8 points

Apr 1, 2022 9:00 AM in response to scrogers

Out of curiosity, did any of you install the Catalina security update from a few weeks ago? 2022-03 https://www.macworld.com/article/623104/macos-big-sur-catalina-security-updates.html


I noticed that did a firmware update, and that's when my problems with kernel panics started (and when I first tried upgrading to Monterey). I suspect that may be the source of the problem... wondering if anybody else installed it.

Reply
User profile for user: Owl-53
Owl-53
User level: Level 10
102,301 points

Mar 30, 2022 2:14 PM in response to scrogers

Very much with most was what has been written.


The issue as I have observed, the moving up the Apple Food-Chain of newer version of macOS has become a bit more complicated and not nearly as straight forwards as in the " Good Old Days ".


Yes the standalone EFI updates are not longer and do not expect seeing then again.


Doing a measured upgrade through several versions to eventually Monterey does better prepare the computer with any Embedded EFIs in each newer version. The mismatch one refers to earlier, is eliminated by moving from Mojave to Catalina to Big Sur and then Monterey. Each previous version will or should update the EFI until the Monterey EFi and presto - should work fine.


Notation: Does this machine have an After Market Internal Drive installed. This Will be a thorn in your side if so. Monterey will verify if the Internal Drive is an Original Apple Drive. If not, Monterey will balk and fail to install with a error message


To get around this - replace the After Market Drive with the Apple Original and Install Monterey. The reverse this action and use the After Market drive and insatall Monterey to that Drive.


It, Monterey will need to Flash the Computer with the New EFI Boot ROM and thereafter all sould be good.



Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Failed to upgrade to macOS Monterey

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up