Share this article

This article is translated in

Improve this guide

LSA Package is Not Signed as Expected: 5 Ways to Fix It

Issues with the Credential guard may affect LSA package

4 min. read

Updated onJuly 25, 2024

updated onJuly 25, 2024

Share this article

This article is translated in

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

Resolve multiple Windows PC issues and speed up your PC effortlessly with specialized software.

The LSA package is not signed as expected is an error from the Local Security Authority (LSA) security subsystem in the Microsoft Windows operating system. It verifies login attempts and tasks relating to Windows authentication.

However, the error can pop up when you try toremove your password from Windows 11or during a system reboot.

Why is the LSA package not signed as expected?

The full error log message reads: Event ID 6155: LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

The most common cause of the LSA package not signing as expected error is aWindows update erroron your PC. Many of our readers reported that the error began when they rebooted their PCs after updating to Windows 22H2.

Furthermore, other factors that can cause this error are:

Various other factors can cause the issue and vary on different PCs. Nonetheless, you can resolve the problem by troubleshooting your PC.

What can I do if the LSA package is not signed?

Before proceeding with any advanced troubleshooting steps for the error, go through the following preliminary check:

If the above checks are not helpful, try the solutions below:

1. Perform a Clean boot

A clean boot will prevent any third-party app from launching from the start, blocking any interference from the apps. Also, it’lldisable startup appsthat may prompt the error.

2. Uninstall recent Windows updates and update Windows

Uninstalling the recent Windows updateshould help fix any bug installed with the last patch causing issues with the LSA package.

3. Perform a System Restore

A system restore will backdate your procedure and remove the recently added corrupt items or faulty components causing the issue.

If you have any issues running it, checkhow to fix Restore Point if it’s not workingon your PC.

If you don’t want to perform this manually, then an alternative to this process would be anautomated tool.

4. Enable LSA Protection using the Registry

Enabling LSAvia the Registry editor will set it to isolate other services.

5. Turn off Credential Guard

Note that you must set the registry settings to 0 to disable virtualization-based security.

Read aboutdisabling Credential Guard on Windows 10/11if you can get around the above steps. This isn’t the only issue and we have a great guide on what to do ifLocal Security Authority Protection is off on Windows 11.

In conclusion, we have a detailed guide onturning off password-protected sharingin Windows 11.

If you have further questions or suggestions, you can drop them in the comments below.

LSA Package is Not Signed as Expected: 5 Ways to Fix It#

Why is the LSA package not signed as expected?#

What can I do if the LSA package is not signed?#

1. Perform a Clean boot#

2. Uninstall recent Windows updates and update Windows#

3. Perform a System Restore#

4. Enable LSA Protection using the Registry#

5. Turn off Credential Guard#