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-17T10:52:34+00:00

    I couldn't agree with you more! I want an OS. I don't want all of the **** that comes with Windows! And you can't even opt out or uninstall! Windows = Bloatware.

    Yes, the average user shouldn't even have to know what the Registry is. Most of the problems that I have to solve are usually of a PEBKAC nature, and Microsoft fosters this environment by forcing a user to fix a problem that shouldn't even exist.

    Another interesting thing that I saw that is related to this issue is in "Device security**."** I use the best components that are available and assemble with security in mind. Normally after setup "Your device meets the requirements for enhanced hardware security" will be displayed under "Device security" however after this issue arose, I'm now seeing "Standard hardware security not supported." I'm now trying to figure that one out. I sure wish there were other options available.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-03-17T10:01:39+00:00

    hello, i am Andre a windows user

    i have the same problem

    i got this problem after i update my windows yesterday

    this is probably because of that update

    Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.385.223.0)

    sorry for my bad english

    it also might this one here as well

    March 14, 2023—KB5023706 (OS Build 22621.1413)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-03-17T05:08:32+00:00

    I am having the issue on my end too

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-03-17T04:57:47+00:00

    You shouldn't have to do any of this. They should be releasing proper updates. Period. Regardless if this is a temp fix or not. It's counterintuitive for them to continue doing this type of junk to people when they knowingly are getting verifiable reports from a multitude of diff users using a multitude of diff specs & YET ALL GETTING THE SAME ISSUE.

    This is a THEM issue, not a US issue. PERIOD FULL STOP. They have time to bog down people's machines with unnecessary junk. Some of which you can't even Opt out of OR Uninstall & yet what you need to work they don't take the time to put compatible things out constantly. It's beyond annoying and counterintuitive. The average user should not be having to go into a registry for nothing & prob won't even know to look somewhere like this to fix their errors but they all paid to have their devices as well. Don't have to accept shoddy workmanship. Sure apply the fix & still report the issue as unfixed because it's unfixed if you're having to apply a fix. Period.

    Was this answer helpful?

    0 comments