Code signing Error

Question

Hello,

Installation of driver signed with new Digicert code signing certificate (Not EV code signing) reports error on Windows 10:

"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

Old works New does not - Previous code signing certificate expired. So, we purchased a new code signing certificate from Digicert. When the driver which was signed by the old certificate is installed on the same Windows 10 system, it does not report error. When we install the driver signed with new certificate, it reports the error.

Previously we used the command:

1. signtool sign /v /tr http://timestamp.digicert.com /fd sha256 /f "ABC123.pfx" /p **** mysatasuballoc.sys For new certificate: Now, to accommodate the new standard, modified sha256 to sha384 Even with that, the error is the same. a) Please let me know if there is a change in Windows policy where code signing certificate cannot be used? b) Is EV code signing required for driver signing? c) Do we have to add any cross certificate to the signtool sign command line? Thanks