Default JavaScript setting
Explanation
Setting the policy to 1 lets websites run JavaScript. Setting the policy to 2 denies JavaScript.
Leaving it unset allows JavaScript, but users can change this setting.
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Google\ChromeHKEY_CURRENT_USER\Software\Policies\Google\Chrome- 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.
Computer (HKLM)
Enable
# Enable: chrome/DefaultJavaScriptSetting
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Default JavaScript setting
# Possible options:
# Allow all sites to run JavaScript = 1
# Do not allow any site to run JavaScript = 2
Set-ItemProperty -Path $k -Name 'DefaultJavaScriptSetting' -Value 1 -Type DWordDisable
# Disable: chrome/DefaultJavaScriptSetting
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": chrome/DefaultJavaScriptSetting
$k = 'HKLM:\Software\Policies\Google\Chrome'
Remove-ItemProperty -Path $k -Name 'DefaultJavaScriptSetting' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Default JavaScript settingDefaultJavaScriptSetting | Drop-down listenum | DefaultJavaScriptSetting | REG_DWORD |
|
Application
Google Chrome (Google) — November 2026 templates
Official templates downloaded on November 12, 2026.