If your computer suddenly sounds like a jet engine and Task Manager shows Antimalware Service Executable hogging 100% of your CPU, don't panic. Nine times out of ten, Windows Defender has either trapped itself in a bizarre self-scanning loop or choked on a corrupted definition file.
You don't have to rip out your antivirus and leave your machine wide open to fix it. Let's walk through how to put a leash on its resource usage and stop that ridiculous loop without compromising your security.
Time needed: About 5 to 10 minutes
Best overall fix: Capping CPU usage with Group Policy
Most common reason: Windows Defender trying to scan its own folder
Tools we'll use: Group Policy Editor, Task Scheduler, Command Prompt, Registry Editor
Why Is MsMpEng.exe Choking Your CPU?
MsMpEng.exe is simply the background engine behind Windows Defender's real-time protection. It isn't the same thing as MRT.exe - which is Microsoft's standalone Malicious Software Removal Tool that only pops up once in a while.
Instead, MsMpEng.exe is constantly watching everything: inspecting files you download, checking network traffic, and monitoring background apps. But when it runs into massive folders packed with thousands of tiny files - or worse, gets confused and tries to scan its own directory - it spirals into an infinite loop that pins your processor at 100% and grinds your PC to a halt.
Method 1: Put a Hard Cap on Defender’s CPU Usage (The Smart Move)
Completely shutting off your antivirus leaves your system wide open, which is rarely a good trade-off just to get your fans to quiet down. A far better strategy is to tell Windows Defender exactly how much of your processor it is allowed to touch. That way, you keep your real-time protection running in the background without letting it hijack your entire machine when you're trying to get work done.
Cap It via the Group Policy Editor (GPO)
Hit Win + R, type gpedit.msc, and press Enter. Once the editor opens, drill down through Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Scan.
Look for the policy named Specify the maximum percentage of CPU utilization during a scan and double-click it. Switch the toggle to Enabled, and down in the options box, dial the number back to somewhere between 20 and 50 percent (setting it to 50% usually works wonders for most setups). Hit Apply, click OK, and give your PC a quick restart.
Method 2: Break Defender Out of Its Self-Scanning Loop
Believe it or not, Windows Defender has a notorious habit of trying to scan its own installation folder. When that happens, it triggers an endless loop where it scans itself scanning itself, immediately pinning your CPU and thrashing your drive. The easiest fix here is simply telling Defender to look the other way when it comes across its own files.
Add Windows Defender to Your Exclusions List
Open up your Start menu, launch Windows Security, and click on Virus & threat protection. Under the "Virus & threat protection settings" heading, click the blue Manage settings link.
Scroll down until you spot the Exclusions section, then click Add or remove exclusions. Click the Add an exclusion button, choose Folder from the dropdown, and navigate to C:\Program Files\Windows Defender. Confirm the prompt, and Defender will stop poking around inside its own house.
Whitelist Heavy Dev Folders (node_modules, VMs, Games)
If you do any coding or spin up virtual environments, you probably know that project directories contain tens of thousands of tiny files that drive real-time scanners crazy. Whenever you build or run an app, Defender tries to inspect every single dependency, bringing your machine to its knees. Pop back into that same exclusions menu and add your node_modules folders, large game install directories, and virtual disk storage paths.
Method 3: Tame Defender's Background Scan Schedule
A lot of the time, heavy background scans kick off right in the middle of your workday because Windows defaults to running them with maximum system priority. With a couple of quick tweaks inside Task Scheduler, you can stop these maintenance tasks from commandeering all your hardware resources while you're in the middle of using the machine.
Drop Its Privileges in Task Scheduler
Hit Win + S, search for Task Scheduler, and launch it. On the left sidebar, navigate to Task Scheduler Library > Microsoft > Windows > Windows Defender. In the middle pane, find and double-click Windows Defender Scheduled Scan.
In the General tab, look near the bottom and uncheck Run with highest privileges. Next, hop over to the Conditions tab and uncheck every single box there - this stops Windows from firing off an aggressive scan the second it thinks you stepped away from your desk.
Method 4: Clear Out Corrupted Virus Definitions
Every now and then, Defender gets stuck in an update rut where a downloaded signature file ends up broken or half-installed. The service keeps burning CPU cycles trying to parse the corrupted data over and over. Purging that local cache forces Windows to start from scratch and grab clean definition files.
Reset the Update Cache via Command Prompt
Open your Start menu, type cmd, right-click Command Prompt, and choose Run as administrator. Type cd C:\Program Files\Windows Defender and hit Enter. Next, paste in mpcmdrun.exe -removedefinitions -all and press Enter to wipe the existing cache.
After that finishes running, type mpcmdrun.exe -signatureupdate and hit Enter again. This will reach out directly to Microsoft's servers, pull down the freshest set of signatures, and overwrite whatever was causing the hangup.
Check for Damaged System Files with SFC
If the definition reset didn't do the trick, underlying Windows files might be damaged and causing the security service to freak out. In that same admin Command Prompt window, type sfc /scannow and let it do its thing. Give the verification tool a few minutes to hit 100 percent, and if it tells you it found and repaired broken system files, restart your PC right away.
Method 5: The Last-Resort Nuclear Option
If you've tried everything above and MsMpEng.exe is still running wild, you might just have to kill the service altogether to get your computer back. Just remember: if you go this route, you have to install a reliable alternative antivirus straight away so you don't leave your machine completely unprotected on the web.
Crucial Step: Disable Tamper Protection First
Don't skip this part, or the tweaks below won't do a single thing. Windows 10 and 11 come with a safeguard called Tamper Protection designed to block unauthorized registry edits from turning off security tools.
Open Windows Security, head into Virus & threat protection, click Manage settings, and flip the Tamper Protection switch to Off. If you leave this turned on, Windows will silently ignore every registry edit you try to make next.
Try Disabling the Service Directly (services.msc)
Press Win + R, enter services.msc, and hit Enter to pull up your system services. Scroll down the list until you locate Windows Defender Antivirus Service (it might also appear as WinDefend). Right-click it, head into Properties, set the Startup type dropdown to Disabled, click the Stop button, and save your changes.
Shut It Down via the Registry Editor
Open the Run prompt again with Win + R, type regedit, and press Enter. In the address bar at the top, paste this path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender.
Right-click any empty space in the right pane, pick New > DWORD (32-bit) Value, and name it DisableAntiSpyware. Double-click that new entry, change its Value data from 0 to 1, and hit OK. From there, you can restart your PC via the command line so the change sticks.
Sniffing Out Third-Party Software Conflicts
Another classic scenario is running another security tool or aggressive utility alongside Defender. When two background monitors watch the same active directory, they can end up inspecting each other back and forth in an endless loop, pinning your CPU to the wall.
Track Down Rogue Apps with a Clean Boot
Open the Run prompt, type msconfig, and hit Enter to launch System Configuration. Head over to the Services tab, make sure you check the box that says Hide all Microsoft services (so you don't break Windows), and then click Disable all.
Next, switch to the Startup tab, open Task Manager, and disable your startup apps. Restart your PC to see if your CPU usage calms down without all that background clutter running.
If that fixes the load, you know a third-party app was the troublemaker - just uninstall the conflicting tool, hop back into msconfig, and re-enable your services. And if you're still seeing occasional spikes after all this, head into Windows Update and let every pending security patch finish installing, as Microsoft frequently pushes out hotfixes for these background quirks.
