Enable leak detection for entered credentials
Explanation
Setting the policy to Enabled lets users have Google Chrome check whether usernames and passwords entered were part of a leak.
Setting the policy to Disabled does not let users have this functionality.
If the policy is set, users can't change it in Google Chrome. If not set, credential leak checking is allowed, but the user can turn it off.
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Google\ChromeHKEY_CURRENT_USER\Software\Policies\Google\Chrome- Value name
PasswordLeakDetectionEnabled
| State | Value written |
|---|---|
| Enabled | REG_DWORD = 1 |
| Disabled | REG_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/PasswordLeakDetectionEnabled
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'PasswordLeakDetectionEnabled' -Value 1 -Type DWordDisable
# Disable: chrome/PasswordLeakDetectionEnabled
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'PasswordLeakDetectionEnabled' -Value 0 -Type DWordRevert to "Not configured"
# Revert to "Not configured": chrome/PasswordLeakDetectionEnabled
$k = 'HKLM:\Software\Policies\Google\Chrome'
Remove-ItemProperty -Path $k -Name 'PasswordLeakDetectionEnabled' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Application
Google Chrome (Google) — November 2026 templates
Official templates downloaded on November 12, 2026.