Windows 10: LSA package is not signed as expected. This can cause unexpected behaviour with Credential...

My computer event viewer started displaying: "Credential Guard is configured to run, but is not licensed. Credential Guard was not started." and "LSA package is not signed as expected. This can cause unexpected behaviour with Credential Guard." It has shown this warning multiple times for different package names. I am not sure how to fix it.

:)

 

LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

Hello,

How to make these messages disappear:

LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0

PackageName: sfapm

PackageName: schannel

and so on...?

 

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

I did a fresh install of windows 11 with only drivers supplied by the install. The 10 errors: LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard. Is still there.

 

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

Each time my PC boot I also have 10 event Warnings ID 6155 "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard" with the paquets: msv1_0, sfapm, schannel, wdigest, cloudap, pku2u, tspkg, msv1_0, kerberos, negoexts.

And I have an event Error ID 28 Kernel Event Tracing "provider {77811378-e885-4ac2-a580-bc86e4f1bc93}. Error: 0xC0000005" that seems related with the warning because it is caused by the running process Lsalso.exe (Credential Guard & VBS Key Isolation"

In Regedit, I have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.

I have fixed:

"RunAsPPL"=dword:00000001

Any ideas???