Fix com.apple.launchd.peruser Error Crash Loop on macOS

Symptoms

Users experiencing the com.apple.launchd.peruser error crash loop may notice the following symptoms:

• Repeated entries in system logs (Console app) showing com.apple.launchd.peruser errors.
• High CPU usage by launchd processes, leading to reduced system performance and battery drain on laptops.
• Applications crashing or failing to launch properly due to launchd instability.
• System sluggishness, especially after login or when switching users.
• Persistent error messages even after restarting the Mac.

Root Causes

The com.apple.launchd.peruser error crash loop typically stems from one or more of the following:

• Corrupted user-specific launch agents: Plist files in ~/Library/LaunchAgents/ that are malformed or incompatible with the current macOS version.
• Third-party software conflicts: Applications that install their own launch agents (e.g., Adobe, Google, or security tools) may cause launchd to crash repeatedly.
• Incorrect permissions: System or user launch daemons/agents with wrong file permissions can trigger launchd errors.
• macOS update issues: Incomplete or failed system updates can leave launchd configurations in an inconsistent state.
• User account corruption: Damaged user preferences or cache files may cause launchd to fail when loading per-user services.

Step-by-Step Fix

Step 1: Identify the Problematic Launch Agent

1. Open Console app from /Applications/Utilities/.
2. In the search bar, type com.apple.launchd.peruser.
3. Look for error entries that mention a specific plist file path, such as ~/Library/LaunchAgents/com.example.agent.plist.
4. Note the exact plist filename causing the crash.

Step 2: Temporarily Disable the Suspect Agent

1. Open Terminal from /Applications/Utilities/.
2. Run the following command to unload the agent (replace com.example.agent with the actual label):
   

   launchctl unload ~/Library/LaunchAgents/com.example.agent.plist

3. If the error stops, the agent is the culprit.

Step 3: Remove or Repair the Agent

1. Backup the plist file:
   

   cp ~/Library/LaunchAgents/com.example.agent.plist ~/Desktop/

2. Delete the agent:
   

   rm ~/Library/LaunchAgents/com.example.agent.plist

3. Restart your Mac to clear any cached errors.

Step 4: Check Permissions

1. In Terminal, run:
   

   sudo chown root:wheel /System/Library/LaunchDaemons/*.plist
   sudo chmod 644 /System/Library/LaunchDaemons/*.plist

2. For user agents:
   

   chmod 644 ~/Library/LaunchAgents/*.plist
   chown $USER:staff ~/Library/LaunchAgents/*.plist

Step 5: Reset Launch Services Database (if needed)

1. Run:
   

   /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user

2. Restart your Mac.

Alternative Fixes

• Use Safe Mode: Boot into Safe Mode (hold Shift during startup) to isolate third-party launch agents. If the error stops, a third-party agent is likely the cause.
• Create a New User Account: If the error persists only for your user, create a new admin account via System Preferences > Users & Groups. Migrate your data to the new account.
• Reinstall macOS: As a last resort, reinstall macOS from Recovery Mode (Command+R at startup) to repair system files without erasing data.

Prevention

• Keep macOS updated: Install the latest system updates to avoid known launchd bugs.
• Vet third-party software: Only install trusted applications that properly manage their launch agents.
• Regularly clean launch agents: Periodically review ~/Library/LaunchAgents/ and remove unused or outdated plist files.
• Use maintenance tools: Run tools like OnyX or CleanMyMac to repair permissions and clear caches.
• Backup before major updates: Always create a Time Machine backup before installing macOS updates.