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

My apologies, the LSA errors in question are to do with Credential Guard (read the errors they state that)

I actually meant Credential Guard is part of Enterprise and Education Editions.

However, it doesn't change the fact that those errors have been there since 22H2 was released and are shown on fresh installs as well. This is because all the editions share the same unified base image.

So, you either

A) wait for Mickeysoft to fix the errors/warnings though current track record with this is probably RIGHT before Windows 12 releases! However, SHOULD they even BE a warning? They should just be "normal logs" saying it is warning is warning you that something isn't right, and having an edition that DOESN'T support it doesn't warrant a warning now does it?. Heck look at the issues with LSA being enabled and it is turning itself off and that has been fixed twice just recently and it is STILL broken.

or

B) suppress the event, because Event Viewer hasn't changed in like 30 years and to filter out unwanted "errors" is cumbersome, and you have to do EVERY TIME you load Event Viewer. Can't have it save its last state now can we in 2023? :-)

or

C) ignore it and stop posting how do I fix it (Because see A)

I was able to fix this issue by creating a new Admin account on my PC, log into that new account, log out of that new account and back into my original Admin account.

I've had this problem occur on several computers now both at home and in the office (4 work PCs) where the user profile gets corrupted after a Windows update (both Windows 10 or 11).

This is clearly a Windows update since it always happens after a Windows update. Why it happens to specific PC that are completely unrelated is beyond me? Microsoft need to address the update process and add some better logging so they can pin point what is causing user profile corruption.

I don't even have Core Isolation turned on as virtualization is not enabled in the BIOS. And Home versions of Windows 11 22H2 don't even support Credential Guard, yet these constant LSA errors every boot up

Sadly, I also have these errors. This is definitely something that affects multiple users, but is it serious or trivial?

Could you please provide some screenshots of LAS package signing error? I can help you record this problem. In addition, you can also open the Feedback Hub by pressing Windows Logo+F to submit your situation to the Feedback department so that we can collect information and investigate the problem.

You can always uninstall 22H2 updates from the Windows Update page by clicking "Update History" - "Uninstall updates", then click ***here*** to download the "Hide Windows updates" tool, and run the tool to hide this update (hidden updates will not automatically install updates again). If you decide to upgrade to 22H2 again (perhaps at some point in the future), you can visit the Windows 11 download page to download the Upgrade Assistant update）