sodcalculator

10 Tech How-To

Fix Local Security Authority Protection Is Off in Windows

Guide 10-53686 · Updated · Step by step

If you see a Windows Security alert saying “Local Security Authority protection is off,” your device may be more vulnerable to credential theft and malware attacks. This guide walks you through the steps to turn LSA protection back on, either through the Windows Security app, the Registry, or Group Policy, and covers what to do if the toggle is grayed out or the setting won’t stick.

What You’ll Need

  • Windows 10 version 1709 or later, or Windows 11 (any recent build)
  • Administrator account access (to change system settings)
  • A backup of your registry (optional but recommended before editing)

Step-by-Step

Method 1: Turn It On via Windows Security (Easiest)

  1. Open the Start menu, type Windows Security, and press Enter.
  2. Select Device security from the left sidebar.
  3. Under Core isolation, click Core isolation details.
  4. Find the toggle labeled Local Security Authority protection.
  5. Toggle it to On. If prompted by User Account Control, click Yes.
  6. Restart your computer when asked to apply the change.

Method 2: Enable via Registry Editor (When the Toggle Is Grayed Out)

  1. Press Win + R, type regedit, and press Enter. Accept the UAC prompt.
  2. Navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Look for a DWORD value named RunAsPPL. If it doesn’t exist, right-click on the right pane, select New → DWORD (32-bit) Value, and name it RunAsPPL.
  4. Double-click RunAsPPL, set the Value data to 1, and click OK.
  5. Close the Registry Editor and restart your PC.

Method 3: Use Group Policy (For Windows Pro or Enterprise)

  1. Press Win + R, type gpedit.msc, and press Enter.
  2. Navigate to Computer Configuration → Administrative Templates → System → Local Security Authority.
  3. Double-click Configure LSA protection.
  4. Select Enabled, then in the drop-down under Options, choose Enabled with UEFI Lock (or just Enabled if UEFI lock isn’t available).
  5. Click OK, then restart your computer.

Common Mistakes

  • Not restarting – LSA protection only takes effect after a full reboot. A shutdown and start is not the same as a restart.
  • Using the wrong registry path – Make sure you’re under Control\Lsa, not Control\Lsa\Credssp or another subkey.
  • Setting the DWORD to 0 – A value of 0 disables the protection. Use 1 (or 2 for UEFI lock).
  • Editing the registry without admin rights – The changes won’t save unless you’re running regedit as administrator.
  • Ignoring driver compatibility – Some older drivers or security software may conflict, causing the setting to revert.

Tips

  • After enabling, check the Windows Security app again to confirm the toggle shows On.
  • If you use the UEFI Lock option, it prevents the setting from being disabled by malware, but it also makes it harder to turn off later – you’ll need to clear the UEFI variable.
  • Keep your Windows updates current. Microsoft occasionally improves LSA protection behavior with patches.
  • If you’re in an enterprise environment, Group Policy is the more reliable method because it’s re-applied on each login.
  • Consider enabling Memory Integrity under Core isolation as well, for an extra layer of defense.

Troubleshooting

The toggle is grayed out or says “This setting is managed by your administrator”

This usually means a Group Policy or registry value is already set. Use Method 2 (registry) to set RunAsPPL to 1, or ask your IT department to apply the policy. If you’re on Windows Home, Group Policy isn’t available, so the registry method is your only option.

The setting turns off after a reboot

This often happens due to a conflicting driver or security software. Check the Event Viewer for LSA errors (look under Windows Logs → System for Event ID 12 or 13 from LsaSrv). If you find a driver causing the issue, update it or remove the conflicting software. Also, ensure your BIOS/UEFI is up to date.

Windows Security shows the error even after enabling

Clear the Windows Security cache by restarting the SecurityCenter service (run services.msc, find Security Center, right-click, and restart). If that doesn’t help, run sfc /scannow in an elevated Command Prompt to repair system files.

You get a “Cannot compute” or error when trying to enable via registry

Make sure you’re not in Safe Mode (some settings are blocked). Also verify you have write permissions to the Lsa key – right-click it, select Permissions, and ensure Administrators have Full Control.

The device doesn’t support LSA protection

LSA protection requires a 64-bit processor and a recent version of Windows. If your hardware is very old, the option may not be available. In that case, focus on other security measures like enabling BitLocker and keeping your antivirus active.

Frequently Asked Questions

What does Local Security Authority protection do?

It prevents untrusted processes from accessing the LSA, which handles user authentication and password verification. This blocks many credential-stealing attacks.

Is it safe to enable LSA protection?

Yes, for the vast majority of users. The only downside is that some older drivers or plugins may stop working, but that’s rare on current systems.

Why does Windows say LSA protection is off even after I turn it on?

It could be due to a pending restart, a conflicting policy, or the setting being reverted by a driver. Follow the troubleshooting steps above to diagnose.

Can I enable LSA protection on Windows 10 Home?

Yes, using the Windows Security toggle or the registry method. Group Policy is not available on Home, but the registry works the same.

What is the difference between RunAsPPL values 1 and 2?

Value 1 enables LSA protection. Value 2 (or 3, depending on build) enables it with UEFI Lock, which prevents the setting from being changed without clearing the UEFI variable. Use 2 if you want extra tamper resistance.

Will enabling LSA protection affect my performance?

No noticeable impact on everyday tasks. The security benefit far outweighs any negligible overhead.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →