Apr 20 2017 10:19 AM
Could I please have some advice around using the Microsoft hardware driver co-signing tool? The URL is https://developer.microsoft.com/en-us/dashboard/hardware/Driver/ . As I understand the process, I provide a CAB file with the signed driver enclosed. The Microsoft Dev Center account has access to the same signing certificate. When I upload the CAB file, it fails the "preparation" phase with the error message:
“Unfortunately we were unable to validate the signature on your attestation submission. Common reasons for this are: the submission was not signed, the signing certificate was expired, or the signing certificate isn’t associated with your Dev Center account. Double check the signature on your package and try your submission again. If you continue to receive this error contact support.”
I needed to get a duplicate certificate to incorporate in my CAB file since we could not find the original. I strongly suspect the problem is the signing certificate that Microsoft has does not match the duplicate certificate in my CAB file. Where and how do I update my Dev Center account with the duplicate certificate?
Thanks!
May 16 2018 11:27 PM
hi,
Here in question, I found this suspicious "As I understand the process, I provide a CAB file with the signed driver enclosed"
as per process
No need to sign driver file before enclosing instead you need to sign cab