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-07-06T11:40:11+00:00

    The Update for Windows Security Platform Antimalware Platform - KB5007651 (Version 1.0.2306.10002) that installed on my computer yesterday, July 5, 2023 appears to have fixed this issue for me. I am "cautiously optimistic" as this issue was resolved back in April but that "fix" did not last very long ... So far so good.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-05-26T23:17:57+00:00

    I followed all the steps but I don't have the RunAsPPL on the right panel. Any idea why is it missing? Thx.

    I have all Dell & MS last updates installed ... but still I cannot turn Memory Integrity On... because of "incompatibilty with your drivers". No list of incompatible drivers is provided.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-05-26T22:38:50+00:00

    I'm trying these steps but why I don't have the RunAsPPL on the right panel?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-05-08T06:09:49+00:00

    In those security settings you can expand for more information and view what drivers are incompatible and force uninstall them with a pnputil command in CMD.

    Make sure these drivers are old or obsolete and not necessary. If these are important drivers there's nothing you can do exept contacting the official manufacturer so they can develop a sollution.

    for instance

    pnputil /delete-driver oem44.inf /uninstall /force

    Was this answer helpful?

    0 comments