MacBook Pro, macOS, "Settings" "Software Update" "Updates Available" "macOS Sonoma 14.1.1"

___D___ wrote:

Please help.

Update to "macOS Sonoma 14.1.1" ( Image A ) does not complete install.

Update exits after ~10%( Image B ), and reads message:

" Failed to personalize the software update. Please try again. "( Image C ).

Have tried various connection settings, Wifi, Hotspot.

Have tried Re-install through Safe-Boot Options.

Ongoing difficulty updating to 14.1.1, has been almost a month.

System:

HW: MacBook Pro17,1, Apple M1,

Boot Volume: Macintosh HD (>100 GB, Free Space)

Current OS: Sonoma, macOS 14.0 (23A344)

Support?: AppleCare? +

Yours is not the first report I have seen with this "personalization" error, with no clear way forward(?)

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

if no insight or resolve—

Call Customer Support (800) MY–APPLE (800–692–7753)

or on line https://getsupport.apple.com/

or call AppleCare Support at 1-800-APLCARE (800-275-2273)

Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

Contact Apple for support and service - Apple Support

1 - Restart in Safe Mode. This will perform a Disk Repair, clear cache files and only load Apple Software, extensions and fonts. The boot up will be slow and can take some time - Normal.

2 - Safe Mode will also eliminate Third Party Software, extensions and drivers from loading. It will only load the Minimum amount of Core Apple Processes to allow the the computer to function at a reduced Level of Performance 

3 - While Still In Safe Mode

Terminal command below

softwareupdate --fetch-full-installer --full-installer-version 14.1.1

Will download the Full Version (12.9 GB ) and place a new application in Applications Folder called ( Install Sonoma )

When ready and Still in Safe Mode - launch the Application and follow the prompts

Cross Fingers and hope and prey it works

Per chance, is this happening on a M3 Apple Computer ?

Sorry for the late reply but never received a Notification of your posting

Thanks for your quick answer, unfortunately it didn't work, same error :s

Logger shows these errors:

MacBook-Pro osinstallersetupd[3236]: 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

And it finish with these errors:

MacBook-Pro osinstallersetupd[3236]: Prepare returned an SUMacControllerErrorDomain error: Error Domain=SUMacControllerError Code=7723 "[SUMacControllerErrorPreflightPersonalizeFailed=7723] Failed to perform PreflightPersonalize operation: [MobileSoftwareUpdateErrorDomain(MSU):1256]" UserInfo={NSLocalizedDescription=Failed to personalize the software update. Please try again., SUMacControllerErrorIndicationsMask=0, NSDebugDescription=[SUMacControllerErrorPreflightPersonalizeFailed=7723] Failed to perform PreflightPersonalize operation: [MobileSoftwareUpdateErrorDomain(MSU):1256], NSUnderlyingError=0x600002bc6f70 {Error Domain=MobileSoftwareUpdateErrorDomain Code=1256 "Failed to find SFR recovery volume" UserInfo={NSDebugDescription=Failed to find SFR recovery volume}}}

MacBook-Pro osinstallersetupd[3236]: Operation queue failed with error: Error Domain=com.apple.OSInstallerSetup.error Code=1007 "An error occurred preparing the update." UserInfo={NSLocalizedRecoverySuggestion=Failed to personalize the software update. Please try again., NSLocalizedDescription=An error occurred preparing the update., NSUnderlyingError=0x600002bc5a70 {Error Domain=SUMacControllerError Code=7723 "[SUMacControllerErrorPreflightPersonalizeFailed=7723] Failed to perform PreflightPersonalize operation: [MobileSoftwareUpdateErrorDomain(MSU):1256]" UserInfo={NSLocalizedDescription=Failed to personalize the software update. Please try again., SUMacControllerErrorIndicationsMask=0, NSDebugDescription=[SUMacControllerErrorPreflightPersonalizeFailed=7723] Failed to perform PreflightPersonalize operation: [MobileSoftwareUpdateErrorDomain(MSU):1256], NSUnderlyingError=0x600002bc6f70 {Error Domain=MobileSoftwareUpdateErrorDomain Code=1256 "Failed to find SFR recovery volume" UserInfo={NSDebugDescription=Failed to find SFR recovery volume}}}}}

MacBook-Pro InstallAssistant[3231]: Stopped operation queue with Error Domain=com.apple.OSInstallerSetup.error Code=1007 "An error occurred preparing the update." UserInfo={NSUnderlyingError=0x6000007f79c0 {Error Domain=SUMacControllerError Code=7723 "[SUMacControllerErrorPreflightPersonalizeFailed=7723] Failed to perform PreflightPersonalize operation: [MobileSoftwareUpdateErrorDomain(MSU):1256]" UserInfo={NSUnderlyingError=0x6000007f7a80 {Error Domain=MobileSoftwareUpdateErrorDomain Code=1256 "Failed to find SFR recovery volume" UserInfo={NSDebugDescription=Failed to find SFR recovery volume}}, SUMacControllerErrorIndicationsMask=0, NSDebugDescription=[SUMacControllerErrorPreflightPersonalizeFailed=7723] Failed to perform PreflightPersonalize operation: [MobileSoftwareUpdateErrorDomain(MSU):1256], NSLocalizedDescription=Failed to personalize the software update. Please try again.}}, NSLocalizedRecoverySuggestion=Failed to personalize the software update. Please try again., NSLocalizedDescription=An error occurred preparing the update.}

Sorry but I think it now time to review the suggestions from @leroydouglas and get on the Telephone with Apple.

I can only say that on 3 different M2 / M1 Machines I own, upgraded from Ventura 13.6.1 and 1 from Ventura 13.4.

All Machines upgraded fine to 14.0 to 14.1 and to 14.1.1

An Aside - still not getting Notification from Apple about your posting

i'm facing the same exact issue when i try to update to Sonoma 14.1.1

any update or fix?

A "Fix". I have had this problem for the last 4 updates of my M1 MacBook air. A time-consuming work-around for me involves 1) doing a complete backup of my problematic mac 2) connecting the mac via its usb charging cable to a second mac and using Apple Configurator 2 and DFU mode. The key is to do a Restore which will erase your problematic Mac. When the restore is complete, your mac should have the latest system (that is, the updated system that you are trying to get in the first place). Then you set up your now restored mac with the time machine or CCC backup from step 1). This has worked for me every time so far, though it is obviously time consuming.

This is explained in detail in an old Youtube post from "Mr Macintosh". https://www.youtube.com/watch?v=i5xmA3lDz3g

I am still hoping that apple eventually fixes this properly.

Hope the work-around works for you.

Joe H.

[Edited by Moderator]

I have had this problem for some time with several OS X updates.

I have just tried something new and it worked.

I disconnected from my Wi-Fi connection. I connected the Mac via personal hotspot to my iPhone on EE. The update performed with no problems at all..

Conclusion – it's something to do with the router or Internet connection rather than the Mac

I'm using an M1, MacBook 13

This "solution" to the problem as posted by "Ben Gow" will sometimes work... if the problem is caused by the MacOS update software being unable to establish a stable secure connection to Apple's servers that provide access to the MacOS update. It is worth a try, but this is the cause of the problem in the minority of cases hence it this solution will not work for most people.

Unfortunately the cause of this problem in most cases is because something deep within the Mac's firmware has become corrupted, causing the MacOS updater to be unable to verify registration of the Mac with the MacOS update servers. In this case the laborious solution posted above by JoeHall may work - and it is the solution that some of the more knowledgeable Apple support techs will propose.

Further unfortunately there are cases where the method described above by JoeHall also does not work. In this case, the Apple techs will tell you the only (and expensive) solution is a replacement of the Mac logic board. I know from experience, because sadly this was what I ended up having to do. I suppose because of the extreme security now built into the Mac firmware, there are settings that are simply inaccessible to any software tools available even to Apple's techs that can be used to salvage a logic board affected by this issue.

Unfortunately did not work with me on my M1 pro 13 2020