![]()
I tried everything over the phone with apple support to reinstall MacOs, nothing worked so I took it to get repaired. I’ve had this problem with my new M1 MacBook air after resetting to factory settings, and it was just a few days old when I had to return it. But i am pretty sure its all the same issue. #Mac os security update could not be verified install#Will try basic X509.”Īlso funny is that if i tried to install the original Yosemite version it fails as well □ But different log errors. It starts here “Sep 27 09:29:55 MacBook-Pro osinstallersetupd: Could not verify trust (5) using MobileSoftwareUpdate policy. Sep 27 09:29:20 MacBook-Pro osinstallersetupd: Mounting disk image complete, results dict = Sep 27 09:07:53 MacBook-Pro osinstallersetupd: Started downloading package .macOSBigSur ( ) ![]() Sep 27 09:07:53 MacBook-Pro osinstallersetupd: Retrieving 1 packages (12.429 GB) Sep 27 09:07:53 MacBook-Pro osinstallersetupd: Retrieving 0 packages (0.000 GB) I checked the logs and it all starts in this section: Just 12 minutes before finish i got this error. Same issue via recovery mode and installation from scratch. Before complete SSD wipe out it had the latest Bir Sur as for beg. #Mac os security update could not be verified pro#Its crazy how this article is from November 17, 2020, and today i found it because i had the same problem on MacBook Pro from 2015 (Model A1398). macOS Big Sur Reinstall on an Apple Silicon Mac running the shipping version 11.0 (20A2411) Credit MacRumors Forum user craigslorach. #Mac os security update could not be verified software#failed to personalize the software update. You will get this error.Īn error occurred preparing the update. ![]() When the macOS is reinstalling the Mac will attempt to personalize the version that is being installed. The only way to recover is by using a 2nd Mac with Apple Configurator 2!! It doesn’t matter if you are using macOS Recovery or Big Sur USB Installer, you will be unable to reinstall Big Sur!!! UPDATE 11/18/20 – I originally reported that this error would happen on a factory build of Big Sur 11.0 (20A2411) but it also happens if you are running 11.0.1 (20B29). UPDATE 11/19/20 – It looks like Apple has fixed the issue! I’ve just finished reinstalling macOS Big Sur from macOS Recovery and from a USB Installer drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |