Open in the explorer

Configure Application Guard container precreation

Type
User
GPO path
User Configuration › Policies › Administrative Templates › Microsoft Office 2016 › Security Settings › Trust Center › Application Guard
Supported on
At least Windows Server 2016, Windows 10
ADMX file
office16.admx
Internal name
office16/L_ConfigurePreCreateInApplicationGuard

Explanation

This policy setting determines if the Application Guard container, for isolating untrusted files, is pre-created for improved run time performance.

If you enable this policy setting, you can specify the number of days to continue pre-creating an Application Guard container if the user has not opened a file with Application Guard. Pre-creating a container when the user logs in will decrease the wait time when opening an untrusted file.

“65535” will configure Office to always create an Application Guard container when a user logs into Windows.
"20" will configure Office to pre-create the container each time a user logs into Windows for up to 20 days after the last time the user opened an untrusted file using Application Guard.
“0” will configure Office to never pre-create the container. Instead the container will only be created when a user opens their first untrusted file after logging into Windows.

Note: if you configure Office to never pre-create a container then users will experience a longer wait when opening an untrusted file after logging into Windows.

If you disable or don’t configure this setting, Office will use a built-in heuristic to pre-create the container.

Note: This policy setting only applies to Microsoft 365 Apps for enterprise.

Registry

HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\common\security\applicationguard
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: office16/L_ConfigurePreCreateInApplicationGuard
$k = 'HKCU:\software\policies\microsoft\office\16.0\common\security\applicationguard'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Pre-Create Window (days)
Set-ItemProperty -Path $k -Name 'prewarmwindow' -Value 0 -Type DWord  # between 0 and 65536

Disable

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

Revert to "Not configured"

# Revert to "Not configured": office16/L_ConfigurePreCreateInApplicationGuard
$k = 'HKCU:\software\policies\microsoft\office\16.0\common\security\applicationguard'
Remove-ItemProperty -Path $k -Name 'prewarmwindow' -ErrorAction SilentlyContinue

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Pre-Create Window (days):L_SetAppGuardPreWarmWindowValueNumeric boxdecimalprewarmwindowREG_DWORD
Min: 0 · Max: 65536

Application

Microsoft 365 Apps / Office (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.