If you use Windows 11 on your computer and are looking for a way to activate the Local Authority Protection (LSA) you’re not alone. Many other users of Microsoft’s latest operating system find themselves in the same situation. Even some of them had never heard of this security feature that is giving them headaches today.
The unexpected deactivation of LSA has become a topic of discussion in the support forums of the Redmond giant. The question that everyone wants to know is what has happened and how to put an end to this problem. Fortunately, as they point out in Genbeta, a volunteer moderator endorsed by Microsoft has provided a solution. Let’s take a closer look at the details.
The latest Windows 11 problem
According to users and the Microsoft expert community, the problem with LSA may be caused by one of the following: latest updates of the operating system. And this is a scenario that shouldn’t surprise us. On some occasions, updates that should offer improvements end up breaking something in the system, and here we have a clear example of this.
What has been broken is one of the components of the Windows Security section. As a result of this inconvenience, users have started to see a yellow warning icon superimposed on the traditional blue icon in the system tray. This has been reason enough to arouse concern and wonder what has really happened.
By clicking on the aforementioned icon, the system indicates that Local Security Authority (LSA) Protection is deactivated. This is a feature intended to protect against the theft of sensitive information or login credentials by blocking code injection and crash dump blocking.
Given the importance of this security element, keeping it enabled is not a bad idea. The problem is that due to the failure in the system this is not possible. The affected users, they explain, have tried everything. Activate it manually, restart your computer and even try to modify the registry with “regedit” or uninstall updates.
The solution provided by the volunteer moderator seems to be the most effective. This consists of modify registry with a file with a “.reg” extension in order to revert the changes applied by the problematic update. It is a very punctual solution that avoids damaging any other component or functionality of the system.
How to enable Local Security Authority (LSA) Protection
Open Notepad and copy the following text:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
“RunAsPPL”=dword:00000002
“RunAsPPLBoot”=dword:00000002
Open the saved file (this will cause the necessary changes to be made to the Windows Registry). Restart the system.
It should be noted that this solution is temporary. That is, it serves to solve the problem until Microsoft releases a new update. Of course, the volunteer moderator points out that it is possible that those in Redmond take time to address the problem through Windows Update.
Images: Ed Hardie | MateoGutierrez4 (Microsoft Community Member)
In Xataka: Microsoft 365 Copilot is ChatGPT revolutionizing Office: this is how you write emails, documents or presentations for you
In Xataka: Microsoft made TPM 2.0 an essential requirement for Windows 11: it is not as secure as we thought
