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

Issues with the Credential guard may affect LSA package

by Henderson Jayden Harper
Henderson Jayden Harper
Henderson Jayden Harper
Passionate about technology, Crypto, software, Windows, and everything computer-related, he spends most of his time developing new skills and learning more about the tech world. He also enjoys... read more
Reviewed by Alex Serban
Alex Serban
Alex Serban
Windows Server & Networking Expert
After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server... read more
Affiliate Disclosure
  • The LSA package error can occur due to a bug installed with a recent Windows update.
  • Performing a Clean boot on your PC can fix the issue.
  • Using the Restore point is easy to get around the problem.
lsa package is not signed as expected

To fix various PC problems, we recommend Restoro PC Repair Tool:
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:

  1. Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
  2. Click Start Scan to find Windows issues that could be causing PC problems.
  3. Click Repair All to fix issues affecting your computer's security and performance
  • Restoro has been downloaded by 0 readers this month.

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 to remove your password from Windows 11 or during a system reboot.

Why is the LSA package not signed as expected?

Encountering the LSA package not signed as expected error on your PC can be due to various reasons. First, the error can cause unexpected behavior with Credential Guard event ID 6155, preventing users from logging in.

However, the most common cause of the LSA package not signing as expected error is a Windows update error on your PC. Many users report that the error began when they rebooted their PCs after updating to Windows 22H2.

Furthermore, other factors that can cause this error are:

  • Third-party app interference with the LSA security system – Third-party apps like antivirus software can impede the activities of the Local Security Authority. They can block access to the necessary credentials, likewise, they can try to access it without authorization. Also, credential manager software can cause the LSA package error.
  • Issues with the Credential Guard – The LSA package is not signed as expected error may appear when there is an issue with the Credential Guard.

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:

  • First, disable the antivirus software on your PC.
  • Then, restart Windows in Safe Mode and check if the error appears.

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

1. Perform a Clean boot

  1. Press Windows + R key to open the Run dialog box, type msconfig in the text bar, and click OK.
  2. Navigate to the Services tab and check the box for the Hide all Microsoft services option, then click Disable all.
  3. Go to the Startup tab and click Open Task Manager.
  4. Select the unnecessary startup programs and click the Disable button.
  5. Restart your PC and check if the error appears.

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

2. Uninstall recent Windows updates and update Windows

  1. Press Windows + I to open the Settings app.
  2. Click on Windows Update and click the Update history option.
  3. Click the Uninstall updates button and select the most recent update.
  4. Select Uninstall.

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

3. Perform a System Restore

  1. Left-click the Start button and input restore, then click Create a Restore Point.
  2. Navigate to the System Protection tab and click on System Restore.
  3. Click Choose a different system restore option and click Next to choose a specific Restore Point.
  4. Select the last time your system worked correctly, then click Next.
  5. Click the Finish button.

Expert tip:


Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

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, check how to fix Restore Point if it’s not working on your PC.

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

This sort of tool helps you run an in-depth scan of your computer and offer you a detailed diagnostic of all faulty or corrupted components, to ultimately repair or replace them with healthy files.

Get Restoro

4. Enable LSA Protection using the Registry

  1. Right-click the Start button, select Run, type Regedit, and click OK to open the Registry Editor.
  2. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Set the new value to:
    1. Value name: RunAsPPL
    2. Value data: 00000002
  4. Close the Registry Editor and restart your PC.

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

5. Turn off Credential Guard

  1. Left-click the Start button, type Regedit in the search box, and select the Registry Editor from the results.
  2. Navigate to the following keys and set their values to 0 to disable the virtualization-based security: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LsaCfgFlags HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\LsaCfgFlags
  3. Restart your computer.

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

Read about disabling Credential Guard on Windows 10/11 if you can get around the above steps.

In conclusion, we have a detailed guide on turning off password-protected sharing in Windows 11.

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

Still having issues? Fix them with this tool:


If the advices above haven't solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on to easily address them. After installation, simply click the Start Scan button and then press on Repair All.

This article covers:Topics: