MsMpEng.exe High CPU Fix

Brendan Smith
Brendan Smith - Cybersecurity Analyst
7 Min Read
CPU spike poster for MsMpEng.exe Antimalware Service Executable high CPU troubleshooting on blog.gridinsoft.com.
MsMpEng.exe CPU spike troubleshooting poster.

Antimalware Service Executable (MsMpEng.exe) is the scanning engine used by Microsoft Defender Antivirus. If CPU usage jumps during a scan, let it finish and see whether the PC responds normally again. If the slowdown returns every time you open the same app or build a project, note what was running. Changing the scan schedule won’t stop Defender from checking files as you open or change them.

What to check in Task Manager

  • CPU jumps after startup or an update: Open Windows Security → Virus & threat protection and check whether a scan is running. Compare CPU again when it finishes.
  • CPU jumps only during one task: Note the app and time. If the same download, build or sync triggers the spike again, use the Defender recording below to identify what is being scanned.
  • Memory looks high, but CPU is quiet: Check available RAM and whether other apps actually slow down. A single reading for MsMpEng.exe is not enough to diagnose a leak.
  • Disk stays near 100% and the PC freezes: Pause a large download or installer and check which process is busiest in the Disk column. If the freeze returns outside a scan, check storage health as well.
  • The executable is in an unexpected location: Check its path and Microsoft signature before treating it as Defender. Don’t exclude or launch an unfamiliar copy.

MsMpEng.exe high memory: compare two readings

Press Ctrl + Shift + Esc. Under Processes, note the memory used by Antimalware Service Executable and which apps use more. Under Performance → Memory, note Available: that is RAM Windows can give to applications. Take the same readings after the scan or file-heavy task ends.

If the process holds roughly steady, available memory recovers and apps respond normally, leave Defender running. If available memory keeps falling and apps stall, sort Processes by Memory again. Record which process is growing, the time and what was open. If the pattern repeats with MsMpEng.exe after updates and a restart, give those readings to support or your IT team. A Defender scan recording can explain slow file scans; it cannot by itself establish a memory leak.

What Is Antimalware Service Executable?

Antimalware Service Executable is the Task Manager name for Microsoft Defender Antivirus activity. The underlying process is usually MsMpEng.exe. It scans files, scripts, downloads, archives, and app activity so Windows can detect malware before it runs.

Antimalware Service Executable using high CPU in Task Manager

Short CPU spikes are normal during a quick scan, a security intelligence update, or when you open many new files. The problem starts when the spike lasts long enough to make the PC hot, noisy, frozen, or unusable. That usually means Defender is scanning a heavy workload, a scheduled scan is running at the wrong time, another security tool is conflicting with it, or Windows security components need repair.

Confirm MsMpEng.exe Is Legitimate

Before changing Defender settings, confirm that the process is actually Microsoft Defender and not a lookalike. Open Task Manager, right-click Antimalware Service Executable, and choose Open file location. On modern Windows, the file commonly appears under a Microsoft Defender platform folder such as C:\ProgramData\Microsoft\Windows Defender\Platform\..., or in the Windows Defender program folder.

Open MsMpEng.exe file location from Task Manager

MsMpEng.exe in a Microsoft Defender folder

In File Explorer, right-click the file and open Properties → Digital Signatures. Select the Microsoft signature and choose Details to see whether Windows validates it. If access is denied or the tab is missing, do not change permissions or assume infection. Use Windows Security or ask your administrator to verify the file.

Be suspicious if the file is in Downloads, Temp, a random user profile folder, or a folder with a misspelled Microsoft name. A fake process may use a similar name to hide. In that case, do not add exclusions. Scan the system and check startup entries, scheduled tasks, browser extensions, and recently installed software.

Move Defender Scans Away From Work Hours

If the spike happens at predictable times, compare those times with the scheduled scan. If the times match, move the scan to a time when the computer is on but not being used heavily.

  1. Open Start, type Task Scheduler, and open it.
  2. Go to Task Scheduler Library > Microsoft > Windows > Windows Defender.
  3. Open Windows Defender Scheduled Scan.
  4. Use the Triggers tab to choose a time outside your work, gaming, or meeting hours.
  5. Use the Conditions tab to prefer idle or power-friendly conditions when that fits your device.

Task Scheduler for Windows Defender scans

Windows Defender scheduled scan properties

Change Windows Defender scheduled scan trigger

Find the Folder or App That Defender Keeps Scanning

Many persistent MsMpEng.exe spikes come from one noisy workload: a game launcher unpacking files, a developer build directory, a folder with thousands of small files, a virtual machine disk, a large archive, or a sync client constantly changing files. On Windows 10 and Windows 11, Microsoft provides Defender Performance Analyzer for deeper troubleshooting. It records Defender scan activity and reports the files, paths, extensions, and processes that cost the most scan time.

For advanced users, open PowerShell as administrator and record the slow moment:

New-MpPerformanceRecording -RecordTo "$env:TEMP\defender-scan.etl"

Repeat the task that causes the slowdown. Return to PowerShell and press Enter to stop and save the recording; Ctrl+C cancels it. Then review the report:

Get-MpPerformanceReport -Path "$env:TEMP\defender-scan.etl" -TopPaths 10 -TopFiles 10 -TopProcesses 10

Look for the path or process that accounts for the most scan time during that task. For example, if a sync client is writing many files, pause the sync and repeat the same work. If responsiveness returns, try scheduling the sync outside work hours. A top entry shows where Defender spent time, not whether a file is safe to exclude.

Use Exclusions Carefully

Exclusions can reduce Defender’s workload, but they also create blind spots. Do not exclude your whole system drive, Downloads, Temp, script extensions, unknown executables, or a suspicious copy of MsMpEng.exe. Exclude only a specific folder or file path you already trust and understand.

To add a narrow exclusion:

  1. Open Windows Security.
  2. Go to Virus & threat protection > Manage settings.
  3. Scroll to Exclusions and choose Add or remove exclusions.
  4. Add only the exact safe folder or file that repeatedly triggers heavy scanning.

Windows Security virus and threat protection settings

Add a narrow Microsoft Defender exclusion

If you do not know what writes to a folder, keep it protected. A clean scan today does not establish that files created there tomorrow are safe.

Lower Scheduled Scan CPU Pressure

On systems where scheduled scans are the main pain point, you can check Defender’s scan CPU guidance setting. This percentage is a target for average CPU use during applicable scans. It does not cap real-time checks when files open, and scheduled scans while the PC is idle are unthrottled by default. Lowering the target can make a scan take longer.

Get-MpPreference | Select-Object ScanAvgCPULoadFactor

To set a lower value, open PowerShell as administrator and use a number that still lets scans finish:

Set-MpPreference -ScanAvgCPULoadFactor 30

If the device is managed by work, school, Intune, or Group Policy, local changes may be overwritten. In that case, document the spike and ask the administrator to review Defender scan policy instead of fighting the setting locally.

Repair Windows Security When the Spike Never Settles

If Antimalware Service Executable stays high after every reboot and no heavy folder explains it, repair the Windows side before disabling protection.

  1. Install pending Windows updates and Microsoft Defender security intelligence updates.
  2. Restart the PC once after updates finish.
  3. If Windows features are also malfunctioning and you suspect system file damage, open an elevated terminal. Run DISM first and wait for it to complete successfully, then run System File Checker:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart and check whether the same workload still causes the problem. These commands repair Windows components; they do not diagnose high memory by themselves.

Also check whether another real-time antivirus, endpoint agent, VPN security module, or DLP tool is scanning the same files. Two tools watching the same file operations can multiply CPU and disk work.

Do Not Permanently Disable Defender Just to Stop CPU Spikes

Turning off real-time protection can make the spike disappear, but it also removes a major safety layer. Keep it on while you compare scan and workload activity. Do not rely on old registry tricks such as DisableAntiSpyware as a normal fix; modern Windows security settings, Tamper Protection, and managed policies may ignore or reverse those changes.

If you install another trusted antivirus, Microsoft Defender Antivirus normally switches off automatically on Windows 10/11 devices that are not onboarded to Microsoft Defender for Endpoint. On Windows 11, Smart App Control being On or in Evaluation can instead leave Defender in passive mode; managed devices onboarded to Defender for Endpoint can also use passive mode. A normal disabled state does not mean the switch failed. Check Windows Security to confirm your chosen antivirus is active, and do not force the mode by stopping security services or changing registry settings. This automatic handover is different from leaving the PC without working antivirus protection. [4]

When High CPU May Mean Malware

Antimalware Service Executable itself is normally legitimate, but malware can trigger Defender repeatedly or imitate Windows process names. Treat the situation as suspicious when:

  • MsMpEng.exe runs from a non-Microsoft folder.
  • Defender or Windows Security will not open.
  • CPU spikes began after a crack, game cheat, fake update, unknown installer, or email attachment.
  • Browser redirects, pop-ups, new extensions, unknown scheduled tasks, or unknown startup items appeared at the same time.
  • Defender finds the same threat again after every reboot.

In those cases, run a full scan and use a second-opinion cleanup tool. Gridinsoft Anti-Malware can help check active malware, suspicious startup entries, unwanted apps, and files that keep Defender busy.

Gridinsoft Anti-Malware
Check your PC for hidden threats.

Scan for malware and unwanted startup components left behind after cleanup.

Download Anti-Malware

For WindowsOfficial Gridinsoft download

Other Defender processes in Task Manager

If Task Manager shows MpDefenderCoreService.exe instead, that is a separate Defender Core Service. Use the MpDefenderCoreService.exe safety and internet-access guide to check its versioned platform path, Microsoft signature, normal service connections, and an Access denied message before changing the service.

If Task Manager instead shows NisSrv.exe or Microsoft Network Realtime Inspection Service, use the NisSrv.exe safety and high-CPU guide to verify WdNisSvc, the Defender Platform path, and the signature before trying to disable it.

FAQ

Is Antimalware Service Executable a virus?

Usually no. It is normally Microsoft Defender Antivirus running as MsMpEng.exe. It becomes suspicious when the file runs from an unusual folder, has no valid Microsoft signature, or appears with other compromise symptoms.

Why does MsMpEng.exe use so much CPU?

Common reasons include a scheduled scan, real-time scanning of many changed files, a large archive or game folder, a Defender update, another security tool scanning the same files, or Windows security component damage.

Can I end Antimalware Service Executable in Task Manager?

Windows usually prevents you from killing it because it is a protected security process. Even if you could stop it temporarily, the better fix is to schedule scans, identify the heavy path, repair Defender, or use a trusted alternative antivirus.

Should I exclude MsMpEng.exe from Defender scans?

No. Leave the Defender executable and its platform folders protected. Microsoft warns that exclusions reduce protection. If you use exclusions, make them narrow and only for a trusted path that you have confirmed is causing repeated scanning.

Is high memory usage always bad?

No. Moderate memory use by a security service can be normal if the PC remains responsive. Troubleshoot when memory keeps growing, CPU stays high for a long time, disk usage freezes the system, or the same spike returns after every restart.

Bottom Line

Antimalware Service Executable high CPU is usually a Defender workload problem, not a reason to switch protection off. Confirm the file path, move scans to idle hours, use Performance Analyzer when the cause is unclear, add only narrow trusted exclusions, and investigate an unexpected path or other independent signs of compromise. A high memory reading alone is not a malware warning.

References

  1. Microsoft. “Performance analyzer for Microsoft Defender Antivirus.” Microsoft Learn, last updated January 15, 2026. https://learn.microsoft.com/en-us/defender-endpoint/tune-performance-defender-antivirus
  2. Microsoft. “Microsoft Defender Antivirus full scan considerations and best practices.” Microsoft Learn, accessed June 7, 2026. https://learn.microsoft.com/en-us/defender-endpoint/mdav-scan-best-practices
  3. Microsoft. “Common mistakes to avoid when defining exclusions.” Microsoft Learn, last updated February 20, 2026. https://learn.microsoft.com/en-us/defender-endpoint/common-exclusion-mistakes-microsoft-defender-antivirus
  4. Microsoft. “Microsoft Defender Antivirus compatibility with other security products.” Microsoft Learn, last updated August 21, 2026; accessed October 19, 2026. Microsoft Defender compatibility documentation.
Share This Article
Cybersecurity Analyst
Follow:
Brendan Smith has spent over 15 years knee-deep in cybersecurity, chasing down malware from the gritty reverse-engineering of old-school trojans all the way to wrangling full-blown incident responses for small-to-medium businesses that couldn’t afford a full-blown breach. Over at Gridinsoft, he’s the guy piecing together those double-checked guides on nasty stuff like AsyncRAT, a remote access tool used in malware campaigns—helping readers make sense of the threat and work through cleanup without the extra headache.
Leave a Comment

AI Assistant

Hello! 👋 How can I help you today?