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-17T03:24:46+00:00

    That was great! Clear and concise! Thank you...I had tried all of the other suggestions but nothing worked!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-17T03:01:27+00:00

    hello, i am Andre a windows user

    i have the same problem

    i got this problem after i update my windows yesterday

    this is probably because of that update

    Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.385.223.0)

    sorry for my bad english

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-17T00:04:27+00:00

    No, they likely won't. You should mark other user comments as useful you find useful & then consider rating them five stars while doing the polar opp with the bad suggestions so the right Tech people see this forum. I just encountered this error today, on a PC that's less than 6 months old I believe. So fairly new dated hardware & programming overall. This is a dumb issue that they need to attempt to recreate on their end & implement a fix that users can download & install.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-17T00:02:30+00:00

    We shouldn't "need" to do jack all. THEY should release compatible updates with this stuff so these additional features or bug errors don't constantly occur requiring additional measures by Customers/Users. It's redundant.

    Was this answer helpful?

    0 comments