Failed to personalize software update, M1 Mac

My 2020 m1 MacBook Air recently developed the "Failed to personalize software update" problem when I attempted to update from 13.5.1 to 13.5.2. Simple fixes like reboot, safe mode, and download update via terminal did not work, but the DFU 2-macs method worked fine.


Unfortunately, the problem persists, as I got the personalization failure error again when trying to update, via the basic Systems Settings, to 13.6 and 14.0. I will therefore resort to the DFU method again (and hope it again works!), but was wondering if anyone had a suggestion that might be more efficient than the backup-erase-DFU-restore drill every time there's a security update.


I've owned many, many macs, starting with the 1984 "Fat Mac." They never died, they just aged. The m1 is the sweetest running machine yet. Yet this "Failed to personalize software update" thing seems kludgey, very un-Apple-like, and unsettling. Although my M1 finds nothing to repair with disk utility and passes every test of the Apple Diagnostics, I wonder if something has gone amiss in the ultra-integrated hardware. I hope that Apple monitors this site and will develop an OS update process that will relieve this headache.


MacBook Air 13″, macOS 13.5

Posted on Sep 27, 2023 12:28 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 30, 2023 12:16 AM

And I got this information from the Chinese version of the community (by tonyfromcalgary, and my translation may not be correct):

"I think it's a network issue, such as a router set to block, or a local change of hosts, or simply an unstable network.

Because when installing, the installer will exchange information with Apple's network communication, such as previous activation steps, or check if the device is registered for a certain organization, or update according to the special settings of the device, and so on.

If you can, change the network environment and try a different time period."

9 replies
Question marked as Top-ranking reply

Oct 30, 2023 12:16 AM in response to JoeHallIII

And I got this information from the Chinese version of the community (by tonyfromcalgary, and my translation may not be correct):

"I think it's a network issue, such as a router set to block, or a local change of hosts, or simply an unstable network.

Because when installing, the installer will exchange information with Apple's network communication, such as previous activation steps, or check if the device is registered for a certain organization, or update according to the special settings of the device, and so on.

If you can, change the network environment and try a different time period."

Feb 8, 2024 8:28 AM in response to JoeHallIII

I have had this problem for some time with various OS X updates, and have had to restore et cetera et cetera.

I have just tried a new approach. I disconnected I from my Wi-Fi network and use the personal hotspot on my phone using my EE 4g. The update works with no problems!


Conclusion – it seems to be to do with the Wi-Fi router rather than the Mac.

So use another Internet connection.

Nov 11, 2023 5:20 PM in response to ming78

这个错误在日志里出现很多次:Package Authoring: error running installation-check script: TypeError: null is not an object (evaluating 'cpuFeatures.split') at x-distribution:///installer-gui-script%5B1%5D/installation-check%5B1%5D/@script

下面是处理的代码 有没有可能是这个脚本的问题

function InstallationCheck(prefix) { var boardIds = ['Mac-E43C1C25D4880AD6','Mac-35C5E08120C7EEAF','Mac-66E35819EE2D0D05','Mac-CAD6701F7CEA0921','Mac-A5C67F76ED83108C','Mac-551B86E5744E2388','Mac-F60DEB81FF30ACF6','Mac-9AE82516C7C6B903','Mac-FFE5EF870D7BA81A','Mac-DB15BD556843C820','Mac-B809C3757DA9BB8D','Mac-65CE76090165799A','Mac-9F18E312C5C2BF0B','Mac-937CB26E2E02BB01','Mac-A369DDC4E67F1C45','Mac-EE2EBD4B90B839A8','Mac-473D31EABEB93F9B','Mac-B4831CEBD52A0C4C','Mac-827FB448E656EC26','Mac-4B682C642B45593E','Mac-77F17D7DA9285301','Mac-BE088AF8C5EB4FA2','Mac-7BA5B2D9E42DDD94','Mac-AA95B1DDAB278B95','Mac-63001698E7A34814','Mac-226CB3C6A851A671','Mac-827FAC58A8FDFA22','Mac-06F11FD93F0323C5','Mac-06F11F11946D27C5','Mac-E1008331FDC96864','Mac-27AD2F918AE68F61','Mac-7BA5B2DFE22DDD8C','Mac-CFF7D910A743CAAF','Mac-AF89B6D9451A490B','Mac-53FDB3D8DB8CA971','Mac-5F9802EFE386AA28','Mac-A61BADE1FDAD7B05','Mac-E7203C0F68AA0004','Mac-0CFF9C7C2B63DF8D','Mac-937A206F2EE63C01','Mac-1E7E29AD0135F9BC','Mac-112818653D3AABFC','VMM-x86_64',]; var cpuFeatures = system.sysctl( 'machdep.cpu.features' ); if (cpuFeatures) { cpuFeatures=cpuFeatures.split(" "); for( var i = 0; i < cpuFeatures.length; i++ ){ if( cpuFeatures[i] == "VMM" ){ return true; } } }


脚本


[Edited by Moderator]

Oct 28, 2023 8:00 AM in response to GlenZheng

Hello GlenZheng,

Thank you for that information. I have updated each and every version since 13.5.1 using DFU restore. Before updating to 14.1 yesterday, I phoned Apple Support to get their take. They took me through all the possibilities, starting with safe mode, all failed. The final try was the bootable flash drive method which also resulted in the personalization fail. So I signed off and did the DFU restore on my own. My M1 continues to indicate no problems in disk utility repair and zero issues with the apple hardware diagnostics. I may take my M1 to the Genius Bar for the next 14.x.

Oct 28, 2023 6:26 AM in response to JoeHallIII

Hey JoeHallIII,

I encountered the same error almost at the same time.

I upgraded my 2020 m1 Macbook Pro from Ventura 13.6 to Sonoma 14.1 via DFU last month, but recently I have encountered the same error again when upgrading to Sonoma 14.1.

I would like to know if your problem has been resolved, and if so, how has it been resolved.

Looking forward to your reply. Thank you!

Oct 30, 2023 12:05 AM in response to JoeHallIII

Hello JoeHallIII,

Thank you for your reply!

My solution is the same as yours (and only DFU works😂) . Hopefully this is just a software bug and not a hardware failure.

Since I haven't had a chance to visit the Genius Bar in the near future, if you find a solution to the problem at the Genius Bar afterward, please reply to me here, it would help me a lot!

Thanks again! Hope we won't meet this annoying problem again.

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 personalize software update, M1 Mac

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