I'm having the same issue following installaiton of the update KB5022404 at the beginning of February. It appears to be the norm now that I get literally dozens of Errors and Warnings arising after installing any Windows 11 updates. So much for Microsoft's quality control!
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: Most helpful
-
Anonymous
2023-03-07T10:24:50+00:00 -
Anonymous
2023-03-05T18:24:16+00:00 I'm having the same issue. Exact same error:
LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.
This started about 9 days ago after a Windows 11 update 10.0.22621.
I'm running AMD 5950X CPU with the latest EFI/BIOS from Asus (ROG STRIX X570-F). I'm using MalwareBytes for Antivirus, nothing being reported as a problem.
My applications are VERY slow to open and then sometimes they will not open at all.
At cmd prompt (Run as Admin) the following showed NO issues at all:
sfc /scannow
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
When I run performance testing like Cinebench R23 or 3DMark, my computer performs well and scores well so I know it's not a hardware issue. The issue if specific to Win11 just sometimes not opening applications and doesn't respond to any mouse input.
I've gone thru the process of "safe" mode and enable disable service but that didn't expose any issues either. So whatever this problem is, it's VERY much Windows 11 update. It's sad that Microsoft don't seem to have any methods to diagnose this problem.
I'm considering going back to Windows 10, at least it works for me. Windows 11 has been up and down, very inconsistent updates and Microsoft MIA.
-
Anonymous
2023-02-10T19:46:25+00:00 That error is slightly different as a package. Try the solution here.
If you read that thread, there are actually no working solutions other than to revert to Windows 10.
Reverting to Windows 10 is not a solution, for me.
-
Anonymous
2023-01-21T03:03:38+00:00 Same here. New build as well. It's on the core MSFT security packages too, so this isn't a profile or device issue. I wish they would just ACK it and get it in the bug queue. It's clearly not working as intended. Either those packages aren't properly signed (seems unlikely), or some aspect of credential guard is being reused on Pro to do some subset of what it does on Enterprise and these errors are annoying, but spurious (very likely)
-
Anonymous
2023-01-13T21:49:00+00:00 Im kinda in the same boat. Onedrive was forcing some profile setting with a fresh install every time. shut one drive down and it fixed it for only for a short time. was throwing dcom 10016 error before as well. thats gone and now just the LSA error. Shuts down to straight black screen shortly into a game, with no reboot.