How to enable “Local Security Authority Protection” | Building a specialized Z computer gaming environment

July 10, 2023Windows Update

In Windows 11, “Local Security Authority / LSA” may not be enabled depending on the environment. In this article,Here’s how to operate the Protect Local Security Authority.

First of all, for “Local Security Authority Protection”, until April 2023, “Settings” -> “Privacy and Security” -> “Windows Security” -> select “Open Windows Security” -> “Device Security” -> ” I was able to set it from Core Quarantine Details, but after April 2023 the setup screen won’t show.

This screen will not be displayed after April 2023

But it works in the background. To check if it’s running in the background, open the event viewer, go to Windows Logs > System, and see “LSASS.exe was started as a level 4 protected process.” (Source: Wininit / Event ID: 12), protection is a business.

If there is this item, it works properly in the background

There is no problem if there are the above items, but depending on the environment, there may not be the above items, and it may not run in the background. If the above item is not present, adjust the registry and restart the computer to enable Local Security Authority Protection.

The procedure for setting the record is as follows.

1. Launch the Registry Editor (press Windows + R, type regedit and enter)
2. Open “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa”
3. Check if there is “RunAsPPL” on the right side. If not, right-click on the right side and select New (D) Value → DWORD (32-bit), type RunAsPPL and enter.
4. Double click “RunAsPPL”, put “2” in “Value data (V)” and enter.

If you restart your computer with this, an event (Source: Wininit / Event ID: 12) will be displayed in the event viewer stating “LSASS.exe was started as a protected process at level 4.” , “Local Security Authority Protection” must be enabled.

If that doesn’t work, add a DWORD called “RunAsPBLBoot” and set the value to “2”.

Now restart your computer and Local Security Authority Protection should be enabled.