2020 MacBook Air here (M1 chip). I had the error. Tried logging out of iCloud and installing from Settings -> General. Didn't work. Logged back into iCloud, tried again and then it did. YMMV!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
"failed to personalize the software update" when updating to macOS Sequoia
- Thread starter 212rikanmofo
- Start date
- Sort by reaction score
Tried all of the methods above (apart from DFU) and nothing works. Will have to wait it out for Apple to make the fix…..
Honestly with all the bugs encountered and all the threads on reddit that I can read about multiples deficiency and bugs about 15.0, I'll just wait a week or two before doing the update...
I have my iMac M3 and wife MBA M2 set on auto update and install. I won't touch it and just let it do its thing. I'm in no rush to jump to this OS. Which seems like a big mess. This yearly update cycle is getting out of hand with quality and testing.
M1 Mac studio, logged out didnt allow the update, but once logged in I could do the update, Thank u
💪😎😋 yea ! I got it to work ! After loading from App Store I try whit and whiteout vpn logging out of Apple no help still the error message! Then I made a restart ,have only my IMac 24‘
Then a new window enter your password to a user you now !!! Never seen this!!!
Ok enter admin pw after a moment he tell your Mac is activate!!
And boot into desktop and BINGO the update run !! Now I am even on 15.1 no problem to install!!! 😎😎😎 certainly AI is not active here in Europe! Thankfully
Then a new window enter your password to a user you now !!! Never seen this!!!
Ok enter admin pw after a moment he tell your Mac is activate!!
And boot into desktop and BINGO the update run !! Now I am even on 15.1 no problem to install!!! 😎😎😎 certainly AI is not active here in Europe! Thankfully
I have a new MacBook Pro M3 and I logged out of my iCloud and this seems to be working its in the process now. Glad someone figured this out.
DFU revive seems to have done the trick for now. Update is preparing, which is furthest I have got so far. Fingers crossed….
Disabling Find My, Losing out of iCloud, DFU method. No excuse for Apple. This is an amateur junk from Apple. Since an enthusiast since 84 when I first got my 512K Fat Mac, I cannot excuse the mess Apple has done with this update in 2024! What a mess Apple.
I mean you would think we should not have to go through all this for an update, it seems the logging out of the find me or iCloud definitely is the trick. But we should never have to figure things out like this to do an update!
It worked! Like, what the heck? Congrats to Apple software engineers, what a mess.
am I missing out smth I tried everything mentioned above but still the same problem persists can anyone pls guide me huh
SOLUTION (at least for me). Turn off Find My on your Mac, install, and then re-enable.
Head to Settings, search "Find My" and disable it. Once disabled, head to Software Update and begin the update process. It'll complete successfully.
still....ahh
Attachments
I'm not counting on there being a macOS 15.0.1 update.
Wouldn't surprise me if the next update ends up being 15.1, last year there was no 14.0.1, the next update after 14.0 was 14.1.
I see there was a 13.0.1 update so maybe ill be wrong. Who knows at this point.
There been mixed results of a fix coming this week some people that talked with apple support said yes and others said no.
Wouldn't surprise me if the next update ends up being 15.1, last year there was no 14.0.1, the next update after 14.0 was 14.1.
I see there was a 13.0.1 update so maybe ill be wrong. Who knows at this point.
There been mixed results of a fix coming this week some people that talked with apple support said yes and others said no.
Last edited:
Bearing in mind that this workaround is not effective for 100% of cases, make sure you do a full restart after you've signed back into iCloud and manually disabled Find My. After a restart, if another install attempt fails, you won't benefit from this workaround, so you'll have to wait on Apple's hotfix due by end-of-week.