You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't update the npcap driver. When trying to install, error e0000247 is displayed (associated with the certificate if I'm not mistaken). How to fix it? What files should I send for a more accurate error diagnosis?
Thanks for reporting this. What version of Windows are you running? Error 0x247 appears to be related to Unicode processing. What locale (language or localization) are you using in Windows? Please include the NPFInstall.log and install.log from \Program Files\Npcap\.
NPFInstall.log install.log
I have Windows in English and the language is set to Polish. Earlier versions of npcap were installed without any problem, only this new version has a problem. The system is Windows 8.1
The installed security catalog file C:\Program Files\Npcap\npcap.cat (file size: 2716 bytes) is signed with a self-signed certificate:
SignTool.exe verify /a /v /kp "C:\Program Files\Npcap\npcap.cat"
Verifying: C:\Program Files\Npcap\npcap.cat
Unable to verify this file using a catalog.
Hash of file (sha1): EA750CDC691DE33A0B1A9224C1BCF2BAF077BC37
Signing Certificate Chain:
Issued to: WDKTestCert nmap,131259686273466591
Issued by: WDKTestCert nmap,131259686273466591
Expires: Thu Dec 10 20:00:00 2026
SHA1 hash: F587B3379B4385078E0F53EDAE66938ACABDD7A1
File is not timestamped.
SignTool Error: Signing Cert does not chain to a Microsoft Root Cert.
Number of files successfully Verified: 0
Number of warnings: 0
Number of errors: 1
Which causes signature verification failure of the driver package, as shown in C:\Windows\Inf\setupapi.dev.log (OS is Windows 8.1 Pro x64, with all updates installed)
@luisdallos Thanks for analyzing this. I will investigate what could have gone wrong on our build system to cause this file to not be signed with our EV code-signing cert.
Ok, here's the problem: we used to dual-sign the Npcap driver with a SHA-1 cert and a SHA-256 cert, because Windows Vista didn't understand SHA-256. When we renewed our certificate, we did not get the SHA-1 cert renewed, and we changed our build system to only sign with the SHA-256 cert by removing the functions that sign with SHA-1. However, the CAT file was only ever signed with SHA-1 because that file format does not support multiple signatures. So the published CAT file used for systems other than Windows 10 was never re-signed when building the installer, and instead has the "test" signature added by Visual Studio. I would have expected Microsoft to flag this as a problem when they provided their Attestation Signature for Windows 10, but they just overwrote it with their own signature there.
We will release a new installer to address this issue. I am not sure yet whether we will increase the version number for this or not.
Npcap 0.9986 should solve this issue. Please let us know if you have any further problems.
@dmiller-nmap I installed npap in win2008R2 and found such an error "The publisher of this driver software could not be verified". I installed kb4474419(support for sha-2 sign) patch can be used normally. I would like to know that it must be installed this patch?
Activity
dmiller-nmap commentedon Dec 15, 2019
Thanks for reporting this. What version of Windows are you running? Error 0x247 appears to be related to Unicode processing. What locale (language or localization) are you using in Windows? Please include the NPFInstall.log and install.log from
\Program Files\Npcap\.MrPepka commentedon Dec 15, 2019
NPFInstall.log
install.log
I have Windows in English and the language is set to Polish. Earlier versions of npcap were installed without any problem, only this new version has a problem. The system is Windows 8.1
luisdallos commentedon Dec 16, 2019
Related issue: nmap/nmap#875
The installed security catalog file
C:\Program Files\Npcap\npcap.cat(file size: 2716 bytes) is signed with a self-signed certificate:Which causes signature verification failure of the driver package, as shown in
C:\Windows\Inf\setupapi.dev.log(OS isWindows 8.1 Pro x64, with all updates installed)dmiller-nmap commentedon Dec 16, 2019
@luisdallos Thanks for analyzing this. I will investigate what could have gone wrong on our build system to cause this file to not be signed with our EV code-signing cert.
dmiller-nmap commentedon Dec 16, 2019
Ok, here's the problem: we used to dual-sign the Npcap driver with a SHA-1 cert and a SHA-256 cert, because Windows Vista didn't understand SHA-256. When we renewed our certificate, we did not get the SHA-1 cert renewed, and we changed our build system to only sign with the SHA-256 cert by removing the functions that sign with SHA-1. However, the CAT file was only ever signed with SHA-1 because that file format does not support multiple signatures. So the published CAT file used for systems other than Windows 10 was never re-signed when building the installer, and instead has the "test" signature added by Visual Studio. I would have expected Microsoft to flag this as a problem when they provided their Attestation Signature for Windows 10, but they just overwrote it with their own signature there.
We will release a new installer to address this issue. I am not sure yet whether we will increase the version number for this or not.
dmiller-nmap commentedon Dec 18, 2019
MrPepka commentedon Dec 18, 2019
Yes, i'm comform. Driver install with success
Thx for help
muse117 commentedon Feb 27, 2020
@dmiller-nmap I installed npap in win2008R2 and found such an error "The publisher of this driver software could not be verified". I installed kb4474419(support for sha-2 sign) patch can be used normally. I would like to know that it must be installed this patch?
