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 No comments
{count} votes
Answer accepted by question author
  1. 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

    19 people found this answer helpful.
    0 comments No comments

138 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-02-23T16:26:44+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

    It works! Thank you so much for your help!

    0 comments No comments
  2. Anonymous
    2023-02-23T16:36:42+00:00

    I have the same problem, it keep asking restart.......... but restart won't help

    reset security, registry edit can't fix as well.......

    0 comments No comments
  3. Anonymous
    2023-02-23T16:43:14+00:00

    Thanks man!!!!!!!!!! You better than Microsoft Staff!!!!!!!!

    How you can fingure out RunAsPPLBoot <-- this is missing in registry??

    I have the same issue, add it back and change it to 2, problem solved

    thank you very much indeed! :D

    0 comments No comments
  4. Anonymous
    2023-02-23T18:26:37+00:00

    Did you try reset app?

    Did you try enable policy?

    Check if the other reg entry has 0,1 ou 2 value.

    Hope it helps.

    0 comments No comments