Failed To Personalise the software update. Please try again

Hi all


I am at my wits end with this MacBook Pro M1.

I am never able to install any update that comes. To get into Sonoma (and because i had issues previously updating) i contacted apple and they basically had me reinstall MacOs then update and then restore from my backup. I am not doing this every time an update comes out)


Is there a way to fix this? I have tried a number things including below


1: Safe mode (which does not work)

2: Re-install MacOs completely (works but is not ideal) then restore all my files from a backup.

3: Contact apple support (again said to do above which i did for Sonoma but again for the new update its doing the same issue again)

4: followed the instructions on the Apple website if you get an error installing macOS.


Any help would be grateful as it's driving me insane.


Macbook Pro M1

Sonoma V14 - trying to upgrade to 14.1.1

16GB Ram

1TB Hard Drive (not even half full)


MacBook Pro 13″, macOS 10.13

Posted on Nov 14, 2023 12:48 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 20, 2024 12:21 PM

***UPDATE***

I have been playing with this for a while, the issue always seemed to occur/start after I had transferred my data via the transfer wizard from my old 2013 MacBook Pro (High Sierra). So thought I would fresh install the new macbook M1 and then manually transfer all my files (software is easy to get). Since doing this I have had no issues at all.

Must be something to do with the settings or the way High Sierra is set up causing the update function not work.

23 replies
Question marked as Top-ranking reply

Jan 20, 2024 12:21 PM in response to MadMax889

***UPDATE***

I have been playing with this for a while, the issue always seemed to occur/start after I had transferred my data via the transfer wizard from my old 2013 MacBook Pro (High Sierra). So thought I would fresh install the new macbook M1 and then manually transfer all my files (software is easy to get). Since doing this I have had no issues at all.

Must be something to do with the settings or the way High Sierra is set up causing the update function not work.

Mar 9, 2024 10:54 AM in response to eva-marie241

Apologies for the delay I missed your message initially. So I bought the new to me m1 MacBook pro and started the transfer wizard straight away. Then started having the issues. Re-installed Mac OS a number of times which would initially work with the updates.Once I carried out the transfer wizard it would cause the issue again. I re-installed Mac OS again did the updates and manually transferred my files and re-installed my apps manually (a long process but worth it in the end for a working system) and all has been ok since. No issues whatsoever. Hope this clarifies.

Nov 14, 2023 12:57 PM in response to MadMax889

MadMax889 wrote:

Hi all

I am at my wits end with this MacBook Pro M1.
I am never able to install any update that comes. To get into Sonoma (and because i had issues previously updating) i contacted apple and they basically had me reinstall MacOs then update and then restore from my backup. I am not doing this every time an update comes out)

Is there a way to fix this? I have tried a number things including below

1: Safe mode (which does not work)
2: Re-install MacOs completely (works but is not ideal) then restore all my files from a backup.
3: Contact apple support (again said to do above which i did for Sonoma but again for the new update its doing the same issue again)
4: followed the instructions on the Apple website if you get an error installing macOS.

Any help would be grateful as it's driving me insane.

Macbook Pro M1
Sonoma V14 - trying to upgrade to 14.1.1
16GB Ram
1TB Hard Drive (not even half full)


https://discussions.apple.com/content/attachment/8904d891-0517-4a57-9f22-231b8bc4327e



reference—

If an error occurred while updating or installing macOS - Apple Support



alternatively you can try from the Terminal.app copy and paste:

sudo softwareupdate -i -a -R



this will bypass the secure token/owner check from the Software Update pref pane:


-i Install

-a All appropriate updates

-R Automatically restart (or shut down) if required to complete installation)




Jan 18, 2024 5:16 PM in response to HWTech


I have seen enough reports from others who have tried a clean reinstall (and found it doesn't work) to not spend the many hours this would take me. That this technique ultimately doesn't work is not surprising, since the problem is not due to a corruption within the MacOS system software residing on the drive, but a corruption at the most basic firmware level of the CPU.


Yes, I did also try the "create a new MacOS admin account" trick - but that also didn't work.


A frustrating problem. This MacBook still runs perfectly in every other respect. The only reason I am going for the main board replacement is because it still has a few months of warranty left on it, otherwise it would be a cost-prohibitive solution and I would just live with it stuck at MacOS 13.4.1


Jan 20, 2024 4:20 PM in response to MadMax889

Re the most recent posting by "MadMax889" stating:

"I have been playing with this for a while, the issue always seemed to occur/start after I had transferred my data via the transfer wizard...."


This is an interesting observation. I wonder how many people who have this problem (myself included) originally used the data transfer wizard to migrate data and applications from an "old Mac" to a "new Mac".


Clearly there are a number of different causes for the "Failed to personalize the software update..." error. The easiest of these causes to solve is when something is blocking the installer's attempt to authenticate the Mac with Apple's server. Solutions like using a bootable standalone installer, or installing while in "safe mode", helps get around this issue. The cause for the problem MadMax889 and I have encountered is more insidious, likely related to an inability of Apple's software update server to authenticate the Mac's identity buried in the Apple Silicon (or previous T2 chip), causing the server to reject installation of the software update. This latter problem is very difficult to fix - and it seems to me Apple's support people really have no clue how to do this either. Sometimes it can be done with a very complete wipe and "de-registration" of the Mac followed by "reactivation" of the Mac as if from brand new followed by reinstallation of everything manually - there is a complicated Youtube video explaining how to do that. However, if all else fails it requires a main logic board replacement. As to the root cause for why this happens in the first place - just possibly use of "migration assistant" is one cause. Regardless, this seems to me a vulnerability in the Mac system software design the engineers should have anticipated.

Jan 18, 2024 4:05 PM in response to MadMax889

I am going to add another data point to this discussion.


I have encountered exactly the same issue, but on an M2 Max MacBook Pro. Absolutely none of the solutions discussed above (or anywhere else for that matter) have solved the problem.


I was instructed by Apple Support to have an Apple service centre perform a "Revive" procedure, though the tech in the service centre warned me this would likely not work either - and he was correct. The only remaining solution is a main logic board replacement, since likely there is a corruption of the security firmware built into the Apple Silicon M2.


Nice going Apple. First computer I've ever owned requiring a main logic board replacement because its own "security" refused to allow an OS upgrade.


Jan 18, 2024 4:45 PM in response to Henry B.

I would do a clean reinstall of macOS to see what happens. This involves erasing the disk or bettery yet by a DFU firmware "Restore"....nothing left to lose.


Did you try to create a new admin macOS user account especially after the DFU firmware "Revive"? The new Apple Silicon Macs have a new concept of "Ownership" which complicates things even more which is why I would recommend a DFU firmware Restore.


Unfortunately this is the type of stuff that happens when everything is controlled by a new specialized chip that can become corrupted. I have seen so many issues with the security enclave chip on the Intel Macs, but have seen some things with the Apple Silicon Macs as well (I support thousands of Macs for my organization).

Jan 18, 2024 6:37 PM in response to Henry B.

I was only suggesting the clean reinstall as a last ditch effort (DFU firmware Restore preferred) before paying for a repair. It is possible between resetting the security enclave and reinstalling macOS that it may correct the issue. I have encountered a lot of odd quirkiness with the security enclave chip while supporting my organization's Macs. I think the data stored within them just becomes corrupt so a reinstall is necessary for some things since a DFU firmware "Revive" has not resolved many of the problems. For example, sometimes only one of the users is recognized when authenticating to the security enclave chip, other times no users are listed, but instead mysterious UUID's of the various users requiring a game of trying everyone for the password.


I think I only ever encountered one laptop with a Personalization issue, but I don't recall any details.


With a computer under warranty which may be ending soon, then having it repaired seems like the best option, but I'm always concerned about the refurbished board...I've never liked getting refurbished Logic Boards.

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 Personalise the software update. Please try again

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