Forums

[kahotv]

signtool sign /f Mycert.cer /tr http://timestamp.digicert.com /td sha256 /fd sha256 /csp "eToken Base Cryptographic Provider" /k "[{{TokenPasswordHere}}]=KeyContainerNameHere" myfile.exe  

The command I used to sign sys and cat files failed with error 577. I noticed that the certificate for the ndisrd demo will expire on August 25, 2024. Please try using your new certificate to see if it can run on Windows 7/8. I suspect that my situation is related to ‘The Microsoft Trusted Root Program no longer supports root certificates that have kernel mode significant capabilities’.

[kahotv]

Thank you, I may know the reason now. The previous certificate could directly sign the driver and run successfully. But after Microsoft banned it, this method no longer works. I noticed that the certificate used in the ndisrd demo will expire on August 25, 2024. Please try again with a new certificate when possible, and I suspect there will also be a 577 error.

=======================================================

The Microsoft Trusted Root Program no longer supports root certificates that have kernel mode signing capabilities.

The Microsoft Trusted Root Program no longer supports root certificates that have kernel mode signing capabilities.

For policy requirements, see Windows 10 Kernel Mode Code Signing Requirements.

Existing cross-signed root certificates with kernel mode code signing capabilities will continue working until expiration. As a result, all software publisher certificates, commercial release certificates, and commercial test certificates that chain back to these root certificates also become invalid on the same schedule. To get your driver signed, first Register for the Windows Hardware Dev Center program.

[kahotv]

I made a mistake, actually I used “/fd sha1”

[Vadim Smirnov]

I believe that, eventually, it will no longer be possible to sign drivers for Windows 7/8, much like it’s currently impossible for Windows Vista. Depending on your code signing certificate, you may need a cross-certificate to correctly sign drivers for Windows 7/8. In my experience, I’ve encountered the fewest issues with certificates from GlobalSign. However, I agree that driver signing can be tricky.

[kahotv]

I have made many attempts and finally found that after HCK testing, the. hck file obtained can be selected with these options after submission, which should solve this problem. (Actually, my HCK test failed, so my submission was rejected.)

Hope it’s helpful to everyone。

Requested Signatures：

Windows Server 2008
Windows Server 2008 X64
Windows Vista Client
Windows Vista Client X64
Windows Server 2003
Windows Server 2003 X64
Windows XP
Windows XP X64
Windows 2000

[Author]

Posts