Thrum

What is wdavdaemon, and why is it using so much CPU on my Mac?

Last reviewed: 19 November 2026. Behavior and commands taken from Microsoft's documentation; not installed on the Mac used for checking.

wdavdaemon is the background service of Microsoft Defender for Endpoint on macOS, and wdavdaemon_unprivileged is the Microsoft Defender Antivirus process that scans files as apps open and write them. It uses CPU when another program touches many files in a short time, such as a build, an updater or a sync app. It is safe; Microsoft's fix is to find the busiest process with its real-time protection statistics and add an exclusion.

wdavdaemon at a glance

wdavdaemon
Made byMicrosoft (Microsoft Defender for Endpoint)
TypeAntivirus background service
Runs asa system service, not your user
Can you quit it?Not recommended. It provides Microsoft Defender real-time protection, and on a managed Mac tamper protection can block changes to it.

What is wdavdaemon?

Microsoft Defender for Endpoint (installed as Microsoft Defender in the Applications folder) runs several processes whose names start with wdavdaemon. Microsoft's performance guide names wdavdaemon_unprivileged as the Microsoft Defender Antivirus process; this is the one that does real-time protection, the continuous file and process monitoring that scans files when they are opened or changed.

Defender is usually installed and configured by an employer through device management. It is managed with the mdatp command in Terminal, keeps diagnostic logs in /Library/Application Support/Microsoft/Defender/wdavdiag/, and stores quarantined files in /Library/Application Support/Microsoft/Defender/quarantine/.

Is wdavdaemon safe?

Yes. wdavdaemon is Microsoft's own antivirus service. It is updated through Microsoft AutoUpdate. If you did not install Defender and your Mac is not managed by an organization, check Applications for Microsoft Defender and ask whoever set up the Mac.

Why does wdavdaemon use so much CPU and disk?

How much CPU is normal for wdavdaemon?

Short bursts of CPU while you open, download or build things are normal. When the Mac is idle and no files are changing, wdavdaemon processes should be near 0% CPU.

Long stretches of high CPU in wdavdaemon_unprivileged usually line up with another program that is writing or reading many files at the same moment.

How do you find what makes wdavdaemon use so much CPU?

  1. Find the program that triggers scans. Open Activity Monitor and look at what else is busy at the same time. Microsoft names software updaters and compilers as typical causes.
  2. Check real-time protection status. In Terminal, mdatp health --field real_time_protection_enabled shows whether real-time protection is on. Microsoft's statistics only work while it is on.
  3. Collect real-time protection statistics. Run mdatp config real-time-protection-statistics --value enabled, reproduce the slowdown, then mdatp diagnostic real-time-protection-statistics --output json > real_time_protection.json. The output lists each process and how many files it caused Defender to scan.
  4. Add an exclusion. For the process or folder with the most scans, Microsoft's fix is an exclusion, for example mdatp exclusion process add --name <process-name> or mdatp exclusion folder add --path <folder>. mdatp exclusion list shows what is excluded.
  5. Ask your IT team on a managed Mac. If your organization manages Defender, exclusions and real-time protection are set by policy, and tamper protection can block local changes. Send them the statistics file.

When should you worry about wdavdaemon?

Microsoft says that if performance problems continue with real-time protection off, the cause may be the endpoint detection and response part of Defender, and support should be contacted.

Do not turn off real-time protection permanently to save CPU. Exclude the specific busy folder or process instead, ideally with your IT team's agreement.

How do you check wdavdaemon in Activity Monitor and Terminal?

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

In Terminal, the first command lists every wdavdaemon process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'wdavdaemon' | grep -v grep
sudo fs_usage -w -f filesys wdavdaemon

How can Thrum help with wdavdaemon?

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 wdavdaemon 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 wdavdaemon

Why are there several wdavdaemon processes?

Defender splits its work across processes with different privileges. Microsoft's performance guide identifies wdavdaemon_unprivileged as the antivirus scanning process to check when CPU is high.

How do I remove Microsoft Defender from my Mac?

Microsoft says to offboard the device first, then move Microsoft Defender from Applications to the Trash or run its uninstall script. On a managed Mac, ask your IT team, since policy will reinstall it.

Does wdavdaemon slow down Xcode builds?

It can, because each file a build creates is scanned. Microsoft's sample statistics show build tools among the top sources of scans, and an exclusion for the build folder is its suggested fix.

Sources