"failed to personalize" error when attempting to update macOS Ventura

Hello:


I'm having a bizarre instance of the "failed to personalize" error when attempting to update macOS Ventura. Unlike all other cases I've seen, changing the source of the update, turning off VPNs, and changing network environment is not resolving the issue.


I have a firewall device as my router, which logs network flows relative to each device on the network. Accordingly, I checked the network flows for my MacBook Pro right as I was attempting to update my device. The network flows are to unregistered URLs made up of randomized characters and not the swscan subdomain that it should be going to.


See:



Additionally, I'm getting really strange WiFi.log content, unlike anything I've seen before.


See:


May 14 00:30:03 brains-mbp newsyslog[29906]: logfile turned over
Sun May 14 02:20:08.520 Usb Host Notification activated
Sun May 14 02:20:08.523 <airport[385]> _initInterface: Unable to initialize unified logger
Sun May 14 02:20:08.523 <airport[385]> _initInterface: Unable to initialize unified temp logger
Sun May 14 02:20:08.523 <airport[385]> _initInterface: Unable to initialize logger
Sun May 14 02:20:08.523 <airport[385]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 02:20:08.523 <airport[385]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 02:25:42.738 Usb Host Notification activated
Sun May 14 02:25:42.797 <airport[375]> _initInterface: Unable to initialize unified logger
Sun May 14 02:25:42.797 <airport[375]> _initInterface: Unable to initialize unified temp logger
Sun May 14 02:25:42.797 <airport[375]> _initInterface: Unable to initialize logger
Sun May 14 02:25:42.797 <airport[375]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 02:25:42.797 <airport[375]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 04:04:42.784 Usb Host Notification activated
Sun May 14 04:04:42.806 <airport[415]> _initInterface: Unable to initialize unified logger
Sun May 14 04:04:42.808 <airport[415]> _initInterface: Unable to initialize unified temp logger
Sun May 14 04:04:42.808 <airport[415]> _initInterface: Unable to initialize logger
Sun May 14 04:04:42.808 <airport[415]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 04:04:42.808 <airport[415]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 04:10:46.064 Usb Host Notification activated
Sun May 14 04:10:46.072 <airport[380]> _initInterface: Unable to initialize unified logger
Sun May 14 04:10:46.074 <airport[380]> _initInterface: Unable to initialize unified temp logger
Sun May 14 04:10:46.074 <airport[380]> _initInterface: Unable to initialize logger
Sun May 14 04:10:46.074 <airport[380]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 04:10:46.074 <airport[380]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 04:15:04.621 Usb Host Notification activated
Sun May 14 04:15:04.624 <airport[384]> _initInterface: Unable to initialize unified logger
Sun May 14 04:15:04.624 <airport[384]> _initInterface: Unable to initialize unified temp logger
Sun May 14 04:15:04.624 <airport[384]> _initInterface: Unable to initialize logger
Sun May 14 04:15:04.624 <airport[384]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 04:15:04.624 <airport[384]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 04:26:14.851 Usb Host Notification activated
Sun May 14 04:26:14.864 <airport[422]> _initInterface: Unable to initialize unified logger
Sun May 14 04:26:14.867 <airport[422]> _initInterface: Unable to initialize unified temp logger
Sun May 14 04:26:14.867 <airport[422]> _initInterface: Unable to initialize logger
Sun May 14 04:26:14.867 <airport[422]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 04:26:14.867 <airport[422]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 05:11:59.110 Usb Host Notification activated
Sun May 14 05:11:59.125 <airport[387]> _initInterface: Unable to initialize unified logger
Sun May 14 05:11:59.126 <airport[387]> _initInterface: Unable to initialize unified temp logger
Sun May 14 05:11:59.126 <airport[387]> _initInterface: Unable to initialize logger
Sun May 14 05:11:59.127 <airport[387]> _initInterface: Unable to initialize driver message tracer monitor
Sun May 14 05:11:59.127 <airport[387]> _initInterface: Unable to initialize unified temporary logger
Sun May 14 05:55:41.540 Usb Host Notification activated
Sun May 14 05:55:41.549 <airport[384]> _initInterface: Unable to initialize unified logger


What is causing this?


I'm running macOS 13.4 (I think?) on a M1 MacBook Pro.


Thanks.


[Re-Titled by Moderator]

MacBook Pro 13″, macOS 13.4

Posted on May 14, 2023 1:46 PM

Reply

Similar questions

3 replies

Mar 9, 2024 3:39 PM in response to SaturnsLament

The macOS logs are almost always worthless for troubleshooting these days and are only meant to be used by the developers of those apps & utilities.


Unfortunately information about Personalization is sketchy, but it appears to be mainly associated with Apple Silicon M-series Macs where Ownership is a new concept & most likely related to these Personalization errors.


You can see my post here trying to help another user:

Failed To Personalise the software update… - Apple Community


And the OP's ultimate solution to the problem including things they tried to do before the final solution:

Failed To Personalise the software update…OP's Final Solution - Apple Community


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" error when attempting to update macOS Ventura

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