This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
"The update resolved the issue".
I believed you - those events stopped
However, after doing the windows update today with "2022-10 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5018427)"
the events have returned...
From 10/5 until today, those events were no longer logged
Looks like I'm a victim of this madness as well. Same messages.
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
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.
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
