Policy
Trigger a quick scan after X days without any scans
Windows 11 25H2
Policy overview
Key metadata and intent for this policy.
Supported OS tags: Windows10, Windows10RT, Windows11, Windows8, Windows81, WindowsRT, WindowsRT81, WindowsServer2012, WindowsServer2012R2, WindowsServer2016
This policy setting defines the number of days that can pass since the last scan before an aggresive catchup quick scan is automatically triggered. The value represents the number of days that can pass without any scans being performed before an agressive quick scan will be triggered. Valid values range from 7 to 60 days. If not configured, aggressive quick scans will be disabled. By default, the value is set to 25 days when enabled.
Registry values
How enabled and disabled states update the registry.
No explicit registry values are set for enabled or disabled states.
Policy elements
Inputs and configuration options exposed by this policy.
| Element | Type | Registry mapping | Constraints & behavior |
|---|---|---|---|
Specify how many days without scans should pass before an aggressive quick scan is triggered ID Scan_DaysUntilAggressiveCatchupQuickScan | decimal | HKLM\Software\Policies\Microsoft\Windows Defender\Scan\DaysUntilAggressiveCatchupQuickScan Type REG_DWORD | Range: 7 to 60 |
Other policies in this category
Explore related policies at the same level.
- ComputerAllow users to pause scanAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerCheck for the latest virus and spyware security intelligence before running a scheduled scanAt least Windows Vista
- ComputerConfigure local setting override for maximum percentage of CPU utilizationAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerConfigure local setting override for schedule scan dayAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerConfigure local setting override for scheduled quick scan timeAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerConfigure local setting override for scheduled scan timeAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerConfigure local setting override for the scan type to use for a scheduled scanAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerConfigure low CPU priority for scheduled scansAt least Windows Server 2016, Windows 10 Version 1809
- ComputerConfigure scanning of network filesAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerCPU throttling typeAt least Windows Server 2016, Windows 10 Version 1607
- ComputerCreate a system restore pointAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerDefine the number of days after which a catch-up scan is forcedAt least Windows Server 2012, Windows 8 or Windows RT