Apply UAC restrictions to local accounts on network logons
Explanation
This setting controls whether local accounts can be used for remote administration via network logon (e.g., NET USE, connecting to C$, etc.). Local accounts are at high risk for credential theft when the same account and password is configured on multiple systems. Enabling this policy significantly reduces that risk.
Enabled (recommended): Applies UAC token-filtering to local accounts on network logons. Membership in powerful group such as Administrators is disabled and powerful privileges are removed from the resulting access token. This configures the LocalAccountTokenFilterPolicy registry value to 0. This is the default behavior for Windows.
Disabled: Allows local accounts to have full administrative rights when authenticating via network logon, by configuring the LocalAccountTokenFilterPolicy registry value to 1.
For more information about local accounts and credential theft, see "Mitigating Pass-the-Hash (PtH) Attacks and Other Credential Theft Techniques": http://www.microsoft.com/en-us/download/details.aspx?id=36036.
For more information about LocalAccountTokenFilterPolicy, see http://support.microsoft.com/kb/951016.
Use cases
Applies UAC token filtering to local accounts logging on over the network (NET USE, C$ access): Administrators membership is disabled and powerful privileges are stripped from the resulting token. This limits lateral movement and credential theft when the same local account and password exist on several machines.
When enabled, the policy keeps Windows’ default behaviour (LocalAccountTokenFilterPolicy at 0). Disabling it (value 1) gives remote local administrators a full token, which removes a layer of protection; domain accounts are unaffected, as they already receive a full token on the remote machine.
Microsoft source: User Account Control and remote restrictions
Registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System- Value name
LocalAccountTokenFilterPolicy
| State | Value written |
|---|---|
| Enabled | REG_DWORD = 0 |
| Disabled | REG_DWORD = 1 |
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_0201_LATFP
$k = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'LocalAccountTokenFilterPolicy' -Value 0 -Type DWordDisable
# Disable: SecGuide/Pol_SecGuide_0201_LATFP
$k = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'LocalAccountTokenFilterPolicy' -Value 1 -Type DWordRevert to "Not configured"
# Revert to "Not configured": SecGuide/Pol_SecGuide_0201_LATFP
$k = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System'
Remove-ItemProperty -Path $k -Name 'LocalAccountTokenFilterPolicy' -ErrorAction SilentlyContinueApplication
Microsoft Security Baseline (MSS, SecGuide) (Microsoft) — November 2026 templates
Official templates downloaded on November 12, 2026.