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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-02T23:40:35+00:00

    I still get these errors with a new local admin profile and with no USB devices (other than my laptop's built-in keyboard) in Device Manager. In my case, this has nothing to do with profiles or USB device drivers, and everything to do with the Windows 11 upgrade being a flaming dumpster fire. Microsoft should stop pressuring Windows 10 users to upgrade to Windows 11 until they fix their broken OS upgrade process. It borked all 3 of my Windows 10 PCs, each in a different way.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-01-02T22:35:20+00:00

    Have you tried a different profile?

    If it’s not hardware then it’s something in the startup.

    You might want to temporarily enable the local Administrator account or add a new local admin profile and see if you get errors.

    Eliminate the last few possibilities by using another profile and removing the KB/Mouse, plug in only to enter your login info and unplug again.

    If you still have an error after that it’s one of the internal component drivers, memory, video, or sound cars.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-02T03:12:43+00:00

    I've recently re-built this machine with the latest download from Microsoft

    I tried unplugging everything but keyboard and mouse

    Still get 10 every time - the same 10 as on November 9:

    "I used the "Using Local Group Policy on Windows 11, 22H2" from the article you provided: Configuring Additional LSA Protection | Microsoft Learn

    I set the "Enabled with UEFI Lock" option

    Still getting 10 errors as before"

    This time I did not jump through the hoops that I had done on Nov 9

    What I have is straight out of MS

    Was this answer helpful?

    0 comments
  4. 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
  5. 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