Open in the explorer

WDigest Authentication (disabling may require KB2871997)

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › MS Security Guide
Supported on
At least Windows Server 2008 R2 or Windows 7
ADMX file
SecGuide.admx
Internal name
SecGuide/Pol_SecGuide_0202_WDigestAuthn

Explanation

When WDigest authentication is enabled, Lsass.exe retains a copy of the user's plaintext password in memory, where it can be at risk of theft. Microsoft recommends disabling WDigest authentication unless it is needed.

If this setting is not configured, WDigest authentication is disabled in Windows 8.1 and in Windows Server 2012 R2; it is enabled by default in earlier versions of Windows and Windows Server.

Update KB2871997 must first be installed to disable WDigest authentication using this setting in Windows 7, Windows 8, Windows Server 2008 R2 and Windows Server 2012.

Enabled: Enables WDigest authentication.

Disabled (recommended): Disables WDigest authentication. For this setting to work on Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012, KB2871997 must first be installed.

For more information, see http://support.microsoft.com/kb/2871997 and http://blogs.technet.com/b/srd/archive/2014/06/05/an-overview-of-kb2871997.aspx .

Use cases

Controls WDigest's UseLogonCredential value: when it is 1, Windows keeps signed-in users' clear-text passwords in memory, which tools such as Mimikatz exploit. Disabling it (value 0) is a baseline security recommendation.

On recent Windows versions WDigest is already off by default; the setting mainly serves to guarantee it across the fleet, notably older systems that need the KB2871997 update.

Microsoft source: The Importance of KB2871997 and KB2928120 for Credential Protection

Registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest
Value name
UseLogonCredential
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.

Enable

# Enable: SecGuide/Pol_SecGuide_0202_WDigestAuthn
$k = 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'UseLogonCredential' -Value 1 -Type DWord

Disable

# Disable: SecGuide/Pol_SecGuide_0202_WDigestAuthn
$k = 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'UseLogonCredential' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": SecGuide/Pol_SecGuide_0202_WDigestAuthn
$k = 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest'
Remove-ItemProperty -Path $k -Name 'UseLogonCredential' -ErrorAction SilentlyContinue

Application

Microsoft Security Baseline (MSS, SecGuide) (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.