F5F Stay Refreshed Software Operating Systems The LSA package does not have the expected signature.

The LSA package does not have the expected signature.

The LSA package does not have the expected signature.

G
GAVIN815
Junior Member
Find
6
12-11-2016, 02:45 PM
#1
Dear Experts,

Assist in resolving these PC issues:
Level Date and Time Source Event ID Task Category
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package lacks expected signature. This may lead to issues with Credential Guard.
PackageName: msv1_0"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing expected signature. Could affect interactions with Credential Guard.
PackageName: sfapm"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing expected signature. May result in unexpected behavior with Credential Guard.
PackageName: schannel"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package lacks signature. This might trigger unintended actions with Credential Guard.
PackageName: wdigest"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing expected signature. Could lead to unexpected outcomes with Credential Guard.
PackageName: cloudap"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package not signed as anticipated. This may impact Credential Guard functionality.
PackageName: pku2u"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing signature. This could result in unexpected behavior with Credential Guard.
PackageName: tspkg"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package lacks expected signature. May cause unforeseen actions with Credential Guard.
PackageName: msv1_0"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing signature. This might disrupt normal operations with Credential Guard.
PackageName: kerberos"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package not signed. Credential Guard is active but not properly licensed. The system did not initiate the feature."
PackageName: negoexts"
Warning 2/13/2025 7:41:38 AM LsaSrv 6147 None Credential Guard is enabled, yet it isn't licensed. The feature was not launched.

Thank you.
Reply
Reply
G
GAVIN815
12-11-2016, 02:45 PM #1

Dear Experts,

Assist in resolving these PC issues:
Level Date and Time Source Event ID Task Category
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package lacks expected signature. This may lead to issues with Credential Guard.
PackageName: msv1_0"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing expected signature. Could affect interactions with Credential Guard.
PackageName: sfapm"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing expected signature. May result in unexpected behavior with Credential Guard.
PackageName: schannel"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package lacks signature. This might trigger unintended actions with Credential Guard.
PackageName: wdigest"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing expected signature. Could lead to unexpected outcomes with Credential Guard.
PackageName: cloudap"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package not signed as anticipated. This may impact Credential Guard functionality.
PackageName: pku2u"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing signature. This could result in unexpected behavior with Credential Guard.
PackageName: tspkg"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package lacks expected signature. May cause unforeseen actions with Credential Guard.
PackageName: msv1_0"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package missing signature. This might disrupt normal operations with Credential Guard.
PackageName: kerberos"
Warning 2/13/2025 7:41:38 AM LsaSrv 6155 None "LSA package not signed. Credential Guard is active but not properly licensed. The system did not initiate the feature."
PackageName: negoexts"
Warning 2/13/2025 7:41:38 AM LsaSrv 6147 None Credential Guard is enabled, yet it isn't licensed. The feature was not launched.

Thank you.

Reply
Reply
K
Kr0ssPissi
Member
Find
183
12-19-2016, 11:31 AM
#2
This article discusses an issue where the package is not signed as expected, leading to a credential guard error.
Reply
Reply
K
Kr0ssPissi
12-19-2016, 11:31 AM #2

This article discusses an issue where the package is not signed as expected, leading to a credential guard error.

Reply
Reply