Open in the explorer

Check RSA key usage for server certificates issued by local trust anchors (obsolete)

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Edge WebView2 User Configuration › Policies › Administrative Templates › Microsoft Edge WebView2
Supported on
Microsoft Edge version 123-135, Windows 7 or later
ADMX file
msedgewebview2.admx
Internal name
msedgewebview2/RSAKeyUsageForLocalAnchorsEnabled

Explanation

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

The X.509 key usage extension declares how the key in a certificate can be
used. These instructions ensure certificates aren't used in an unintended
context, which protects against a class of cross-protocol attacks on HTTPS and
other protocols. HTTPS clients must verify that server certificates match the
connection's TLS parameters.

Starting in Microsoft Edge 124, this
check is always enabled.

Microsoft Edge 123 and earlier have the
following behavior:

If this policy is set to enabled,
Microsoft Edge performs this key
check. This helps prevent attacks where an attacker manipulates the browser into
interpreting a key in ways that the certificate owner didn't intend.

If this policy is set to disabled,
Microsoft Edge skips this key check-in
HTTPS connections that negotiate TLS 1.2 and use an RSA certificate that
chains to a local trust anchor. Examples of local trust anchors include
policy-provided or user-installed root certificates. In all other cases, the
check is performed independent of this policy's setting.

If this policy isn't configured,
Microsoft Edge behaves as if the
policy is enabled.

This policy is available for administrators to preview the behavior of a
future release, which will enable this check by default. At that point, this
policy will remain temporarily available for administrators that need more
time to update their certificates to meet the new RSA key usage requirements.

Connections that fail this check will fail with the error
ERR_SSL_KEY_USAGE_INCOMPATIBLE. Sites that fail with this error likely have a
misconfigured certificate. Modern ECDHE_RSA cipher suites use the
"digitalSignature" key usage option, while legacy RSA decryption cipher suites
use the "keyEncipherment" key usage option. If uncertain, administrators should
include both in RSA certificates meant for HTTPS.

The policy has been obsoleted starting from Microsoft Edge version 136,
but the key check has been always enabled since Microsoft Edge version 124.

Registry

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

Disable

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

Revert to "Not configured"

# Revert to "Not configured": msedgewebview2/RSAKeyUsageForLocalAnchorsEnabled
$k = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2'
Remove-ItemProperty -Path $k -Name 'RSAKeyUsageForLocalAnchorsEnabled' -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.