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-02-02T15:24:31+00:00

    Yeah, I ultimately had to reinstall windows via the Reset This PC option in bootup recovery mode (at least I could keep my files). Both the Explorer and LSA issues got resolved and haven’t returned, but some time later I got a new “Standard Hardware Security Not Supported” warning in Windows Security, *sigh*. Still working that one out.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-02T13:46:50+00:00

    Did you ever solve this problem?

    I'm in the same boat.

    Group Policy, Registry, DISM, SFC, and restting the security app all failed to solve the problem.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-18T15:17:37+00:00

    Hi again,

    Recently after I shutdown my computer and booting up the next day, the same error returned, alerting me that lsa needs a system restart yet not registering the restart. I found that repeating the in-place repair still resolves the issue temporarily, but later after doing another shutdown, I found that the error returned again on bootup.

    I'm not sure if this is relevant, but between these two instances of finding the lsa error to return some time after temporarily fixing it with an in-place repair, I was prompted at the start menu power options to either restart or shutdown presumably for a recent windows update. However, I repeated a restart twice, but both times similarly failed to register that a restart had occurred, and the little orange dot remained on the restart and shutdown options in the start menu. After I selected the shutdown option instead, the system seemed to register it, and the alerts disappeared (though doing a shutdown instead of a restart for this lsa error has no effect).

    Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-16T04:14:44+00:00

    Cool. The in-place repair fixed it. Thanks for all your help!

    Was this answer helpful?

    0 comments