Running into the exact same problem as you. Not only on my gaming machine, but the secondary work machine which I just built 3 days ago. My primary work machine which uses a FOB for logging in, isn't showing these issues. So simply, whether or not it's useful to anybody, even with a brand-new build, with only baseline drivers, with only windows running. I'm also swarmed with these errors. They broke "something" and it looks like they don't know what that "something" is.
How to fix LSA package is not signed as expected event log entries?
The home (non-work) desktop was upgraded yesterday to Windows 11 Pro 22H2 and afterwards on every boot there are several errors about LSA package is not signed as expected. How do I fix these errors? The desktop has Secure boot enabled with virtual based security enabled for memory protection. The CPU is an Intel i7 8700K, which meets Microsoft's requirements for Windows 11.
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.
85 answers
Sort by: Newest
-
Anonymous
2022-10-19T09:02:05+00:00 -
Anonymous
2022-10-19T00:10:03+00:00 Please note: it is entirely probable the gap in days between 10/5 and 10/11 of my original post is because I had not done a reboot (I tend to logout and put the machine to sleep)
I wasn't keeping track as close as I should've -
Anonymous
2022-10-17T21:05:53+00:00 I use a pin on this machine (changed it), and the MS Authenticator for the account (the account is a "Passwordless account")
I have no local users on this machine
These events occur only after a reboot
-
Anonymous
2022-10-17T16:36:13+00:00 If you're still having issues try changing your account password, if you have local admin enabled that would be the one to change.
Did you also have a local account or just the Microsoft one?