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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-01T18:47:20+00:00

    Try removing all USB plugged in peripheral devices except mouse and kb, reboot and see if it clears the error.

    It should, then by process of elimination you can determine which device is causing the error and check for a WHQL certified driver. If there isn’t one you can set a delayed start action in startup or services.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-31T09:57:11+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.

    I get the exact same events logged on every reboot. I'm on Win11 22H2 Version 10.0.22621.963. These warnings have been logging on every reboot for a long time. Would be nice to know why, and if this logging can stop via a fix. Or at least have some information or utility provided to find out why the packages are not signed as expected, especially as at least one is a Microsoft binary.

    I've checked registry settings for everything listed in this thread, changed password, etc., to no avail.

    Was this answer helpful?

    0 comments
  3. 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
  4. Anonymous
    2022-10-19T00:10:03+00:00

    Please note: it is entirely probable the gap in days between 10/5 and 10/11 of my original post is because I had not done a reboot (I tend to logout and put the machine to sleep)
    I wasn't keeping track as close as I should've

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more