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

I'm not sure why you would get that on Win 10 unless you turned on core isolation. It's likely a USB device or other boot device/app that isn't compatible with either the OS or drivers. Considering it's Win 10 and probably been at least a couple of years since a clean install, you might consider it. On average, every 2 to 3 years, you should reinstall the OS.

I started in IT in the '90s with Windows 3.1 and 95 and can tell you that without a doubt, they will continue to do the same thing they have always done. Code over the top of the errors found by its uses, patch any newfound exploits, and create bloatware that eventually can't run simple programs requiring a new OS version.

Genuinely interested, why would any business ever start to even imagine that an individual would willingly re-install their OS every 2-3 years

I can tell you why: because it saves time compared to actually debugging things, finding and fixing root cause (or filing a bug report for it, if it can't be fixed directly). Or rather people believe it saves time, but I doubt there is real research that would prove (or debunk) this.

Personally, I've got my first job 15 years ago after I answered a question "What will you do if a Windows PC is in cyclic boot?". My answer had a couple of steps and only the very last one, last resort, was WinXP reinstallation. Other 7 people who were interviewed that day went for reinstallation right away. At least that's what interviewer told me.

I can somewhat agree, that with WinXP that probably was a good idea, at least if you had frequent applications installs and removals. But since Win7 it is rarely a real need. It may be a good idea if your are transferring your system drive to a significantly different hardware, but even then it's not really required with how drivers are managed nowadays: it will be enough to remove old devices and uninstall unused software.

I started face with this issue after recent Microsoft updates. On my Asus Rog Laptop with Windows 11, it usually restarts due LSP not signed issue after Windows Installer reconfigures Microsoft Game Input even though i disabled or delete any related services, files or stop any tasks. I've done quite many steps here and there through registery, command and configuration. After spending tremendous amount of attempts until Microsoft finds a solution i found this solution works for me;

Unplug the power cable and run the laptop on battery. ( Strange, isn't it ? )

Hope that is works for anyone out there having the issue. It is a real bugger.