Open in the explorer

Enable post-quantum key agreement for TLS (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 120-146, Windows 7 or later
ADMX file
msedge.admx
Internal name
msedge/PostQuantumKeyAgreementEnabled

Explanation

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

This policy configures whether Microsoft Edge offers a post-quantum key agreement algorithm in TLS. This lets supporting servers protect user traffic from being decrypted by quantum computers.

If you enable or don't configure this policy, Microsoft Edge offers a post-quantum key agreement in TLS connections. TLS connections are protected from quantum computers when communicating with compatible servers.

If you disable this policy, Microsoft Edge won't offer a post-quantum key agreement in TLS connections. User traffic is unprotected from decryption by quantum computers.

Offering a post-quantum key agreement is backwards-compatible. Existing TLS servers and networking middleware are expected to ignore the new option and continue selecting previous options.

However, devices that don't implement TLS correctly may malfunction when offered the new option. For example, they might disconnect in response to unrecognized options or the resulting larger messages. These devices aren't post-quantum-ready and will interfere with an enterprise's post-quantum transition. If this issue is encountered, administrators should contact the vendor for a fix.

This policy has been removed starting in Microsoft Edge version 147. Post-quantum key agreement is now enabled by default and cannot be disabled. Enterprises should work with device vendors to obtain fixes for proper post-quantum support.

Registry

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

Disable

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

Revert to "Not configured"

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