Forum Discussion

philippwree's avatar
philippwree
Copper Contributor
Jul 09, 2020

Limit Windows Defender CPU Usage

I have the problem that our Clients use too much CPU during a FullScan. Actually, the usage is limited to 20%, but the setting seems to have no effect. Whether I set it via Configuration Manager or GPO, the result is the same.

 

Does anyone have a similar problem or even better... a solution?

 

19 Replies

  • Kapil_Madaan's avatar
    Kapil_Madaan
    Copper Contributor

    This might help.

     

    https://learn.microsoft.com/en-us/powershell/module/defender/set-mppreference?view=windowsserver2022-ps#-scanavgcpuloadfactor

  • Daniel_Larsson's avatar
    Daniel_Larsson
    Copper Contributor

    philippwree We have the same issue, CPU limit is completely ignored. Is there a solution anywhere? iv been searching but cant find anything usefull

    • mongrel15's avatar
      mongrel15
      Copper Contributor

      Daniel_Larsson In your antimalware policy under “Scheduled Scans”, switch the option “Start a scheduled scan only when the computer is idle” to no. That solved the problem for us.
      It seems that the check by Microsoft is flawed. If Endpoint thinks the system is idle, he ignores the CPU limit.

       

      • AJP123's avatar
        AJP123
        Copper Contributor

        mongrel15 

        Changing the following setting to NO doesn't make any difference for us -  "Start a scheduled scan only when the computer is idle” / "“ScanOnlyIfIdle”  doesn't make any difference for us.

         

        I tried setting "AvgCPULoadFactor"n in the registry to 1% and it would still hit up to 68%.

         

  • mongrel15's avatar
    mongrel15
    Copper Contributor

    Did you find any solution for the Windows Defender problem philippwree?

     

    We are currently distributing the load on our host by running the scans of the VMs at different times. However, we still have the problem with the load on the CPU.

  • mongrel15's avatar
    mongrel15
    Copper Contributor

    Have the same problem as philippwree!

    In the Configuration Manager, we defined a CPU load of 30% for our windows servers in the default defender policy. The setting has also been correctly transmitted to the agents.

    Checked local via powershell "Get-MpPreference" and in the registry "HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows Defender \ Scan \ AvgCPULoadFactor". The values ​​are correctly limited to 30%.

     

    Despite the throttling, the process "MsMpEng.exe" uses up to 100% CPU for scheduled and manual defender scans (full and quick).

     

    Possibly a bug in a microsoft defender update?

    • DanXC's avatar
      DanXC
      Copper Contributor
      Yes... It would be great if the setting actually worked, eh?
      😞
    • rahul_malgun's avatar
      rahul_malgun
      Copper Contributor
      Hello do we got any solution for the cpu utilization which is consuming more than 80 % for the antimalware service executable ?

Resources