en-US windows computer

Configure validation of ROCA-vulnerable WHfB keys during authentication

Verified with Windows 11 25H2 — updated on July 30, 2026

Windows 11 25H2

Supported on: At least Windows Vista

Path in the GPO console

Computer Configuration\Administrative Templates\System\Security Account Manager

Description

This policy setting allows you to configure how domain controllers handle Windows Hello for Business (WHfB) keys that are vulnerable to the "Return of Coppersmith's attack" (ROCA) vulnerability. For more information on the ROCA vulnerability, please see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15361 https://en.wikipedia.org/wiki/ROCA_vulnerability If you enable this policy setting the following options are supported: Ignore: during authentication the domain controller will not probe any WHfB keys for the ROCA vulnerability. Audit: during authentication the domain controller will emit audit events for WHfB keys that are subject to the ROCA vulnerability (authentications will still succeed). Block: during authentication the domain controller will block the use of WHfB keys that are subject to the ROCA vulnerability (authentications will fail). This setting only takes effect on domain controllers. If not configured, domain controllers will default to using their local configuration. The default local configuration is Audit. A reboot is not required for changes to this setting to take effect. Note: to avoid unexpected disruptions this setting should not be set to Block until appropriate mitigations have been performed, for example patching of vulnerable TPMs. More information is available at https://go.microsoft.com/fwlink/?linkid=2116430.

Registry

HKLM Software\Microsoft\Windows\CurrentVersion\Policies\System\SAM

More options available

Options

Options for handling ROCA-vulnerable WHfB keys:
SamNGCKeyROCAValidation enum
  • Ignore ROCA-vulnerable WHfB keys -> 0
  • Audit ROCA-vulnerable WHfB keys on use -> 1
  • Block ROCA-vulnerable WHfB keys on use -> 2 (default)

MDM / Intune (CSP)

./Device/Vendor/MSFT/Policy/Config/ADMX_sam/SamNGCKeyROCAValidation
Device Since Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later | Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later | Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later | Windows 11, version 21H2 [10.0.22000] and later Official mapping (Microsoft Learn)

Microsoft Learn documentation Mapping data: Microsoft Learn (CC BY 4.0)

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO.

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Configure validation of ROCA-vulnerable WHfB keys during authentication
; State: Enabled
; Supported on: At least Windows Vista

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\SAM]
"SamNGCKeyROCAValidation"=dword:00000002
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Configure validation of ROCA-vulnerable WHfB keys during authentication
# State: Enabled
# Supported on: At least Windows Vista

$path = 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System\SAM'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'SamNGCKeyROCAValidation' -Value 2 -Type DWord

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview