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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-03-02T17:50:42+00:00

    So, we are all in agreement here, that this is a bug in Windows, and as such, Microsoft should eventually be fixing it (if we don't want to do anything now, like registry edits, etc.)......Is that correct?

    Thanks!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-02T18:08:54+00:00

    brianchris,

    yes, your understanding is correct according to what Microsoft Support told me in a webchat.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-03T03:22:36+00:00

    Solution worked for me. Thanks!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-03T23:55:05+00:00

    Look, do you really think that a gazillion users can begin to figure out how to do this gibberish from what you wrote? Instructions like this do not help most folks at all.

    Was this answer helpful?

    0 comments