Thrum

What is kernelmanagerd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

kernelmanagerd is the macOS kernel extension server: it loads kernel extensions (kexts) from the loaded kext collections, builds new kexts into the auxiliary kext collection for the next restart, and launches driver extensions. It gets busy when software that includes a kext or driver is installed or updated, and after macOS updates. Otherwise it is idle.

kernelmanagerd at a glance

kernelmanagerd
Made byApple (part of macOS)
TypeSystem daemon
Location/usr/libexec/kernelmanagerd
Runs asroot
Started bylaunchd job com.apple.kernelmanagerd
Can you quit it?No. It handles kernel extension and driver requests for the whole system.

What is kernelmanagerd?

The kernelmanagerd(8) man page describes it as the kernel extension server. It runs as a launchd daemon and handles requests from the kernel and from other processes to load kernel extensions if they are available in a loaded kext collection. If a requested kext is not yet available, kernelmanagerd builds it into the auxiliary kext collection for use on the next reboot. It also launches driver extensions, and watches /Library/Extensions for kexts that installers add or remove.

Apple's Platform Security guide explains the background: kexts are no longer recommended for macOS, are merged into an Auxiliary Kernel Collection that loads at boot, and need the user's approval and a restart. Most modern drivers and security tools are system extensions or DriverKit drivers that run outside the kernel.

Is kernelmanagerd safe?

Yes. kernelmanagerd is part of macOS at /usr/libexec/kernelmanagerd, runs as root and is started at boot by launchd. Third-party kexts it loads are subject to your approval in System Settings > Privacy & Security.

Why does kernelmanagerd use so much CPU?

How much CPU is normal for kernelmanagerd?

Typical: near 0% CPU after startup. A burst during an installer that includes a kext or driver, or after a macOS update, is normal.

Repeated activity without installs can point to a driver or installer that keeps retrying.

How do you check what kernelmanagerd is loading?

  1. List non-Apple kernel extensions. In Terminal, kmutil showloaded --list-only --variant-suffix release | grep -v com.apple lists loaded kexts not made by Apple. kmutil showloaded alone lists all of them.
  2. List system extensions. systemextensionsctl list shows installed system extensions and DriverKit drivers with their state.
  3. Remove kexts you no longer need. Uninstall old drivers and security tools with their own uninstallers. Many vendors now ship system extensions instead of kexts.
  4. Restart after approving a kext. Apple's guide says rebuilding the auxiliary collection requires your approval and a restart. Until you restart, the kext is not loaded.

When should you worry about kernelmanagerd?

Worry if kernelmanagerd is busy over and over while nothing is being installed, or if an installer keeps asking you to restart for the same kext. The vendor's software is the cause.

A kernelmanagerd outside /usr/libexec would not be Apple's.

How do you check kernelmanagerd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type kernelmanagerd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every kernelmanagerd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'kernelmanagerd' | grep -v grep

How can Thrum help with kernelmanagerd?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when kernelmanagerd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about kernelmanagerd

Why does installing a driver need a restart?

Kexts are merged into the auxiliary kernel collection, which loads at boot. kernelmanagerd builds the collection, and the restart loads it.

Do Apple silicon Macs need reduced security for kexts?

Apple's Platform Security guide says that rebuilding the auxiliary kernel collection requires secure boot to be set to Reduced Security on those Macs.

Sources