(If anyone knows how to do this via command line please let me know as I couldn't find a way) CER) Next > File name, choose one, e.g "epson.cer" > Next > Finish. > View certificate > 'Details' tab > 'Copy to File' > Next > (leave default X.509 DER encoded. cat file in the driver package, in this case es3e.cat > Digital Signatures > Highlight the name in 'Name of Signer' on the 'Signatures List' > Details.Ī new window 'Digital Signature Details' should open. (yes, Epson can't sign their drivers properly!) Successfully verified: e:\epson v300\es8b.cat SignTool Error: A certificate chain processed, but terminated in a rootĬertificate which is not trusted by the trust provider.Į:\>"E:\7600.DDK\signtool.exe" verify /a "e:\epson v300\es8b.cat" To test what's actually broken, you can use "signtool.exe /verify",įirst one fails (as in this example) and second one is correct from an Epson V300 scanner driver.Į:\>"E:\7600.DDK\signtool.exe" verify /a "e:\Epson 3170\es43.cat" INFO: Preinstalling 'e:\epson 3170\es43.inf'. INFO: RETURN: DriverPackagePreinstallW (0圎0000242) INFO: Preinstalling 'e:\epson 3170\es32.inf'. INFO: Found driver package: 'E:\epson 3170\LIB\0c0a\Es52.inf'.
INFO: Found driver package: 'E:\epson 3170\LIB\0c0a\Es32n.inf'. Or with the dpinst error in c:\WINDOWS\DPINST.log if doing command line with dpinst.exeĭpinst RETURN: DriverPackagePreinstallW (0圎0000242)
The error will manifest itself like this if installing directlyĭevcon Windows Security - "Would you like to install this device software" - tick box "Always trust software from" This will stop you being able to install from command line without fixing. In this example - installing drivers for an Epson 3170 scanner that has a broken certificate chain. Missing or incorrect Trusted Publishers/Certificates 6.2 ARM mbed Windows serial port driver.1 Missing or incorrect Trusted Publishers/Certificates.