Open in the explorer

Controls whether unload event handlers can be disabled.

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Google › Google Chrome User Configuration › Policies › Administrative Templates › Google › Google Chrome
Supported on
Microsoft Windows 7 or later
ADMX file
chrome.admx
Internal name
chrome/ForcePermissionPolicyUnloadDefaultEnabled

Explanation

unload event handlers are being deprecated. Whether they fire depends on the unload Permissions-Policy. Currently, they are allowed by policy by default. In the future they will gradually move to being disallowed by default and sites must explicitly enable them using Permissions-Policy headers. This enterprise policy can be used to opt out of this gradual deprecation by forcing the default to remain as enabled.

Pages may depend on unload event handlers to save data or signal the end of a user session to the server. This is not recommended as it is unreliable and impacts performance by blocking use of BackForwardCache. Recommended alternatives exist, however the unload event has been used for a long time. Some applications may still rely on them.

If this policy is set to false or not set, then unload events handlers will be gradually deprecated in-line with the deprecation rollout and sites which do not set Permissions-Policy header will stop firing `unload` events.

If this policy is set to true then unload event handlers will continue to work by default.

NOTE: This policy had an incorrectly documented default of `true` in M117. The unload event did and will not change in M117, so this policy has no effect in that version.

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome
HKEY_CURRENT_USER\Software\Policies\Google\Chrome
Value name
ForcePermissionPolicyUnloadDefaultEnabled
StateValue written
EnabledREG_DWORD = 1
DisabledREG_DWORD = 0

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.

Computer (HKLM)

Enable

# Enable: chrome/ForcePermissionPolicyUnloadDefaultEnabled
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'ForcePermissionPolicyUnloadDefaultEnabled' -Value 1 -Type DWord

Disable

# Disable: chrome/ForcePermissionPolicyUnloadDefaultEnabled
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'ForcePermissionPolicyUnloadDefaultEnabled' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": chrome/ForcePermissionPolicyUnloadDefaultEnabled
$k = 'HKLM:\Software\Policies\Google\Chrome'
Remove-ItemProperty -Path $k -Name 'ForcePermissionPolicyUnloadDefaultEnabled' -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Application

Google Chrome (Google) — November 2026 templates

Official templates downloaded on November 12, 2026.