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. Enric Cortés 39,445 Reputation points Volunteer Moderator
    2023-03-16T13:13:56+00:00

    "...Standard hardware security not supported..."

    To fix this issue apply the solution I posted on page 4 of this thread.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-16T13:38:41+00:00

    To create a new DWORD32 and set it to 2, follow these steps:

    1. Press the Windows key + R to open the Run dialog box.
    2. Type "regedit" and press Enter.
    3. Navigate to the following registry key:
    4. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\
    5. Right-click on an empty space in the right pane, select New and then DWORD (32-bit) Value.
    6. Name the new value "RunAsPPLBoot" (without the quotes).
    7. Double-click on the newly created "RunAsPPLBoot" registry value.
    8. Change the value data to "2" (without the quotes).
    9. Click OK to save the changes. Close the Registry Editor.
    10. Restart your computer for the changes to take effect.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-16T16:17:53+00:00

    hi

    Virus scan was all clear so tried providing missing reg entry RunAsPPLBoot.

    Created a new DWORD32 and set to 2.

    Rebooted and fixed. Windows 11 pro, 22H2.

    This appears to have come on after KB5023706 installed.

    Thanks to all in the posts for LSAP.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-16T20:04:27+00:00

    this one helps me

    Was this answer helpful?

    0 comments