Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to:
- Microsoft Defender for Endpoint Plan 1
- Microsoft Defender for Endpoint Plan 2
- Microsoft Defender Antivirus
Platforms
- Windows
This article describes how to configure scheduled scans using Group Policy. To learn more about scheduling scans and about scan types, see Configure scheduled quick or full Microsoft Defender Antivirus scans.
Configure antivirus scans using Group Policy
On your Group Policy management machine, in the Group Policy Editor, go to Computer configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus > Scan.
Right-click the Group Policy Object you want to configure, and then select Edit.
Specify the settings for the Group Policy Object, and then select OK.
Repeat steps for each setting you want to configure.
Deploy your Group Policy Object as you normally do. If you need help with Group Policy Objects, see Create a Group Policy Object.
Note
When configuring scheduled scans, the setting Start the scheduled scan only when computer is on but not in use (which is enabled by default) can affect the expected scheduled time by requiring the machine to be idle first. For weekly scans, the default behavior on Windows Server and Windows 10 and later, is to scan outside of the automatic maintenance when the machine is idle. To change this behavior, modify the settings by disabling "Start the scheduled scan only when computer is on but not in use" (ScanOnlyIfIdle), and then define a schedule.
For more information, see the Manage when protection updates should be downloaded and applied and Prevent or allow users to locally modify policy settings articles.
Group Policy settings for scheduling daily scans (quick)
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Scan | Specify the daily interval for running quick scans. | Specify the number of hours that should pass before the next quick scan is performed. For example, to run every two hours, enter 2, for once a day, enter 24. Enter 0 to never run a daily quick scan. | Never |
| Scan | Specify the time for a daily quick scan | Specify the number of minutes after midnight (for example, enter 60 for 1 AM.) If this setting is set to 0, daily quick scans don't run. | 120 (2 AM) |
Tip
When scheduling a scan, depending on your environment, if your client devices are shutdown after-hours, you might want to consider setting the daily quick scans during lunch time (720).
Group Policy settings for scheduling weekly scans (quick or full)
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Scan | Specify the scan type to use for a scheduled scan | Quick scan | |
| Scan | Specify the day of the week to run a scheduled scan | Specify the day (or never) to run a scan. | Never |
| Scan | Specify the time of day to run a scheduled scan | Specify the number of minutes after midnight to run a scan (for example, enter 60 for 1 AM). | 2 AM. |
Tip
Our recommendation for scheduled scans is to configure quick scan together with always-on real-time protection and cloud protection, as this combination provides strong coverage against malware that starts with the system and kernel-level malware.
Warning
Generally, there's no need to schedule a full scan, and most users won't need to manually run full scans (see Comparing quick scan, full scan, and custom scan).
Group Policy settings for general scheduling scans
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Root | Randomize scheduled task times | In Microsoft Defender Antivirus, randomize the start time of the scan to any interval from 0 to 23 hours. By default, scheduled tasks begin at a random time within four hours of the time specified in Task Scheduler. | Enabled |
| Root | Configure scheduled task times randomization window | - This setting lets you set the start time for scheduled task scans and security updates. - When enabled, you can choose a randomization window between 1 and 23 hours. - The Randomize Scheduled Task Times uses the specified window. - If disabled or not configured, it randomizes times between 0 and 4 hours. |
Not configured (Disabled) |
Tip
Enable randomization for Virtual Machines (VMs), Virtual Desktop Infrastructure (VDI), and Azure Virtual Desktop (AVD) devices to ensure that scheduled scans don't run simultaneously. This helps prevent CPU and disk I/O bottlenecks on the parent partition (also known as the Host).
Group Policy settings for scheduling scans for specifying the maximum percentage of CPU utilization during a scan
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Scan | Specify the maximum percentage of CPU utilization during a scan | Configure the maximum percentage CPU utilization permitted during a scan. Valid values for this setting are a percentage represented by integers 5 to 100. A value of 0 indicates that there should be no throttling of CPU utilization. | Enabled - 50 |
Note
Reducing the maximum CPU utilization during a scan to between 5% and 30% will extend the duration of the scheduled scan. For environments with a maintenance window, please take this into consideration.
Group Policy settings for scheduling scans for lowering the CPU priority
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Scan | Start the scheduled scan only when computer is on but not in use | Scheduled scans won't run, unless the computer is on but not in use | Enabled |
Group Policy settings for scheduling scans for when an endpoint isn't in use
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Scan | Start the scheduled scan only when computer is on but not in use | Scheduled scans won't run, unless the computer is on but not in use | Enabled |
Note
When you schedule scans for times when endpoints aren't in use, scans don't honor the CPU throttling configuration and takes full advantage of the resources available to complete the scan as fast as possible.
Group Policy settings for scheduling remediation-required scans
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Remediation | Specify the day of the week to run a scheduled full scan to complete remediation | Specify the day (or never) to run a scan. | Never |
| Remediation | Specify the time of day to run a scheduled full scan to complete remediation | Specify the number of minutes after midnight (for example, enter 60 for 1 AM.) | 120 (2 AM) |
Group Policy settings for scheduling scans after protection updates
| Location | Setting | Description | Default setting (if not configured) |
|---|---|---|---|
| Signature updates | Turn on scan after Security intelligence update | A process scan will occur immediately after a new protection update is downloaded | Enabled |
See also
Troubleshoot Microsoft Defender Antivirus scan issues
Performance analyzer for Microsoft Defender Antivirus
Use PowerShell cmdlets to configure and manage Microsoft Defender Antivirus
Set the PowerShell cmdlet to configure and manage Microsoft Defender Antivirus
Defender Antivirus specific PowerShell functions
Troubleshoot Microsoft Defender Antivirus settings
Tip
If you're looking for Antivirus related information for other platforms, see:
- Set preferences for Microsoft Defender for Endpoint on macOS
- Microsoft Defender for Endpoint on Mac
- macOS Antivirus policy settings for Microsoft Defender Antivirus for Intune
- Set preferences for Microsoft Defender for Endpoint on Linux
- Microsoft Defender for Endpoint on Linux
- Configure Defender for Endpoint on Android features
- Configure Microsoft Defender for Endpoint on iOS features
Tip
Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: Microsoft Defender for Endpoint Tech Community.