Open in the explorer

Process Exclusions

Exclusions de processus

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › Windows Components › Microsoft Defender Antivirus › Exclusions FR: Configuration ordinateur › Stratégies › Modèles d'administration › Composants Windows › Antivirus Microsoft Defender › Exclusions
Supported on
At least Windows Server 2012, Windows 8 or Windows RT FR: Au minimum Windows Server 2012, Windows 8 ou Windows RT
ADMX file
WindowsDefender.admx
Internal name
WindowsDefender/Exclusions_Processes

Explanation

This policy setting allows you to disable real-time scanning for any file opened by any of the specified processes. This policy does not apply to scheduled scans. The process itself will not be excluded. To exclude the process, use the Path exclusion. Processes should be added under the Options for this setting. Each entry must be listed as a name value pair, where the name should be a string representation of the path to the process image. Note that only executables can be excluded. For example, a process might be defined as: "c:\windows\app.exe". The value is not used and it is recommended that this be set to 0.

French text from Windows 11 26H2

Ce paramètre de stratégie vous permet de désactiver les analyses en temps réel pour tout fichier ouvert par l’un des processus spécifiés. Cette stratégie ne s’applique pas aux analyses planifiées. Le processus lui-même n’est pas exclu. Pour exclure le processus, utilisez l’exclusion de chemin d’accès. Les processus doivent être ajoutés sous Options pour ce paramètre. Chaque entrée doit être répertoriée en tant que paire nom/valeur, où le nom doit être une représentation sous forme de chaîne du chemin d’accès à l’image du processus. Notez que seuls les exécutables peuvent être exclus. Par exemple, un processus peut être défini en tant que « c:\windows\app.exe ». La valeur n’est pas utilisée et il est recommandé qu’elle soit égale à 0.

Use cases

Turns off real-time scanning of files opened by the listed processes, typically for a database server or line-of-business application whose disk access slows down under antivirus. The policy does not apply to scheduled scans, and the process itself is not excluded: that requires a separate path exclusion.

Prefer the full path (c:\test\test.exe) over the bare image name, which matches any process with that name from any location, including removable media. Another consequence flagged by Microsoft: an excluded process also escapes inspection by network protection and ASR rules, and its files can still trigger EDR alerts.

Microsoft sources: Exclusions in Microsoft Defender Antivirus · Configure custom exclusions for Microsoft Defender Antivirus

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows Defender\Exclusions
Value name
Exclusions_Processes
StateValue written
Enablednot defined in the ADMX (see the options below)
Disablednot defined in the ADMX (see the options below)

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

The ADMX does not specify the value written when enabled; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled). The commands below use 1/0 as an assumption.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Enable

# Enable: WindowsDefender/Exclusions_Processes
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Exclusions'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'Exclusions_Processes' -Value 1 -Type DWord  # assumed value (not defined in the ADMX)
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Exclusions\Processes'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Process Exclusions
$items = @{
    '<name1>' = '<value1>'
    '<name2>' = '<value2>'
}  # Replace the values with your own
$items.GetEnumerator() | ForEach-Object { Set-ItemProperty -Path $k -Name $_.Key -Value $_.Value -Type String }

Disable

# Disable: WindowsDefender/Exclusions_Processes
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Exclusions'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# The ADMX does not specify the value written; the GPO editor usually writes REG_DWORD 1 (enabled) / 0 (disabled)
Set-ItemProperty -Path $k -Name 'Exclusions_Processes' -Value 0 -Type DWord  # assumed value (not defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": WindowsDefender/Exclusions_Processes
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Exclusions'
Remove-ItemProperty -Path $k -Name 'Exclusions_Processes' -ErrorAction SilentlyContinue
$k = 'HKLM:\Software\Policies\Microsoft\Windows Defender\Exclusions\Processes'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinue

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Process ExclusionsExclusions de processusExclusions_ProcessesListList (table)listSoftware\Policies\Microsoft\Windows Defender\Exclusions\ProcessesName = value pairs · additiveREG_SZ (values under the key)

Availability