How to fix LSA package is not signed as expected event log entries?

It continually amazes me how Microsoft uses its customers to find all the poor programming and lack of quality control in its products. Have Windows 10.0.22621 Build 22621 and the issue is happening in tspkg, wdigest, msv1_0,sfapm,schanel,cloudap and many other packages.

LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard. Event IDs 6155,6156 depending but the screenshot looks the same as above....event log littered.

Why does my event log get filled each and every day with this stupidity? What is Microsoft going to do to stop torturing its paying customers with this crappy programming, crappy QA, crappy code?

Peace

If you are seeing LSA errors for packages negoexts, kerberos, msv1_0, tspkg, pku2u, cloudap, wdigest, schannel, sfapm - it looks like you can ignore those, because they are related to password-based SSO, according to this. These specific warnings (they are not errors in the event viewer!) only indicate that something tried loading one of the affected protocols or it was just the general attempt to load the library. According to MS article, this only blocks SSO, not the whole protocols.

It is clear, that for these particular instances it would warrant Microsoft to write a more appropriate warning text, perhaps also indicating what was calling the library or whether it was a general load of the library during boot-up sequence.

I have not found a way to learn what is actually triggering these libraries/protocols, and what can be done to disable them, if that is safe enough for a particular system (because if they are in use, disabling them may affect other apps).

So I have seen this issue with 22H2 on only some machines. This can also affect Remote Desktop login. Here is the answer:

First it is a credential guard problem. Then it is a problem because I thought credential guard was only available on Enterprise Edition of Windows 11. We are running Pro. But if I look under Settings and Core Isolation it says credential guard is active. Which is probably the REAL problem. It shouldn't be active on these machines. We are running Pro.

If your problem is Remote Desktop login or this message then the answer is to turn off credential guard (group policy or the registry on that system Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa then LsaCfgFlagsDefault to 0) or if it is already set to 0 just have that user delete the "saved credentials" from the Credential Manager in control panel for Remote Desktop and NOT USE THAT FEATURE. They need to log in every time they connect.

If it is happening on your internal network...wait to see if it is a problem. If the user can log in and connect to resources then leave it alone. At some point maybe microsoft can fix this. So ignore these errors.

If your version of 11 is anything other than Enterprise...you can have this issue.