Office Admin Explorer

Configure Application Guard container precreation

Registry value
prewarmwindow
Group PolicyConfigure Application Guard container precreation
German versionKonfiguration des vorab erstellten Application Guard-Containers.
Intune settings catalogConfigure Application Guard container precreation. (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_ConfigurePreCreateInApplicationGuard
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Security Settings\Trust Center\Application Guard
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\Sicherheitseinstellungen\Trust Center\Application Guard

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\common\security\applicationguard
prewarmwindowdecimal 0–65536

Not configured = the value does not exist – the application default applies and users may change the setting.

PowerShell

Check the current value (read-only)

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\common\security\applicationguard"
foreach ($name in @('prewarmwindow')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.

Enable

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\16.0\common\security\applicationguard"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'prewarmwindow' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # range 0–65536
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\common\security\applicationguard"
Remove-ItemProperty -Path $key -Name 'prewarmwindow' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Configure Application Guard container precreation. (User)

Settings catalog → Add settings → search for the name above.

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./User/Vendor/MSFT/Policy/Config/office16v8~Policy~L_MicrosoftOfficeSystem~L_SecuritySettings~L_trustcenter241~L_ApplicationGuard/L_ConfigurePreCreateInApplicationGuard
Data typeString
Value<enabled/> · <disabled/>

This policy has options: add one <data id="…" value="…"/> per element after <enabled/>. The element IDs are in the ADMX file.

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Configure Application Guard container precreation. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft 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.

Same category: Microsoft Office 2016 › Security Settings › Trust Center › Application Guard

All policies in this category · All 945 policies of office16.admx