Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For Microsoft Defender, the safest practical adjustments are to schedule quick scans rather than routine full scans and, on managed PCs, reduce scheduled-scan CPU priority or its CPU usage limit. Keep real-time and cloud protection enabled. Use exclusions only to address a specific, verified scanning conflict: they leave excluded content with less protection. These changes can reduce scan-related processor competition, but the cited guidance does not establish a general setting that reliably lowers antivirus memory use across products.

Start by identifying what is using resources

Antivirus settings vary by product and configuration, so first identify the process responsible for the CPU or memory use in Task Manager. If the load occurs while a scan is running, scan type, timing, and scan priority are relevant. If it persists outside scans, changing scheduled-scan settings may not address the cause.

Microsoft’s performance troubleshooting guidance recommends diagnosing performance issues rather than assuming a particular Defender setting is responsible: Troubleshoot performance issues – Microsoft Defender for Endpoint.

Which settings can help without routinely reducing protection?

Schedule quick scans instead of routine full scans

Microsoft recommends scheduled quick scans alongside always-on real-time and cloud protection. Its guidance says most users do not need scheduled full scans: “In general, there’s no need to schedule a full scan, and most users never need to manually run full scans.” A quick scan is therefore the sensible routine scheduled choice for most users; it is not a reason to disable ongoing protection. See Microsoft Defender Antivirus full scan considerations and best practices.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Run scans at a less disruptive time

Scheduling scans when the PC is less likely to be in use can reduce the chance that scanning competes with foreground work. This changes when scan activity occurs, not the protection provided by real-time scanning. Microsoft’s scan best-practices guidance covers scheduled scans and maintaining real-time and cloud protection: Microsoft Defender Antivirus full scan considerations and best practices.

Keep real-time and cloud protection enabled

Real-time protection checks files as they are opened or downloaded. Microsoft says that while real-time protection is off, files opened or downloaded during that period are not scanned at that time; it also describes the off state as temporary, with protection turning back on after a short while. It is not a dependable background-resource setting. Microsoft’s guidance is at Virus and Threat Protection in the Windows Security App.

Defender controls for reducing CPU competition during scans

Lower scheduled-scan priority

In centrally managed Defender environments, an administrator can enable low CPU priority for scheduled scans. This lets other work take precedence, but a scan may take longer to finish. These are policy-oriented controls, not necessarily a simple switch in the consumer Windows Security app.

Set a lower scan CPU usage limit

Administrators can also reduce the CPU usage limit for scans. Microsoft describes the percentage as guidance to the scanning engine, not a hard cap on total processor use. Lowering it can reduce competition for CPU time while a scan runs, with longer scan completion as the trade-off. Neither CPU control promises to reduce memory use. Details are in Microsoft’s Defender performance troubleshooting guidance.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use exclusions only for a known, trusted conflict

An exclusion can prevent repeated scanning of a particular file, folder, file type, or process, but it also creates a protection gap for the excluded content. Microsoft advises caution. Its documentation says Defender exclusions apply to real-time scanning; scheduled Defender scans or other antimalware products might still inspect excluded items. The available exclusion choices and their effects are described in Microsoft’s Windows Security guidance.

Prefer the narrowest possible exclusion and use one only when you have a specific, trusted item and a demonstrated scanning conflict. Avoid excluding broad folders, file types, or processes as a general performance tweak.

Settings differ across antivirus products

McAfee exclusions have a different scope

McAfee says excluded files or apps are not scanned by its real-time, on-demand, scheduled, and command-line scanners. That is broader than the scope Microsoft describes for Defender exclusions, so do not assume exclusion behavior is interchangeable between products. Check the installed product’s documentation before changing its settings: Exclude files from virus scans on Windows and macOS.

A faster scan mode can use more resources

McAfee’s Fast Scan documentation says that its faster full scan uses all available system resources, including CPU and memory. That is specific to this McAfee mode, not a general rule for antivirus products, but it illustrates why prioritizing scan speed can increase resource use while scanning: How to run a Fast Scan in Windows.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

McAfee also warns that turning off real-time scanning leaves the PC exposed to threats: Setting real-time scanning options.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What to change—and what not to expect

Setting Potential benefit Trade-off or limit
Scheduled quick scans in Defender Avoids routinely scheduling full scans that Microsoft says most users do not need. Does not establish a cross-product reduction in memory use.
Scan timing Moves scan activity away from times when you need the PC responsive. Changes timing, not real-time protection.
Lower Defender scan priority or CPU limit Can reduce scan competition for CPU time in managed environments. May extend scan duration; the CPU percentage guidance is not a hard cap.
Narrow, justified exclusion May avoid repeated scanning of a known item causing a conflict. Excluded content receives less scanning; scope varies by product.
Turn off real-time protection Not a recommended routine resource-saving adjustment. Files opened or downloaded while protection is off are not scanned at that time.

The cited vendor documentation does not provide a comparable cross-product measurement of memory reduction or establish a universal antivirus memory setting. Treat memory use as product- and situation-specific rather than expecting one switch to solve it.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.