3 ways to limit Windows Defender CPU usage in Windows 10

Is the Windows Defender Service using high CPU at all times?

If you have real-time protection turned on, Windows Defender will perform a background scan and this can cause high CPU usage.

To prevent Windows Defender from using your CPU too much, you can use the following methods to limit the use of Windows Defender CPU in Windows 10.

Restrict Windows Defender CPU usage through PowerShell

1. Open Windows PowerShell as an administrator and issue the following command. It will display the current maximum CPU usage limit for Windows Defender.

Get-MpPreference | select ScanAvgCPULoadFactor

2. When you need to reduce CPU usage, type the following command and press Enter. Windows Defender will not use more than 30% of the CPU.

Set-MpPreference -ScanAvgCPULoadFactor 30

Limit Windows Defender CPU usage through Group Policy

1. Open Local Group Policy Editor and browse to:

Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Scan

On the right, double-click the policy Specify the maximum percentage of CPU utilization during a scan .

Double click the policy Specify the maximum percentage of CPU utilization during a scan

2. Select the Enabled option and limit the Windows Defender's CPU usage to 30% or whatever percentage you prefer. Click Apply and then click OK.

Select the Enabled option and limit the CPU usage of Windows Defender

3. Restart the computer to apply the changes.

Restrict Windows Defender CPU usage through Registry Editor

1. Open Registry Editor and navigate to:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows Defender

Right-click on the Windows Defender key and select New> Key . Name it Scan.

Create a new key and name it Scan

2. Next, right-click the newly created Scan sub-key and select New> DWORD (32-bit) Value .

Select New> DWORD (32-bit) Value

3. Name DWORD  AvgCPULoadFactor, then double-click it to specify the maximum CPU percentage for Windows Defender.

Name DWORD as AvgCPULoadFactor

4. Close Registry Editor. Restart the computer and check if Windows Defender is still using the CPU at a high level.