How to Fix ‘Coreauthd High CPU Usage’ on Mac

Opening Activity Monitor on your Mac only to discover the background system process coreauthd consuming 100% to 300% CPU on multiple cores drains battery life and degrades system responsiveness. In the macOS architecture, coreauthd (Core Authentication Daemon) is the primary user-space daemon responsible for coordinating biometric authentication, Touch ID, Apple Watch unlock handshakes, and cryptographic LocalAuthentication framework requests. When an application continuously polls for biometric approval, Touch ID fingerprint templates become corrupted in the Secure Enclave, or Bluetooth proximity handshakes with your Apple Watch get stuck in an infinite loop, coreauthd fails to sleep and exhausts CPU cycles. Follow this guide to resolve coreauthd runaway CPU usage on Intel and Apple Silicon Macs.

What Causes coreauthd to Consume Excessive CPU?

The Core Authentication Daemon is designed to remain idle until an application explicitly requests biometric authorization. Common triggers for high CPU usage include:

  • Apple Watch Auto-Unlock Bluetooth Desynchronisation: When “Use your Apple Watch to unlock apps and your Mac” is enabled, connection timeouts can leave coreauthd running persistent Bluetooth proximity scans.
  • Corrupted Touch ID Biometric Templates: Stale fingerprint templates stored in the Secure Enclave triggering recurring validation errors.
  • Third-Party Password Managers or Sudo Touch ID Tweaks: Command-line PAM modules (such as pam_tid.so) or browser extensions requesting biometric tokens in rapid succession.
  • Corrupted System Preferences Domain: Damaged property list files in ~/Library/Preferences/ByHost/ preventing authentication state caching.

Method 1: Force Quit coreauthd in Activity Monitor

Terminating the hung daemon allows launchd to restart it immediately in a clean state without rebooting your Mac.

  1. Press Command + Space, type Activity Monitor, and press Return.
  2. In the search box in the top-right corner, type coreauthd.
  3. Click on the coreauthd process to highlight it.
  4. Click the Stop (X) button in the top toolbar.
  5. Select Force Quit.
  6. macOS will automatically reload coreauthd with fresh memory structures. Observe whether its CPU usage settles back below 1%.

Method 2: Toggle Apple Watch Unlock Settings

Desynchronised Apple Watch proximity handshakes are the leading trigger for recurring coreauthd loops.

  1. Open System Settings from the Apple menu.
  2. Navigate to Touch ID & Password (or Login Password).
  3. Locate the Apple Watch section.
  4. Toggle the switch for your Apple Watch Off.
  5. Restart your Mac.
  6. After rebooting, return to System Settings and toggle Apple Watch unlock back On, authenticating with your Mac password.

Method 3: Reset Touch ID Fingerprints

Corrupted fingerprint data in the Secure Enclave causes the local authentication daemon to retry matching operations indefinitely.

  1. In System Settings, select Touch ID & Password.
  2. Hover your mouse over each enrolled fingerprint and click the Delete (X) badge that appears.
  3. Confirm deletion by entering your administrator password.
  4. Once all fingerprints are removed, shut down your Mac completely.
  5. Wait 30 seconds, power on your Mac, return to Touch ID settings, and click Add Fingerprint to enroll your fingers cleanly.

Method 4: Revert Custom PAM Touch ID Terminal Configurations

If you modified PAM configurations to enable Touch ID for sudo commands in Terminal, malformed syntax locks the daemon.

  1. Open Terminal.
  2. Inspect your PAM sudo configuration:
    cat /etc/pam.d/sudo
  3. If the line auth sufficient pam_tid.so is present at the top, verify that it was entered correctly without trailing whitespace. If persistent CPU issues occur, remove or comment out that line and restart Terminal.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.