|

Antimalware Service Executable High CPU Usage Fix (2026)

Antimalware Service Executable is the Task Manager name for the Microsoft Defender Antivirus engine, MsMpEng.exe.

It uses the most CPU when it scans files, so a spike during a scan is expected, but constant high usage is not.

Start with the quick answer below, then work down the list until the CPU drops.

Quick answer: what to try first

Likely causeFixWhere
A scan is runningLet it finish, or move the scan timeWindows Security, PowerShell
Another antivirus is installedCheck that product for known issues, then add exclusions both waysOther antivirus vendor, Windows Security
One file, folder or app triggers itAdd an exclusionWindows Security > Virus & threat protection
Scans take too much CPULower the scan CPU limitPowerShell Set-MpPreference
Large files in synced foldersMove big .iso, .vhd or .vhdx files to a local folderFile Explorer

What Antimalware Service Executable is

Microsoft’s own performance guide lists it as MsMpEng.exe, the process behind Microsoft Defender Antivirus on Windows.

It scans files, so it works hardest when you open, copy or download many files.

You should not end the task, because that leaves the PC without antivirus scanning.

Why Defender uses so much CPU

Microsoft’s scan guidance explains that real-time protection scans files before you access or run them.

TriggerWhat Microsoft says
Archives and containers such as ISO filesSlow to scan because they cannot be scanned in parallel and need extraction
Complex file typesContent complexity affects scan time more than file size does
File hash computationRuns for every executable scanned when no hash exists yet, which costs more when copying large files from network shares
Full scansTake several hours to several days depending on content and resources

The same page says most people never need to run a full scan.

Check for another security program

Microsoft tells admins to rule out other security software before changing any Defender setting.

Two antivirus, backup or endpoint tools scanning the same files can conflict and drive CPU up.

If you run one, add its program folder to the Defender exclusions and add Defender’s files to that product’s exclusions.

Let a running scan finish

Open Windows Security and select Virus & threat protection to see whether a scan is running.

Defender also scans after it downloads a security intelligence update, so a scan can start at an odd time.

If the PC is idle, the scan should finish and the CPU should settle.

Our guide to scanning Windows 11 with Windows Security covers quick, full and offline scans.

Lower the scan CPU limit

Microsoft’s default for the maximum average CPU during a scan is 50 percent.

You can lower it to 20 or 30, but scans then take longer.

  1. Right-click Start and open PowerShell as administrator.
  2. Run Set-MpPreference -ScanAvgCPULoadFactor 30.
  3. Run Set-MpPreference -EnableLowCpuPriority $true to give scans low CPU priority.

Microsoft calls the CPU limit guidance for the scan engine, not a hard limit.

Why the limit may seem ignored

SettingDefaultWhat it does
ScanAvgCPULoadFactor5 to 100, default 50Ignored if both idle settings below are true
ScanOnlyIfIdleEnabledTrue by defaultScheduled scans run when the PC is on but not in use
DisableCpuThrottleOnIdleScansTrue by defaultNo throttling while the PC is idle, meaning under 90 percent CPU
EnableLowCpuPriorityTrue by defaultLow CPU priority for scheduled scans

Setting the CPU factor to 0 or 100 turns throttling off, which Microsoft does not recommend because apps can stop responding and the PC can overheat.

Move the scan to a time you are away

Microsoft lists a default quick scan time of 02:00 with a 120 minute offset.

Start times are randomized by up to 30 minutes unless you turn that off.

This command from Microsoft’s scheduling page runs a daily quick scan at 12:30 PM and disables the idle check.

Set-MpPreference -ScanScheduleQuickScanTime 12:30:00 -ScanScheduleOffset 0 -RandomizeScheduleTaskTimes $false -ScanOnlyIfIdleEnabled $false

Pick your own time with the same pattern, and keep the idle check on if the PC sleeps overnight.

Add an exclusion for the file, folder or app that triggers it

  1. Open Windows Security and select Virus & threat protection.
  2. Under Virus & threat protection settings, select Manage settings.
  3. Select Add or remove exclusions, then choose File, Folder, File type or Process.

For a process, Microsoft advises using its full path and file name.

Excluded items are not checked for threats, and exclusions apply only to real-time scanning, so scheduled scans may still check them.

Never exclude locations malware likes, such as Temp folders, because Microsoft warns against it.

Test with real-time protection off

Microsoft’s test for isolating the cause is to turn real-time protection off and watch the CPU.

  1. In Windows Security, open Virus & threat protection settings and Manage settings.
  2. Turn Real-time protection off, after turning off Tamper Protection if it is on.
  3. Check whether CPU use drops, then turn protection back on.

Windows turns it back on by itself after a short while, and files you open while it is off are not scanned.

Move large files out of synced folders

Microsoft names large .iso, .vhd and .vhdx files in redirected Desktop, Downloads or Documents folders as a cause of high CPU.

Move them to a local folder that is not on a network share or an Offline Files or OneDrive location.

You can also trim background load with our Task Manager guide and startup apps guide.

Find what is triggering the scans

ToolWhen Microsoft suggests it
Performance analyzer for Microsoft Defender AntivirusFirst choice, reproduce the problem while it records
Process MonitorIf the analyzer shows nothing, record for 5 to 10 minutes
Windows Performance RecorderAdvanced, limit to 3 to 5 minutes because it is verbose

Official sources

This guide follows Microsoft’s Defender performance troubleshooting, scheduled scan PowerShell settings, scan best practices and Windows Security exclusions pages.

Leave a Reply

Your email address will not be published. Required fields are marked *