Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
Autoruns 14.3 reports Kaspersky driver as "Not Verified" despite valid Authenticode signature
Hello,
I would like to report a possible signature verification inconsistency in Autoruns 14.3 on Windows 11.
The following Kaspersky driver is displayed in red as "(Not Verified) AO Kaspersky Lab":
- Entry:
klids.K4W-21-26
Description: Network Processor [fre_win7_x64]
File: C:\ProgramData\Kaspersky Lab\AVP21.26\Bases\klids.sys
SHA-256: DDE49DB840B614BCB7E93485A1316F243142233166E34F34051F0B51C397D202
However, Windows PowerShell reports:
Status : Valid
SignatureType : Authenticode
IsOSBinary : False
The signing certificate is:
Subject: Microsoft Windows Hardware Compatibility Publisher
Issuer: Microsoft Windows Third Party Component CA 2012
Validity: February 20, 2025 – February 18, 2026
The issue persists after refreshing Autoruns. Disabling "Verify code signatures" removes the red highlighting.
Could you please clarify why Autoruns reports this driver as unverified while Windows Authenticode verification succeeds?
Is this expected behavior related to certificate expiration, timestamp validation, or a difference in signature verification policies?
Thank you for your assistance.Hello,
I would like to report a possible signature verification inconsistency in Autoruns 14.3 on Windows 11.
The following Kaspersky driver is displayed in red as "(Not Verified) AO Kaspersky Lab":
Entry: klids.K4W-21-26
Description: Network Processor [fre_win7_x64]
File: C:\ProgramData\Kaspersky Lab\AVP21.26\Bases\klids.sys
SHA-256: DDE49DB840B614BCB7E93485A1316F243142233166E34F34051F0B51C397D202
However, Windows PowerShell reports:
Status : Valid
SignatureType : Authenticode
IsOSBinary : False
The signing certificate is:
Subject: Microsoft Windows Hardware Compatibility Publisher
Issuer: Microsoft Windows Third Party Component CA 2012
Validity: February 20, 2025 – February 18, 2026
The issue persists after refreshing Autoruns. Disabling "Verify code signatures" removes the red highlighting.
Could you please clarify why Autoruns reports this driver as unverified while Windows Authenticode verification succeeds?
Is this expected behavior related to certificate expiration, timestamp validation, or a difference in signature verification policies?
Thank you for your assistance.