Open in the explorer

Determines whether the built-in certificate verifier will enforce constraints encoded into trust anchors loaded from the platform trust store (obsolete)

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Edge User Configuration › Policies › Administrative Templates › Microsoft Edge
Supported on
Microsoft Edge version 113-127, Windows 7 or later
ADMX file
msedge.admx
Internal name
msedge/EnforceLocalAnchorConstraintsEnabled

Explanation

OBSOLETE: This policy is obsolete and doesn't work after Microsoft Edge 127.

X.509 certificates might encode constraints, such as Name Constraints, in extensions in the certificate. RFC 5280 specifies that enforcing such constraints on trust anchor certificates is optional.

From Microsoft Edge 112, such constraints in certificates loaded from the platform certificate store will now be enforced.

This policy exists as a temporary opt-out in case an enterprise encounters issues with the constraints encoded in their private roots. In that case this policy may be used to temporarily disable enforcement of the constraints while correcting the certificate issues.

If you enable this policy or don't configure it, Microsoft Edge enforces constraints encoded into trust anchors loaded from the platform trust store.

If you disable this policy, Microsoft Edge won't enforce constraints encoded into trust anchors loaded from the platform trust store.

This policy has no effect if the 'MicrosoftRootStoreEnabled' (Determines whether the Microsoft Root Store and built-in certificate verifier will be used to verify server certificates) policy is disabled.

This policy was removed in Microsoft Edge version 128. Starting with that version, constraints in trust anchors are always enforced.

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge
Value name
EnforceLocalAnchorConstraintsEnabled
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: msedge/EnforceLocalAnchorConstraintsEnabled
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'EnforceLocalAnchorConstraintsEnabled' -Value 1 -Type DWord

Disable

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

Revert to "Not configured"

# Revert to "Not configured": msedge/EnforceLocalAnchorConstraintsEnabled
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
Remove-ItemProperty -Path $k -Name 'EnforceLocalAnchorConstraintsEnabled' -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Application

Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.