"LSA package is not signed as expected" -- Yes, again.


STRESSED

STRESSED

Well-known member
Member
Local time
11:14 AM
Posts
43
OS
Windows 11 23H2 (OS Build 22631.3296)
I've already set "Configure LSA to run as a protected process" to "Enabled without UEFI lock" in Group Policy, as described here. I've of course rebooted. But I still see a series of warnings in the Event Viewer System log:

LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.
PackageName: negoexts ... PackageName: kerberos ... PackageName: msv1_0 ... PackageName: tspkg ... PackageName: pku2u ...
PackageName: cloudap ... PackageName: wdigest ... PackageName: schannel ... PackageName: sfapm
Click to expand...

The "RunAsPPL" value is set to 2 under "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" and this was done by Group Policy, not by direct registry editing. I don't have a "RunAsPPLBoot" value at all.

Is this a real issue? What should I do?
 
Windows Build/Version
23H2

My Computer

System One

  • OS
    Windows 11 23H2 (OS Build 22631.3296)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Maingear Vybe
    CPU
    AMD Ryzen 5 3600X
    Motherboard
    Gigabyte X570 Gaming X
    Memory
    HyperX Predator RGB DDR4 3200MHz (32 GB total)
    Graphics Card(s)
    NVIDIA GeForce RTX 2070 Super
    Sound Card
    RealTek ALC887 (Onboard)
    Hard Drives
    Seagate FireCuda 520 SSD/NVMe (1 TB)
    PSU
    EVGA 750W SuperNOVA B2 80+ BRONZE
    Cooling
    Maingear Epic 240
    Keyboard
    SteelSeries Apex 3 TKL
    Mouse
    Razer Viper 8KHz
    Internet Speed
    1 Gbps
    Browser
    Brave
    Antivirus
    Microsoft Defender
    Other Info
    No third-party security software
STRESSED said:
I've already set "Configure LSA to run as a protected process" to "Enabled without UEFI lock" in Group Policy, as described here. I've of course rebooted. But I still see a series of warnings in the Event Viewer System log:



The "RunAsPPL" value is set to 2 under "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" and this was done by Group Policy, not by direct registry editing. I don't have a "RunAsPPLBoot" value at all.

Is this a real issue? What should I do?
Click to expand...
Check the information at the link listed below for some help.

www.thewindowsclub.com

LSA package is not signed as expected Credential Guard error

Fix LSA package is not signed as expected, This can cause unexpected behavior with Credential Guard, Event ID 6155 error in Windows 11.
www.thewindowsclub.com www.thewindowsclub.com
 

My Computer

System One

  • OS
    Windows 11 Professional
    Computer type
    PC/Desktop
    Manufacturer/Model
    Microcenter B677
    CPU
    Intel Core i5-9400
    Motherboard
    ASRock H310CM-HDV/M.2
    Memory
    32GB
    Graphics Card(s)
    Integrated Intel UHD Graphics 630
    Sound Card
    Intel Kaby Lake - High Definition Audio / cAVS (Audio, Voice, Speech) [A0]
    Monitor(s) Displays
    LG Model: GSM59F1
    Screen Resolution
    2560x1080
    Case
    Lian Li 205M
    Antivirus
    Kaspersky AV
The only real takeaway for me from that article is to try adding "RunAsPPLBoot". I'll give it a shot. Thanks.
 

My Computer

System One

  • OS
    Windows 11 23H2 (OS Build 22631.3296)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Maingear Vybe
    CPU
    AMD Ryzen 5 3600X
    Motherboard
    Gigabyte X570 Gaming X
    Memory
    HyperX Predator RGB DDR4 3200MHz (32 GB total)
    Graphics Card(s)
    NVIDIA GeForce RTX 2070 Super
    Sound Card
    RealTek ALC887 (Onboard)
    Hard Drives
    Seagate FireCuda 520 SSD/NVMe (1 TB)
    PSU
    EVGA 750W SuperNOVA B2 80+ BRONZE
    Cooling
    Maingear Epic 240
    Keyboard
    SteelSeries Apex 3 TKL
    Mouse
    Razer Viper 8KHz
    Internet Speed
    1 Gbps
    Browser
    Brave
    Antivirus
    Microsoft Defender
    Other Info
    No third-party security software
No use. The errors persist. I guess I will simply ignore them.
 

My Computer

System One

  • OS
    Windows 11 23H2 (OS Build 22631.3296)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Maingear Vybe
    CPU
    AMD Ryzen 5 3600X
    Motherboard
    Gigabyte X570 Gaming X
    Memory
    HyperX Predator RGB DDR4 3200MHz (32 GB total)
    Graphics Card(s)
    NVIDIA GeForce RTX 2070 Super
    Sound Card
    RealTek ALC887 (Onboard)
    Hard Drives
    Seagate FireCuda 520 SSD/NVMe (1 TB)
    PSU
    EVGA 750W SuperNOVA B2 80+ BRONZE
    Cooling
    Maingear Epic 240
    Keyboard
    SteelSeries Apex 3 TKL
    Mouse
    Razer Viper 8KHz
    Internet Speed
    1 Gbps
    Browser
    Brave
    Antivirus
    Microsoft Defender
    Other Info
    No third-party security software
You must log in or register to reply here.

Similar threads

LSA package is not signed as expected.
Replies
9
Views
26K
Jacques1945
Jacques1945

Latest Support Threads

Latest Tutorials

Back
Top Bottom