CPU throttling type
Verified with Windows 11 25H2 — updated on July 10, 2026
Supported on: At least Windows Server 2016, Windows 10 Version 1607
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\Microsoft Defender Antivirus\Scan Description
This policy setting determines whether the maximum percentage CPU utilization permitted during a scan applies only to scheduled scans, or to both scheduled and custom scans (but not real-time protection). The maximum CPU utilization limit is also referred to as CPU throttling, or a CPU usage limit. The default value for this policy setting is True, which means CPU throttling is applied only to scheduled scans. If you either enable or do not configure this setting, CPU throttling will apply only to scheduled scans. If you disable this setting, CPU throttling will apply to scheduled and custom scans.
Registry
HKLM
Software\Policies\Microsoft\Windows Defender\Scan Value name: ThrottleForScheduledScanOnly
Enabled: ThrottleForScheduledScanOnly = 1
Disabled: ThrottleForScheduledScanOnly = 0
Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: CPU throttling type
; State: Enabled
; Supported on: At least Windows Server 2016, Windows 10 Version 1607
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows Defender\Scan]
"ThrottleForScheduledScanOnly"=dword:00000001More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: CPU throttling type
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1607
$path = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Scan'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ThrottleForScheduledScanOnly' -Value 1 -Type DWordIntune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune.Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: CPU throttling type
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1607
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows Defender\Scan' -Name 'ThrottleForScheduledScanOnly' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: CPU throttling type
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1607
$path = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Scan'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ThrottleForScheduledScanOnly' -Value 1 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: CPU throttling type
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1607
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: CPU throttling type
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1607
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows Defender\Scan' -Name 'ThrottleForScheduledScanOnly' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: CPU throttling type
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10 Version 1607
$path = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Scan'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ThrottleForScheduledScanOnly' -Value 1 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.