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-18T10:47:46+00:00

    I'm wondering the same thing. Yes, it got rid of the error, but now all of the items in the Windows Security app show 'unknown'. LOL Not good, in my opinion. I'll continue researching.

    Indeed, bump this statement. I have no idea what these registry edits are going to do. Something is fishy here. All of the accounts that say its helpful recently only have been members since February this year. I dont think so it all goes back to one source and same thing. FISHY!

    All I did was update the Local Group Policy and did the Registry bit and it resolved the issue for me and the error / warning has now gone and it now displaying as it did before this issue started as you can see below.

    ![](https://learn-attachment.microsoft.com/api/attachments/79ac0b6d-ec4e-4c24-817b-4d2d9e9471ef?platform=QnA

    As you can see its now working fine for me.

    Oh and I have been a member a lot longer than February.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-18T03:21:46+00:00

    I'm wondering the same thing. Yes, it got rid of the error, but now all of the items in the Windows Security app show 'unknown'. LOL Not good, in my opinion. I'll continue researching.

    Indeed, bump this statement. I have no idea what these registry edits are going to do. Something is fishy here. All of the accounts that say its helpful recently only have been members since February this year. I dont think so it all goes back to one source and same thing. FISHY!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-18T01:06:34+00:00

    I'm having this issue too. Did you ever figure it out?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-17T22:45:24+00:00

    I agree!

    Was this answer helpful?

    0 comments