False error on Local Security Authority Protection [Windows 11]

By kiddingguy
in Microsoft (Windows)

 Share

Recommended Posts

Grand Master

kiddingguy

Posted
Posted

My Windows 11 Security states that there are errors on my Local Security Authority Protection.

The info that is given is that no TPM it there. Yet, there is.

image.png.7977590e99989ac5b1985d783f5f1b8e.png

 

I also got this message on other (Intel) computer, and after checking and double-checking I decided to Dismiss this error.

Is this a (known) bug on Windows 11, 22H2 with all latest updates installed?

image.png

image.png

  • kiddingguy changed the title to False error on Local Security Authority Protection [Windows 11]
Grand Master

spaceelf

Posted
Posted
On 04/05/2023 at 07:11, Ixion said:

Yup, it's a known bug and there have been several Neowin articles about it. I thought that a fix had been released but it may be limited to release preview or beta builds for the moment.

Fairly sure it's unfixed in Beta.

Grand Master

Brandon H Supervisor

Posted
  • Supervisor
Posted
On 04/05/2023 at 07:11, Ixion said:

Yup, it's a known bug and there have been several Neowin articles about it. I thought that a fix had been released but it may be limited to release preview or beta builds for the moment.

they did release a fix, but that fix recently broke again from what I heard :D 

Grand Master

kiddingguy

Posted
  • Author
Posted
On 07/05/2023 at 21:10, skinnyJM said:

Yes, it's back, returned to both of my (officially supported) W11 machines yesterday, but not the unofficially supported one. So I'm not sure what's going on there...

I guess it's the Microsoft way of "fixing".

1. It works
2. Let's break it with an update
3. Let's fix it
4. Let's break it again
5. Let's fix it with another update

(repeat steps 4 & 5 indefinitely) 

Grand Master

+Elі Subscriber²

Posted
  • Subscriber²
Posted

I think the OP is experiencing two different bugs here. The article that is posted here in Neowin relates to the error with the Local Security Authority Protection bein off. ( I even experienced that myself, but it was fixed in one of my PCs, yet not in the other). Yet the OP is seeing an error related to no TPM module detected as well.

OP might want to refresh his Windows TPM settings.  Here's how.

Additionally you might want to make sure Secure Boot is enabled on your BIOS / UEFI.

Because I have Linux also installed in dual boot and have disabled Secure Boot at times, I have then experienced that TPM error on Windows 11.

Grand Master

kiddingguy

Posted
  • Author
Posted
On 08/05/2023 at 19:01, Elі said:

I think the OP is experiencing two different bugs here. The article that is posted here in Neowin relates to the error with the Local Security Authority Protection bein off. ( I even experienced that myself, but it was fixed in one of my PCs, yet not in the other). Yet the OP is seeing an error related to no TPM module detected as well.

OP might want to refresh his Windows TPM settings.  Here's how.

Additionally you might want to make sure Secure Boot is enabled on your BIOS / UEFI.

Because I have Linux also installed in dual boot and have disabled Secure Boot at times, I have then experienced that TPM error on Windows 11.

TPM is on.

It's the message in Windows Security that tells me it's off [not true]. And the bug came back.

Grand Master

adrynalyne

Posted
Posted (edited)
On 09/05/2023 at 16:29, skinnyJM said:

I'm seeing the same exact screens, preceded by:

image.jpeg.07c63e792865f014de9a89108e499378.jpeg

Yes, MS doing what they do best. They break something, fix it, and then break it again later.

 

But with MS being a small indie developer, its to be expected. /s

Grand Master

kiddingguy

Posted
  • Author
Posted

See frontpage news:   Microsoft admits it couldn't really fix Windows 11 Security and Defender LSA issues :D

And my question: Is disabling kernel mode better than just click “ Dismiss” and not be bothered by this message?
For security-sake I mean...

Community Regular

Ixion

Posted
Posted

The issue for some people appears to be that it's causing a BSOD rather than just an annoying message so disabling Kernal mose is a sensible setp. Personally I use my machine primarily for gaming and most of the virtualisation based security (kernel mode isolation, memory integrity etc) causes a loss of performance for what at best is a negligable gain in security on a system not containing sensitive information so I've disabled all such features. On my work machine/networks I administer they're all turned on!

  • 3 weeks later...
Grand Master

kiddingguy

Posted
  • Author
Posted

Even with the Moment 3 update and all, it's still not fixed.

Wake up Microsoft!? Or does this have more impact than expected on how Windows and its security management/Windows Security behaves in W11?
Or maybe with next week's Patch Tuesday it'll be fixed?

  • hellowalkman and skinnyJM
  • Like 1
  • Sad 1
Rising Star

skinnyJM

Posted
Posted
On 05/06/2023 at 10:28, kiddingguy said:

Even with the Moment 3 update and all, it's still not fixed.

Wake up Microsoft!? Or does this have more impact than expected on how Windows and its security management/Windows Security behaves in W11?
Or maybe with next week's Patch Tuesday it'll be fixed?

Maybe they really do fix things based on throwing darts while wearing a blindfold???😵

  • 1 month later...
Grand Master

kiddingguy

Posted
  • Author
Posted
On 06/07/2023 at 10:31, hellowalkman said:

okay so MS says it is fixed now https://www.neowin.net/news/microsoft-finally-manages-to-fix-windows-11-defender-local-security-authority-protection-off/

@kiddingguywhat do you think?

It looks like it's solved. I think from server-side, because I haven't installed the Patch Tuesday updates not yet [doing it now].

Grand Master

adrynalyne

Posted
Posted
On 06/07/2023 at 08:21, kiddingguy said:

It looks like it's solved. I think from server-side, because I haven't installed the Patch Tuesday updates not yet [doing it now].

It would have come in as a Defender update, not a patch Tuesday update.

Grand Master

kiddingguy

Posted
  • Author
Posted
On 06/07/2023 at 19:51, adrynalyne said:

It would have come in as a Defender update, not a patch Tuesday update.

OK. Anyways, seems like it's solved. For now 🤞

  • hellowalkman and goretsky
  • Like 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.