Hi,
Thank you for posting in Microsoft Q&A forum.
1,Per my experience, the CPU limit setting is not a hard limit but rather a guidance for the scanning engine to not exceed this maximum on average (so the corresponding registry key is named Average CPU Load Factor). The CPU limit setting is used to set the maximum CPU usage for Microsoft Defender for Endpoint scans, but it does not affect real-time protection.
2,You can try to configure Microsoft Defender Antivirus always-on protection settings using Group Policy. To do this, open Local Group Policy Editor, expand the tree to Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus and follow these steps:
Double-click the Allow antimalware service to start up with normal priority policy setting in the details pane on the right and set it to Enabled.
Double-click the Real-time Protection policy setting and configure the policy settings as per your choice.
3,Additionally, you can set limits on the CPU and RAM used by the Microsoft Defender Antivirus Service during scans by using the Set-MpPreference cmdlet. You can set the maximum percentage of CPU usage during a scan by using the "-ScanAvgCPULoadFactor" parameter.
Please refer to:
Thanks for your time. Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.