Windows Security Bug - Local Security Authority Protection Not Registering a System Restart

Anonymous
2023-01-15T20:14:29+00:00

After I uninstalled Avira Antimalware, I got an alert from Windows Security that my Local Security Authority Protection was turned off. But after I turned it on and restarted as instructed, I continue to get the same alert that my Local Security Authority Protection is turned off, even though within the same window, the toggle switch under the "Local Security Authority Protection" heading displays that it's already turned on.

Additionally, at the same time that this bug appeared, I've also started to get an old Windows bug where if I try to open File Explorer from the taskbar, the entire taskbar would crash and restart every time (though I can open File Explorer from the Start menu without issue).

Any help resolving either bug would be appreciated. Thanks.

Windows for home | Windows 11 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2023-02-23T14:51:38+00:00

I figure that is a missing reg entry RunAsPPLBoot in my case.

Create a new DWORD32 and set to 2

After reboot no longer get error.

RunAsPPL and RunAsPPLBoot.

By default they are set to 0 to enable this you need to set them to 2.

Also set group policy as enable for uefi lock only , my problem is fixed now, no need to reset windows.

In the Local Group Policy Editor window, navigate to the following path: Computer Configuration\Administrative Templates\System\Local Security Authority.

In the right panel, double-click on the ‘Configure LSASS to run as a protected process‘ policy.

In the policy settings window, select the Enabled option

Then click on the dropdown under Configure LSA to run as a protected process and select Enabled with UEFI Lock

Was this answer helpful?

10+ people found this answer helpful.
0 comments

138 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-03-16T12:25:31+00:00

    does this answer solve the problems.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-16T12:01:41+00:00

    Thank you, Fatih ILKAN!

    Up until now there were no issues with this system that is running Windows Pro 22H2, then after the latest update (KB5022913) this became a problem. The update states that it "addresses an issue that affects the Local Security Authority Subsystem Service (LSASS)." This patch had a negative effect on the Local Security Authority protection. Your suggestions resolved Microsoft's attempt at re-inventing the wheel.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-16T09:55:23+00:00

    This is an odd one. I didn't have this issue until I noticed it today. There was an update yesterday and I noticed that the LSA is turned off (no idea why) so I've enabled it, rebooted the laptop and it is doing this, but I am up-to-date with all the updates.

    Has the bug come back?

    UPDATE - I did the fix and added the entry and set both values to 1 and it now shows Standard hardware security not supported.

    Further update - Local Security Authority protection is on.

    I've got a Lenovo Legion 5 laptop and am on Windows 11 version 21H2.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-16T08:59:04+00:00

    Problem solved, thank you!

    Was this answer helpful?

    0 comments