TerryE
A process named Mobileassetupdaterd owned by the user _accessoryupc, hogs 35% of CPU.
It's associated with a file named MobileAssetUpdater at:
/System/Library/PrivateFrameworks/MobileAssetUpdater.framework/MobileAssetUpdater
Which is a 35 byte alias pointing to the executable at:
/System/Library/PrivateFrameworks/MobileAccessoryUpdater.framework/Support/accessoryupdaterd
Which is consistently relaunches using this Plist:
/System/Library/LaunchDaemons/com.apple.accessoryupdaterd.plist
I tried unloading the process with this command others have suggested:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.accessoryupdaterd.plist
But I just get the error: Unload failed: 5: Input/output error
So I'm just not a Terminal master.
I've also tried exhaustive searches at Apple, here at StackOverflow, and online to find a solution, with no luck.
I watch processes periodically, and it wasn't there until I Updated OS from Ventura to Sonoma 14.5.
Anyone have thoughts?
Running macOS Sonoma 14.5 on 2021 M1 MacBook Pro.
Thanks!
About
- Username
- TerryE
- Joined
- Visits
- 1
- Last Active
- Roles
- member
- Badges
- 0
- Posts
- 5
Reactions
Comments
-
Thank you so much for your kind and continued support. Been on the phone with Apple just to get advice on moving/copying user info. They were not much help. The best support I've had is right here from your kind replies. But I have successfully re…
-
Thank you SO much for the kind replies and suggestions! launchctl list | grep -v "apple" PID Status Label 764 0 application.com.rockysandstudio.Battery-Diag.141576981.141577051 - 0 com.rockysandstudio.Battery-Diag.LaunchHelper…
-
Marvin said: TerryE said: while it persists in Safe Mode, it did NOT occur when I set up a new user account on my machine to test it. So the trigger to launch the bugger is likely somewhere in my user data That's interesting, it's g…
-
Thanks for the kind reply. I've tried everything. Can't unload it with terminal because of system integrity protection. Apple help just want's me to reinstall OS but warned that the Time Machine backup might still contain the problem. That's because…