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-10-21T17:08:50+00:00

    It's something in the user account controls.

    Do these both have local Admin accounts enabled or multiple user accounts?

    Unfortunately, the person who did a new build didn't respond as to whether it was an upgrade or a fresh install since an upgrade from 10 might have the local admin enabled.

    I logged into the local admin on mine and saw an error about the password change requirement, which was previously set to never expire, so I am leaning towards a change in the group policy from the update. After I reset the policies, just through the user account control, to never expire password, etc. I haven't had further issues.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-10-21T17:38:21+00:00

    Try setting a password.

    I know its something to do with the user account controls from an update, possibly to the Group Policies, and since 11 is working on being more secure, I think it is trying to force specific user account controls.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-10-22T06:43:29+00:00

    The gaming machine has a MUA and local admin, with options of same sign-in using passwords or via PIN. The work rig2 that I just built only uses a single sign-in source via the FOB. Said machine is a fresh clean install with the prebuilt MS ISO, and uses no-other sign-in option except the FOB verification.

    The only machine not doing this is my 1st rig which uses a direct MS account for sign-in.

    Anyway for fun, here's a list of the packages throwing a LSA error: msv1_0, sfapm, schannel, wdigest, cloudap, tspkg, kerberos, negoexts

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-10-23T19:30:50+00:00

    I removed the pin from this machine, and added a password to my Microsoft account

    Rebooted, same 10 events

    Removed the password from account, added pin to this machine

    Rebooted, same 10 events

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-10-24T14:46:50+00:00

    Looks like I'm a victim of this madness as well. Same messages.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments