Blog Post

Hardware Dev Center
1 MIN READ

IMPORTANT: All Partners must reassociate their signing certificates!

kevintremblay's avatar
kevintremblay
Icon for Microsoft rankMicrosoft
Sep 21, 2021

We recently made some changes to Partner Center for Windows Hardware. As a result of these changes, all participants in the hardware program are required to reassociate their valid signing certificates used when making submissions to Partner Center for Windows Hardware. As a part of this process, you will need to reassociate both your Extended Validation (EV) codesign certificate, and your Authenticode codesigning certificate (if applicable). You need to take action now as any new submissions are blocked until this reassociation occurs. Additionally, you will be unable to publish any new content to Windows Update until your signing certificates have been updated.

 

To check the necessary steps, see Add or update a code signing certificate - Windows drivers. 

 

If you encounter issues while trying to update the certificates registered to your account, please reach out to our support team. For details on how to contact support, see Partner Center FAQ - Windows drivers | Microsoft Docs. 

 

 

Updated Sep 21, 2021
Version 1.0

50 Comments

Show More
  • eltima_guru's avatar
    eltima_guru
    Copper Contributor
    Sep 30, 2021

    I have the same problem. I have reassociated a signing certificate. And now receive an error 

    Unfortunately there is no valid EV certificate associated with your account.

    red-ray did you solve this?

  • red-ray's avatar
    red-ray
    Copper Contributor
    Sep 28, 2021

    Dear kevintremblay,

     

    I could not find the previous Support request number so have just submitted SR1529230915.

     

    How can I list all the Support request numbers I have submitted please?

  • red-ray's avatar
    red-ray
    Copper Contributor
    Sep 28, 2021

    Dear kevintremblay,

     

    Thank you for your post. I have read  see https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-dashboard-faq (several times) and it does not address the issue I have that I have reassociated my signing certificate several times and I still get the "Unfortunately there is no valid EV certificate associated with your account".

     

    I also reached out to your support team via https://developer.microsoft.com/en-gb/windows/hardware/support/ and thus far I have not had a response.

     

    I know the driver I signed 16-Sep-2021 still works, but I made a change to my driver on 23-Sep-2021 and need to use that driver on my Windows 11 systems.

  • kevintremblay's avatar
    kevintremblay
    Icon for Microsoft rankMicrosoft
    Sep 27, 2021

    If you encounter issues while trying to update the certificates registered to your account, please reach out to our support team. For details on how to contact support, see Partner Center FAQ - Windows drivers | Microsoft Docs. 

     

    The requirement to associate your EV codesign certificate, and if used. Authenticode codesign certificates has no impact on the ability of your driver to be loaded by the OS. Submissions that have already been processed and signed by Microsoft will continue to function.

  • red-ray's avatar
    red-ray
    Copper Contributor
    Sep 27, 2021

    I have uploaded a new certificate which is reported as:

     

    Certificate list
    Name               Thumbprint                                                                   Type         Expiration date Validated Date       Issuer Name Status Action
    RH Software Ltd3AD34BFD2DAFF23F5C2B751501863D740B6AF6D5CodeSign1/28/202309/27/2021 10:38:26ZCN=COMODO RSA Extended Validation Code Signing CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBActive
    https://partner.microsoft.com/en-us/dashboard/Account/ManageCertificates#

     

    But I am still unable to WHQL sign my driver and then I try I get:

     

    • Unfortunately there is no valid EV certificate associated with your account. To make submissions to the Hardware Dev Center, your account needs to be verified with at least one EV certificate upload. You can upload a new certificate http://go.microsoft.com/fwlink/?LinkId=829460 and read more about this policy http://go.microsoft.com/fwlink/?LinkId=829459.

    All was great when I signed my driver on 16-Sep-2021, what needs to happen to make things start working again please?

  • Koichi_Nagai's avatar
    Koichi_Nagai
    Copper Contributor
    Sep 27, 2021

     Our registered Signable.bin  is singed with our effective digital certificate with SHA256, but new submission is blocked.

     

    To clarify, do we need just re-upload the Signable.bin to reassociate?

    Or must we upload a new Signable.bin signed with the latest SignTool?

     

  • Igakl's avatar
    Igakl
    Copper Contributor
    Sep 22, 2021

    I'm sorry I do not understand. The Driver Hardware dashboard has prepared a signed driver upon submition a year ago. now I download the Microsoft signed driver but when I install it on a Win10 station it does not load, unless I disable the secure boot. What should I do next? re-sign the driver? it means that I need to purchase a new key. Why was it changed? why an "old" driver is not acceptable as a signed driver?

    Regards.

  • Mammon's avatar
    Mammon
    Copper Contributor
    Sep 22, 2021

    Even after new signed file was uploaded notification still appear:
    ATTENTION: We recently made changes to signature validation on all Partner Center for Windows Hardware submissions. You must take action before you can create new submissions, or publications. https://aka.ms/cert_revalidation

  • Igal_KroyterIgal's avatar
    Igal_KroyterIgal
    Copper Contributor
    Sep 22, 2021

    Hi,

    I understand that the above info is regarding new submissions what about older submissions of drivers which already have been signed and refused by the Win10 boot process, unless the secure boot is disabled?