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 No comments

85 answers

Sort by: Oldest
  1. Anonymous
    2023-01-13T21:49:00+00:00

    Im kinda in the same boat. Onedrive was forcing some profile setting with a fresh install every time. shut one drive down and it fixed it for only for a short time. was throwing dcom 10016 error before as well. thats gone and now just the LSA error. Shuts down to straight black screen shortly into a game, with no reboot.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-01-16T07:01:37+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???

    Exact same issues - Win 11 Pro 22H2. AMD 2700X.

    I have tried all the troubleshooting options provided in this thread and elsewhere.

    Errors persist but fortunately do not appear to impact the system

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-01-19T20:52:15+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-21T03:03:38+00:00

    Same here. New build as well. It's on the core MSFT security packages too, so this isn't a profile or device issue. I wish they would just ACK it and get it in the bug queue. It's clearly not working as intended. Either those packages aren't properly signed (seems unlikely), or some aspect of credential guard is being reused on Pro to do some subset of what it does on Enterprise and these errors are annoying, but spurious (very likely)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-01-21T07:33:58+00:00

    Was this answer helpful?

    0 comments No comments