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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-03-18T19:23:37+00:00

    Hi,

    I had this issue recently, this is how I fixed it,

    • Using RegEdit I went to this path: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    • I set RunAsPPL entry as 2 (Hex),
    • I also created a new entry named RunAsPPLBoot and set it as 2 (Hex) as well,
    • Finally, I restarted the laptop and now it's working.

    Hope this helps!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-18T16:25:37+00:00

    Still not solved. I have genuine key.

    this have nothing to do with genuine key or any types of key

    and no it's still not solved

    we have to wait for a proper update from windows

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-18T15:46:45+00:00

    Still not solved. I have genuine key.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-18T13:42:29+00:00

    I am now having this very same issue ... running Windows 11 Home 22H2 that was installed on January 22, 2023. I first noticed this on Thursday morning (March 16th) when I started up my desktop. I note that I did receive a few Windows updates the previous day ... I am not very technical and don't know a whole lot about computers except that I always do my "due diligence" in making sure that the Windows Security seems to be running properly each and every time I turn on this desktop. So, I am not comfortable in attempting any of these recommended fixes in fear that I may mess something up irreparably but, if I understand the previous posts here correctly then this continued warning message is not a real threat, it is a Microsoft problem and Microsoft should be sending a “fix” to correct this at some point? I thought I had read in an earlier post that someone had chatted with MS Support and were told this issue would disappear by the second or third Friday in March?

    Was this answer helpful?

    0 comments