Open in the explorer

Turn on Microsoft Defender Application Guard in Managed Mode

Activer Microsoft Defender Application Guard en mode géré

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › Windows Components › Microsoft Defender Application Guard FR: Configuration ordinateur › Stratégies › Modèles d'administration › Composants Windows › Microsoft Defender Application Guard
Supported on
Windows 10 Enterprise, Windows 10 Education, or later FR: Windows 10 Entreprise, Windows 10 Éducation ou version ultérieure
ADMX file
apphvsi.admx
Internal name
apphvsi/AppHVSI_AllowAppHVSIConfig

Explanation

This policy setting enables application isolation through Microsoft Defender Application Guard.

Application Guard uses Windows Hypervisor to create a virtualized environment for apps that are configured to use virtualization-based security isolation. While in isolation, improper user interactions and app vulnerabilities can’t compromise the kernel or any other apps running outside of the virtualized environment.

If you enable this setting, Application Guard is turned on for your organization.

French text from Windows 11 26H2

Ce paramètre de stratégie permet l’isolation de l’application via Microsoft Defender Application Guard.

Application Guard utilise l’hyperviseur Windows pour créer un environnement virtualisé pour des applications configurées pour utiliser l’isolation de sécurité basée sur la virtualisation. Pendant l’isolation, les interactions incorrectes d’utilisateurs et les vulnérabilités d’applications ne peuvent pas compromettre le noyau ni d’autres applications exécutées hors de l’environnement virtualisé.

Si vous activez ce paramètre, Application Guard sera activé pour votre organisation.

Registry

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\AppHVSI
Value name
not defined in the ADMX

Enable / disable values: not 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.

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: apphvsi/AppHVSI_AllowAppHVSIConfig
$k = 'HKLM:\SOFTWARE\Policies\Microsoft\AppHVSI'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
#
Set-ItemProperty -Path $k -Name 'AllowAppHVSI_ProviderSet' -Value 1 -Type DWord  # between 0 and 3

Disable

# Disable: apphvsi/AppHVSI_AllowAppHVSIConfig
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": apphvsi/AppHVSI_AllowAppHVSIConfig
$k = 'HKLM:\SOFTWARE\Policies\Microsoft\AppHVSI'
Remove-ItemProperty -Path $k -Name 'AllowAppHVSI_ProviderSet' -ErrorAction SilentlyContinue

Options (1)

LabelControlRegistry valueREG typeConstraints / details
AppHVSI_AllowAppHVSI_TextBoxNumeric boxdecimalAllowAppHVSI_ProviderSetREG_DWORD
Min: 0 · Max: 3 · Default (UI): 1

Availability

Windows Server