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

Anonymous
2022-09-21T15:03:13+00:00

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.

0 comments

85 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-11-10T03:07:30+00:00

    "Was hoping the Windows Updates applied last night would help..."

    I'm happy to see event ids 6147, 6155 go away

    I'm guessing the updates were effective

    Not sure why I was showing new events after installing the updates and rebooting

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-11-10T10:00:35+00:00

    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???

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-11-12T04:44:35+00:00

    I'm at a loss...

    I just rebooted the machine, and am again seeing event Ids 6147, 6155

    Beyond me...

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-11-22T14:03:22+00:00

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

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-12-17T22:57:58+00:00

    Same exact problem after upgrading Win10 Pro x64 to Win11 Pro x64 on my personal laptop. I use my Microsoft account (administrator) to sign into Windows, and I have it set up to use a PIN code for signing in.

    Of course, this isn't the only problem the upgrade to Windows 11 has created; it also mangled all my local filesystem ACLs, so the system itself and various services/applications all report "access denied" errors at every turn. It even wrongly traversed symlinks/junctions I had created under my %USERPROFILE% folder (for convenient persistently-mounted access to shares on other PCs on my home network) and partially mangled the ACLs on *those* files on the other PCs! And on one of my other PCs, the upgrade swapped my drive letters around so that it won't even boot anymore because it wrongly keeps assigning C: to a data drive and assigning F: to my system drive.

    As far as I can tell, Windows 11 is a total technical dumpster fire under its pretty-looking veneer. This is what you get when you lay off your entire QA department and let developers assure the "quality" of their own work. Absolutely unforgiveable.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments