The Local Security Authority protection is off - Windows 11 Home

Anonymous
2023-03-17T06:10:20+00:00

A yellow triangle appeared on the Windows Security iron yesterday. It says that Local Security Authority protection is off. Your device may be vulnerable.

I can press Go to settings or Dismiss but when I click go to settings, a notification saying "the page You want to access doesn't contain required functions and is unavailable". 

There is also no option to turn the protection on in the Device Security panel (there is only "dismiss" option).

When I was looking at it yesterday, there was also a notification that "The tpm module is unavailable" but today it doesn't show. I checked the device manager and uefi and both say that the tpm is enabled.

I've found an advice to turn on SMV in UEFI (in the CPU settings) to solve the problem but I don't want to change anything in BIOS without consultation as I'm no expert. I've also found a reply from a truste source that this whole problem is a Microsoft bug and it's better to just wait till they fix it.

What should I do?

Screenshots are in Polish, I hope they can be useful somehow. The first one shows the notification about a page being not available and the second shows the Device security panel (the notification from the first screenshot displays when I close the device security page or when I click on "go to settings" below the information that the protection is turned off). There is also an information (second screenshot) that "standard device security is not supported".

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-07-06T07:36:56+00:00

Microsoft have just posted that they have resolved the "Local Security Authority protection is off" issue in an update. Has anyone tried to apply it from Windows Update?

Resolution: This issue was resolved in an update for Windows Security platform antimalware platform KB5007651 (Version 1.0.2306.10002). If you would like to install the update before it is installed automatically, you will need to check for updates.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

174 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-05-17T10:46:20+00:00

    Hello,

    If I understood correctly then, they do not recommend doing this procedure:

    1. Open Windows Registry Editor.
    2. Navigate to the following location: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    3. Make sure you have RunAsPPL and RunAsPPLBoot. entries. If you don’t have RunAsPPLBoot listed, create DWORD entries for RunAsPPL and RunAsPPLBoot.
    4. Value for both entries should be 2.
    5. Reboot and warnings should stop.

    Now we are still in the most total vagueness: is it better to do nothing and ignore the warnings? Is it better to create these RunAsPPL and RunAsPPLBoot registry entries, or does this manipulation only turn off the Windows Security warning without further protecting our PCs? I haven't seen any article certifying something about this problem one way or the other, a little annoying

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-05-17T10:57:21+00:00

    Microsoft still says that this has been fixed

    They have marked it as "mitigated", by advising users to dismiss the warnings. If and when they finally fix it properly, the status should move to "resolved".

    Yes but that being said, currently in the core isolation settings there is no slider switch button currently, to turn it off and on in the first place , hoping also that it doesn't allow viruses to slip through the net, and Malware also .

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-05-18T08:22:59+00:00

    If I understood correctly then, they do not recommend doing this procedure:

    1. Open Windows Registry Editor.
    2. Navigate to the following location: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    3. Make sure you have RunAsPPL and RunAsPPLBoot. entries. If you don’t have RunAsPPLBoot listed, create DWORD entries for RunAsPPL and RunAsPPLBoot.

    Microsoft have explicitly told people not to apply any workarounds other than clicking dismiss.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-05-18T09:22:51+00:00

    Hello Cory Royce,

    You sayd " Microsoft have explicitly told people not to apply any workarounds other than clicking dismiss " ,

    and that's what Microsoft advises and there are supporters in favor of this attitude, but there are other specialists who recommend to create these 2 registry values RunAsPPL and RunAsPPLBoot in D Word 32 bits by giving them a value of 2 and who say that if you don't, there is no kernel protection.

    No one can affirm or prove 100% what is best in terms of security, so we are all in a dark smoke.

    Was this answer helpful?

    0 comments