IMPORTANT: All Partners must reassociate their signing certificates!

Published Sep 21 2021 07:56 AM 11.7K Views
Microsoft

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

 

 

37 Comments
Occasional Visitor

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? 

Occasional Visitor

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

Occasional Visitor

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.

Regular Visitor

 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?

 

Frequent Visitor

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

 

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 here and read more about this policy here.

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

Microsoft

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.

Frequent Visitor

Dear kevintremblay,

 

Thank you for your post. I have read  see Partner Center FAQ - Windows drivers | Microsoft Docs (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.

Frequent Visitor

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?

Frequent Visitor

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?

Occasional Visitor

I'm also having the same problem as red-ray.  Ticket opened with MS, but what has changed to cause this?

Occasional Visitor

Hi there!

Our company has been using an EV Code Signing Certificate issued by Sectigo, and we have recently noticed that it is no longer defined as an EV Certificate by you, but rather as a CodeSign certificate, for some reason, which prevents us from being able to sign our driver. Would you be able to tell us why this change from EV to CodeSign happened and what needs to be done to fix this issue?

We hope to hear from you soon.

P.S. We're attaching our certificate to the enquiry.

Occasional Visitor

Policy.png

 

Frequent Visitor

@danshov I have the same problem. The certificate is called "COMODO RSA Extended Validation Code Signing CA".

But in certificate list Microsoft marked it as Codesign instead of EV. Previously we used it many times to receive a driver signature. It stopped working after cerificate reassociation. 
 
Occasional Visitor

We also use the COMODO RSA Extended Validation Code Signing CA.

Frequent Visitor

We also use the COMODO RSA Extended Validation Code Signing Certificate. I have uploaded a new certificate which is reported below in Certificate List. Still I can not submit my drivers for attestation signing. What is the problem? I NEED to SIGN new version of drivers.

 

SignableFile.bin was signed with command line below. All options for sha256 are used. What is wrong? Why type is "CodeSign" instead of "EV CodeSign"?

 

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\signtool.exe" sign /s MY /sha1 "ead1de2a8e66964d3ef1d80ea9c42af953a6fd32" /v /d "FDExt Software" /du "http://www.softlab-nsk.com" /tr http://timestamp.comodoca.com/rfc3161 /td sha256 /fd sha256 SignableFile.bin 


"OOO ""SoftLab-NSK"""EAD1DE2A8E66964D3EF1D80EA9C42AF953A6FD32CodeSign01.12.202210.03.2021 07:40:35ZCN=COMODO RSA Extended Validation Code Signing CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBАктивные
Frequent Visitor

@kevintremblay can you help us here?

Regular Visitor

We have a ticket open now and hopefully routed correctly.  Will update with what we hear.

Occasional Visitor

We are trying to reassociate our driver signing EV certificate but in Step 2 of the update-a-code-signing-certificate link, the Manage Certificates does not show up on the left pane after selecting "Sign and upload your File", or manually navigating to the page following these steps when logged in as Global Admin.

3. Select the gear icon in the upper right, then select Developer settings, then Manage Certificates on the left pane. 

Occasional Visitor

My company has the same problem now with the EV Certificate issued by Sectigo. It used to work perfectly before reassociation. However it was only reported as CodeSign Certificate after reassociation. We could not sign our driver any more.

 

Why is our EV certificate (COMODO RSA Extended Validation Code Signing Certificate) disqualified as EV certificate after reassociation? The ticket has been opened last week and we are still waiting for response. 

 

Since there are multiple reports now related to this COMODO RSA Extended Validation Code Signing Certificate, can Microsoft seriously investigate and solve the problem ASAP? Thanks

Frequent Visitor

Please can someone help me with the command line sintax....

 

how is the right command for sign the SignableFile.bin with SHA256 option?

 

signtool /sign ..................?

 

I have copy the SignableFile.bin and my Digicert .cer file in the same folder.

 

Regards

Regular Visitor

Command line should look something like this:

 

".\<PATH TO>\signtool.exe" sign /fd sha256 /v /debug /ac "<YOUR CERTIFICATE PATH AND NAME>" /t <http://<TIMESTAMP SERVER YOU ARE USING>> /n "<NAME CERT IS ASSIGNED TO>" <FILENAME TO BE SIGNED>

 

Frequent Visitor

Hi ChrisUniPrint,

in my case with the right command is:

 

signtool sign /tr TIME_STAMP_SERVER /td sha256 /fd sha256 /a "c:\path\to\file_to_sign.exe"

 

but I also need to change my token hardware becaue is only 2048bits and now it must be need at least 3072bits, I got this information from digicert support.

 

https://www.digicert.com/kb/code-signing/ev-authenticode-certificates.htm 

Occasional Visitor

I originally assigned the EV certificate to: "https://partner.microsoft.com/en-us/dashboard/account/managecertificates" v Certificate management canceled, I downloaded a new SignableFile.bin, I signed it with my valid Digicert EV certificate, I sent it and thus renewed it again in the Certificate list and I tried to send the submission with drivarpack. Everything went OK and the driver was signed. That was early October. To this day, I am "lit" with a warning "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" ". What does that mean?

Frequent Visitor

    Hello once more Microsoft Team!

 

    Any news about this problem?

 

    I see a lot of similar problems as my problem here. And see no answer for a lot of time. Also I have no answer for my ticket from tech support.

 

  It seems like Extended Validation Code Signing Certificates from COMODO and DigiCert are interpreted by DashBoard as NON Extended Validation.  So companies are not verified And we all can not sign our files.

 

Good Luck for ALL here,

Igor Arsenin

Frequent Visitor

Hi,

     We are also facing the same Issue, the hlkx file has been rejected while registering for signing.

So, after reading the Microsoft doc and following the procedure (https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/update-a-code-signing-certificat...). Now it is giving error as "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 here and read more about this policy here.".

It seems very confusing. Our code signing certificate is from COMODO

 

Due to this issue our company release is on hold.

 

If any one has any idea, kindly help us.

Regular Visitor

Hi Michele_Canini ,

 

  Thanks for that; I tried resubmitting with my cert and those options.  It was accepted but is still coming up as CodeSign and not EV.

 

 

Frequent Visitor

I have just been told by a contact I have who works for Microsoft that Microsoft have recently discovered that Comodo isn’t issuing properly formed certificates

 

Assuming this is correct I have asked Sectigo/Comodo for a corrected EV Certificate and plan to add a new comment once I have more information

 

I also gather that the Type needs to be reported as EV rather than CodeSign. Given this I feel Microsoft should reject SignableFile.bin files that result in a Type of CodeSign (other than EV?) as they will not work and accepting them just causes confusion.

 

Certificate list
Name               Thumbprint                                                                        Type         Expiration date Validated Date       Issuer Name Status Action
RH Software Ltd3AD34BFD2DAFF23F5C2B751501863D740B6AF6D5CodeSign1/28/202310/08/2021 09:32:41ZCN=COMODO RSA Extended Validation Code Signing CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GBActive

 

Frequent Visitor

Digicert also said me that now the token must be 3072 bits or more.... My is 2048bits and even if i can sign the certified as sha256, when I try to uplaod it the system reject it.

Frequent Visitor

It's interesting that the token must be >= 3072 bits given that MS WHQL sign with a 2048 bit certificate! I though this may be down to my driver being WHQL signed before 21-Sep-2021 on 15-Sep-2021, so I checked a driver signed on 03-Oct-2021 and that's also only using 2048 bits which makes me wonder if MS should fix their certificate.

 

MS only use 2048 bits.png

 

Occasional Visitor

Hi,


We recently purchased an EV certificate to sign our software kernel driver, however, when trying to load it in Windows 10 it fails with code 0x800B010C aka CERT_E_REVOKED - A certificate was explicitly revoked by its issuer.
We checked the driver with "signtool verify /v /all /pa" as suggested by our cert provider and everything is still valid and the cert provider also confirmed it didn't revoke our certificate.
We followed the instructions for attestation signing a kernel driver for public release yet the driver is not loading

 

We've also tried contacting Microsoft's dev support but MS closed it down recently and they're not replying anymore...

 

Any help would be appreciated,

Thanks!

Visitor

I have followed procedure to update Signable.bin with our certificate. Procedure was successful, however, I still get following error
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

Please suggest what needs to be done to get successful submission. 

Frequent Visitor
Farooq1979  from what you had specified I can't even guess, post your reported Certificate list as I did in https://techcommunity.microsoft.com/t5/hardware-dev-center/important-all-partners-must-reassociate-t... and I may be able to.
Regular Visitor

If you have a Sectigo/Comodo EV cert you should talk to them; the issue may be with your cert and they are aware of it now, although it may not apply to all certs they have issued.

Frequent Visitor

The last things MS specified to me is as below, at the moment I am half way through getting my EV Certificate reissued.

 

As per engineering: About the Comodo/Sectigo EV Certificate issue.

 

Sectigo confirms that the EV certs they issued prior to May 2020 were improperly formed. Partners impacted will need to contact Comodo/Sectigo to get a replacement certificate issued. Some EV certs issued prior to May 2020 are missing the EV CS OID and therefore they are failing validation as EV certificates, and the portal is showing them as codesign. This is not a bug on Microsoft’s side, this is an issue with the certificate itself.

 

So, we request you to please work directly with Comodo/Sectigo to get your EV cert reissued.

Occasional Visitor

Our company have a new digicert EV certificate, when i upload a SignableFile.bin, show a error just follow:

Sigen_0-1634273393524.png

my certificate has updated to SHA384, how can i resolve this issue, thanks.

 

Frequent Visitor

I have solve my issue, after have buy a new 4096bits token and ask to Digicert a certified reissue.

I have install the new token with the new certified and sucesufully upload the new SignableFile.bin.

After this I aslo do with success a new hardware submission.

 

 

Occasional Visitor

Will a Symantec EV cert still qualify or do we need a new certificate?

%3CLINGO-SUB%20id%3D%22lingo-sub-2770529%22%20slang%3D%22en-US%22%3EIMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2770529%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20recently%20made%20some%20changes%20to%20Partner%20Center%20for%20Windows%20Hardware.%20As%20a%20result%20of%20these%20changes%2C%20all%20participants%20in%20the%20hardware%20program%20are%20required%20to%20reassociate%20their%20valid%20signing%20certificates%20used%20when%20making%20submissions%20to%20Partner%20Center%20for%20Windows%20Hardware.%20As%20a%20part%20of%20this%20process%2C%20you%20will%20need%20to%20reassociate%20both%20your%20Extended%20Validation%20(EV)%20codesign%20certificate%2C%20and%20your%20Authenticode%20codesigning%20certificate%20(if%20applicable).%20You%20need%20to%20take%20action%20now%20as%20any%20new%20submissions%20are%20blocked%20until%20this%20reassociation%20occurs.%20Additionally%2C%20you%20will%20be%20unable%20to%20publish%20any%20new%20content%20to%20Windows%20Update%20until%20your%20signing%20certificates%20have%20been%20updated.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20check%20the%20necessary%20steps%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fupdate-a-code-signing-certificate%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAdd%20or%20update%20a%20code%20signing%20certificate%20-%20Windows%20drivers.%26nbsp%3B%20%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20encounter%20issues%20while%20trying%20to%20update%20the%20certificates%20registered%20to%20your%20account%2C%20please%20reach%20out%20to%20our%20support%20team.%20For%20details%20on%20how%20to%20contact%20support%2C%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fhardware-dashboard-faq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPartner%20Center%20FAQ%20-%20Windows%20drivers%20%7C%20Microsoft%20Docs%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2773014%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2773014%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20understand%20that%20the%20above%20info%20is%20regarding%20new%20submissions%20what%20about%20older%20submissions%20of%20drivers%20which%20already%20have%20been%20signed%20and%20refused%20by%20the%20Win10%20boot%20process%2C%20unless%20the%20secure%20boot%20is%20disabled%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2773331%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2773331%22%20slang%3D%22en-US%22%3E%3CP%3EEven%20after%20new%20signed%20file%20was%20uploaded%20notification%20still%20appear%3A%3CBR%20%2F%3E%3CSPAN%3EATTENTION%3A%20We%20recently%20made%20changes%20to%20signature%20validation%20on%20all%20Partner%20Center%20for%20Windows%20Hardware%20submissions.%20You%20must%20take%20action%20before%20you%20can%20create%20new%20submissions%2C%20or%20publications.%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fcert_revalidation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fcert_revalidation%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2773362%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2773362%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20sorry%20I%20do%20not%20understand.%20The%20Driver%20Hardware%20dashboard%20has%20prepared%20a%20signed%20driver%20upon%20submition%20a%20year%20ago.%20now%20I%20download%20the%20Microsoft%20signed%20driver%20but%20when%20I%20install%20it%20on%20a%20Win10%20station%20it%20does%20not%20load%2C%20unless%20I%20disable%20the%20secure%20boot.%20What%20should%20Io%20do%20next%3F%20resign%20the%20driver%3F%20it%20means%20that%20I%20need%20to%20purchase%20a%20new%20key.%20why%20was%20it%20changed%3F%20why%20an%20%22old%22%20driver%20is%20not%20acceptable%20as%20a%20signed%20driver%3F%3C%2FP%3E%3CP%3ERegards.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2787823%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2787823%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BOur%20registered%20Signable.bin%26nbsp%3B%20is%20singed%20with%20our%20effective%20digital%20certificate%20with%20SHA256%2C%20but%20new%20submission%20is%20blocked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20clarify%2C%20do%20we%20need%20just%20re-upload%20the%20Signable.bin%20to%20reassociate%3F%3C%2FP%3E%3CP%3EOr%20must%20we%20upload%20a%20new%20Signable.bin%20signed%20with%20the%20latest%20SignTool%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2787862%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2787862%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20uploaded%20a%20new%20certificate%20which%20is%20reported%20as%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CH5%20id%3D%22toc-hId--1445469997%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%20id%3D%22toc-hId--1446604103%22%3ECertificate%20list%3C%2FH5%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3ENameThumbprint%20Type%20Expiration%20date%20Validated%20Date%20Issuer%20Name%20Status%20Action%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3ERH%20Software%20Ltd%3C%2FTD%3E%3CTD%3E3AD34BFD2DAFF23F5C2B751501863D740B6AF6D5%3C%2FTD%3E%3CTD%3ECodeSign%3C%2FTD%3E%3CTD%3E1%2F28%2F2023%3C%2FTD%3E%3CTD%3E09%2F27%2F2021%2010%3A38%3A26Z%3C%2FTD%3E%3CTD%3ECN%3DCOMODO%20RSA%20Extended%20Validation%20Code%20Signing%20CA%2C%20O%3DCOMODO%20CA%20Limited%2C%20L%3DSalford%2C%20S%3DGreater%20Manchester%2C%20C%3DGB%3C%2FTD%3E%3CTD%3EActive%3C%2FTD%3E%3CTD%3E%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fpartner.microsoft.com%2Fen-us%2Fdashboard%2FAccount%2FManageCertificates%23%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERemove%3C%2FA%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20I%20am%20still%20unable%20to%20WHQL%20sign%20my%20driver%20and%20then%20I%20try%20I%20get%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%20class%3D%22%22%3EUnfortunately%20there%20is%20no%20valid%20EV%20certificate%20associated%20with%20your%20account.%20To%20make%20submissions%20to%20the%20Hardware%20Dev%20Center%2C%20your%20account%20needs%20to%20be%20verified%20with%20at%20least%20one%20EV%20certificate%20upload.%20You%20can%20upload%20a%20new%20certificate%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkId%3D829460%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%20read%20more%20about%20this%20policy%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkId%3D829459%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSPAN%20class%3D%22%22%3EAll%20was%20great%20when%20I%20signed%20my%20driver%20on%2016-Sep-2021%2C%20what%20needs%20to%20happen%20to%20make%20things%20start%20working%20again%20please%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2788514%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2788514%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EIf%20you%20encounter%20issues%20while%20trying%20to%20update%20the%20certificates%20registered%20to%20your%20account%2C%20please%20reach%20out%20to%20our%20support%20team.%20For%20details%20on%20how%20to%20contact%20support%2C%20see%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fhardware-dashboard-faq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPartner%20Center%20FAQ%20-%20Windows%20drivers%20%7C%20Microsoft%20Docs%3C%2FA%3E%3CSPAN%3E.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20requirement%20to%20associate%26nbsp%3Byour%20EV%20codesign%20certificate%2C%20and%20if%20used.%20Authenticode%20codesign%20certificates%20has%20no%20impact%20on%20the%20ability%20of%20your%20driver%20to%20be%20loaded%20by%20the%20OS.%20Submissions%20that%20have%20already%20been%20processed%20and%20signed%20by%20Microsoft%20will%20continue%20to%20function.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2793595%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2793595%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EDear%26nbsp%3Bkevintremblay%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20could%20not%20find%20the%20previous%20%3C%2FSPAN%3E%3CSPAN%3ESupport%20request%20number%20so%20have%20just%20submitted%20SR1529230915.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20can%20I%20list%20all%20the%26nbsp%3BSupport%20request%20numbers%20I%20have%20submitted%20please%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2799690%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2799690%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20problem.%20I%20have%20reassociated%20a%20signing%20certificate.%20And%20now%20receive%20an%20error%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EUnfortunately%20there%20is%20no%20valid%20EV%20certificate%20associated%20with%20your%20account.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1167546%22%20target%3D%22_blank%22%3E%40red-ray%3C%2FA%3E%26nbsp%3Bdid%20you%20solve%20this%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2799845%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2799845%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20also%20having%20the%20same%20problem%20as%20%3CSPAN%20class%3D%22%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1167546%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3Ered-ray%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E.%26nbsp%3B%20Ticket%20opened%20with%20MS%2C%20but%20what%20has%20changed%20to%20cause%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2800300%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2800300%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there!%3C%2FP%3E%3CP%3EOur%20company%20has%20been%20using%20an%20EV%20Code%20Signing%20Certificate%20issued%20by%20Sectigo%2C%20and%20we%20have%20recently%20noticed%20that%20it%20is%20no%20longer%20defined%20as%20an%20EV%20Certificate%20by%20you%2C%20but%20rather%20as%20a%20CodeSign%20certificate%2C%20for%20some%20reason%2C%20which%20prevents%20us%20from%20being%20able%20to%20sign%20our%20driver.%20Would%20you%20be%20able%20to%20tell%20us%20why%20this%20change%20from%20EV%20to%20CodeSign%20happened%20and%20what%20needs%20to%20be%20done%20to%20fix%20this%20issue%3F%3C%2FP%3E%3CP%3EWe%20hope%20to%20hear%20from%20you%20soon.%3C%2FP%3E%3CP%3EP.S.%20We're%20attaching%20our%20certificate%20to%20the%20enquiry.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2800317%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2800317%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Policy.png%22%20style%3D%22width%3A%20405px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F314029i9FD4536F0911C235%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Policy.png%22%20alt%3D%22Policy.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2803026%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2803026%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20also%20use%20the%20COMODO%20RSA%20%3CSTRONG%3EExtended%20Validation%3C%2FSTRONG%3E%20Code%20Signing%20CA.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2806606%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2806606%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CSPAN%3EWe%20also%20use%20the%20COMODO%20RSA%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EExtended%20Validation%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BCode%20Signing%20Certificate.%20I%20have%20uploaded%20a%20new%20certificate%20which%20is%20reported%20below%20in%20Certificate%20List.%20Still%20I%20can%20not%20submit%20my%20drivers%20for%20attestation%20signing.%20What%20is%20the%20problem%3F%20I%20NEED%20to%20SIGN%20new%20version%20of%20drivers.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%3ESignableFile.bin%20was%20signed%20with%20command%20line%20below.%20All%20options%20for%20sha256%20are%20used.%20What%20is%20wrong%3F%20Why%20type%20is%20%22CodeSign%22%20instead%20of%20%22EV%20CodeSign%22%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%3E%22C%3A%5CProgram%20Files%20(x86)%5CWindows%20Kits%5C10%5Cbin%5C10.0.17763.0%5Cx86%5Csigntool.exe%22%20sign%20%2Fs%20MY%20%2Fsha1%20%22ead1de2a8e66964d3ef1d80ea9c42af953a6fd32%22%20%2Fv%20%2Fd%20%22FDExt%20Software%22%20%2Fdu%20%22%3CA%20href%3D%22http%3A%2F%2Fwww.softlab-nsk.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.softlab-nsk.com%3C%2FA%3E%22%20%2Ftr%20%3CA%20href%3D%22http%3A%2F%2Ftimestamp.comodoca.com%2Frfc3161%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Ftimestamp.comodoca.com%2Frfc3161%3C%2FA%3E%20%2Ftd%20sha256%20%2Ffd%20sha256%26nbsp%3BSignableFile.bin%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20class%3D%22%22%3E%3CBR%20%2F%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%22OOO%20%22%22SoftLab-NSK%22%22%22%3C%2FTD%3E%3CTD%3EEAD1DE2A8E66964D3EF1D80EA9C42AF953A6FD32%3C%2FTD%3E%3CTD%3ECodeSign%3C%2FTD%3E%3CTD%3E01.12.2022%3C%2FTD%3E%3CTD%3E10.03.2021%2007%3A40%3A35Z%3C%2FTD%3E%3CTD%3ECN%3DCOMODO%20RSA%20Extended%20Validation%20Code%20Signing%20CA%2C%20O%3DCOMODO%20CA%20Limited%2C%20L%3DSalford%2C%20S%3DGreater%20Manchester%2C%20C%3DGB%3C%2FTD%3E%3CTD%3E%D0%90%D0%BA%D1%82%D0%B8%D0%B2%D0%BD%D1%8B%D0%B5%3C%2FTD%3E%3CTD%3E%3CDIV%3E%3CA%20href%3D%22https%3A%2F%2Fpartner.microsoft.com%2Fru-ru%2Fdashboard%2Faccount%2Fmanagecertificates%23%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%D0%A3%D0%B4%D0%B0%D0%BB%D0%B8%D1%82%D1%8C%3C%2FA%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2808095%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2808095%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299650%22%20target%3D%22_blank%22%3E%40kevintremblay%3C%2FA%3E%26nbsp%3Bcan%20you%20help%20us%20here%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2809198%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2809198%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20ticket%20open%20now%20and%20hopefully%20routed%20correctly.%26nbsp%3B%20Will%20update%20with%20what%20we%20hear.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2811511%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2811511%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20company%20has%20the%20same%20problem%20now%20with%20the%20EV%20Certificate%20issued%20by%20Sectigo.%20It%20used%20to%20work%20perfectly%20before%20reassociation.%20However%20it%20was%20only%20reported%20as%20CodeSign%20Certificate%20after%20reassociation.%20We%20could%20not%20sign%20our%20driver%20any%20more.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20is%20our%20EV%20certificate%20(%3CSPAN%3ECOMODO%20RSA%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EExtended%20Validation%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BCode%20Signing%20Certificate)%20disqualified%20as%20EV%20certificate%20after%20reassociation%3F%20The%20ticket%20has%20been%20opened%20last%20week%20and%20we%20are%20still%20waiting%20for%20response.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESince%20there%20are%20multiple%20reports%20now%20related%20to%20this%26nbsp%3BCOMODO%20RSA%26nbsp%3B%3CSTRONG%3EExtended%20Validation%3C%2FSTRONG%3E%26nbsp%3BCode%20Signing%20Certificate%2C%20can%20Microsoft%20seriously%20investigate%20and%20solve%20the%20problem%20ASAP%3F%20Thanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2809736%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2809736%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20trying%20to%20reassociate%20our%20driver%20signing%20EV%20certificate%20but%20in%20Step%202%20of%26nbsp%3Bthe%20update-a-code-signing-certificate%20link%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fupdate-a-code-signing-certificate%2C%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%2C%3C%2FA%3E%26nbsp%3Bthe%26nbsp%3B%3CSTRONG%3EManage%20Certificates%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Bdoes%20not%20show%20up%20on%20the%20left%20pane%20after%20selecting%20%22Sign%20and%20upload%20your%20File%22%3C%2FSPAN%3E%2C%20or%20manually%20navigating%20to%20the%20page%20following%20these%20steps%20when%20logged%20in%20as%20Global%20Admin.%3C%2FP%3E%3CP%3E3.%20Select%20the%20gear%20icon%20in%20the%20upper%20right%2C%20then%20select%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EDeveloper%20settings%3C%2FSTRONG%3E%2C%20then%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EManage%20Certificates%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eon%20the%20left%20pane.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2813770%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813770%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20can%20someone%20help%20me%20with%20the%20command%20line%20sintax....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehow%20is%20the%20right%20command%20for%20sign%20the%26nbsp%3BSignableFile.bin%20with%20SHA256%20option%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3Esigntool%20%2Fsign%20..................%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20copy%20the%26nbsp%3BSignableFile.bin%20and%20my%20Digicert%20.cer%20file%20in%20the%20same%20folder.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2813897%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2813897%22%20slang%3D%22en-US%22%3E%3CP%3ECommand%20line%20should%20look%20something%20like%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22.%5C%3CPATH%20to%3D%22%22%3E%5Csigntool.exe%22%20sign%20%2Ffd%20sha256%20%2Fv%20%2Fdebug%20%2Fac%20%22%3CYOUR%20certificate%3D%22%22%20path%3D%22%22%20and%3D%22%22%20name%3D%22%22%3E%22%20%2Ft%20%26lt%3B%26gt%3B%26gt%3B%20%2Fn%20%22%3CNAME%20cert%3D%22%22%20is%3D%22%22%20assigned%3D%22%22%20to%3D%22%22%3E%22%20%3CFILENAME%20to%3D%22%22%20be%3D%22%22%20signed%3D%22%22%3E%3C%2FFILENAME%3E%3C%2FNAME%3E%3C%2FYOUR%3E%3C%2FPATH%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2816380%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2816380%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20ChrisUniPrint%2C%3C%2FP%3E%3CP%3Ein%20my%20case%20with%20the%20right%20command%20is%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Esigntool%20sign%20%2Ftr%20TIME_STAMP_SERVER%20%2Ftd%20sha256%20%2Ffd%20sha256%20%2Fa%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E%22c%3A%5Cpath%5Cto%5Cfile_to_sign.exe%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20I%20also%20need%20to%20change%20my%20token%20hardware%20becaue%20is%20only%202048bits%20and%20now%20it%20must%20be%20need%20at%20least%203072bits%2C%20I%20got%20this%20information%20from%20digicert%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.digicert.com%2Fkb%2Fcode-signing%2Fev-authenticode-certificates.htm%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.digicert.com%2Fkb%2Fcode-signing%2Fev-authenticode-certificates.htm%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2816437%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2816437%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%3EI%20originally%20assigned%20the%20EV%20certificate%20to%3A%3C%2FSPAN%3E%3C%2FSPAN%3E%26nbsp%3B%22%3CSPAN%20class%3D%22%22%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fpartner.microsoft.com%2Fen-us%2Fdashboard%2Faccount%2Fmanagecertificates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpartner.microsoft.com%2Fen-us%2Fdashboard%2Faccount%2Fmanagecertificates%22%3C%2FA%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22%22%3E%3CSPAN%3Ev%20Certificate%20management%20canceled%2C%20I%20downloaded%20a%20new%20SignableFile.bin%2C%20I%20signed%20it%20with%20my%20valid%20Digicert%20EV%20certificate%2C%20I%20sent%20it%20and%20thus%20renewed%20it%20again%20in%20the%20Certificate%20list%20and%20I%20tried%20to%20send%20the%20submission%20with%20drivarpack.%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22%22%3E%3CSPAN%3EEverything%20went%20OK%20and%20the%20driver%20was%20signed.%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22%22%3E%3CSPAN%3EThat%20was%20early%20October.%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22%22%3E%3CSPAN%3ETo%20this%20day%2C%20I%20am%20%22lit%22%20with%20a%20warning%20%22ATTENTION%3A%20We%20recently%20made%20changes%20to%20signature%20validation%20on%20all%20Partner%20Center%20for%20Windows%20Hardware%20submissions.%20You%20must%20take%20action%20before%20you%20can%20create%20new%20submissions%2C%20or%20publications.%20%22%3CA%20href%3D%22Https%3A%2F%2Faka.ms%2Fcert_revalidation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EHttps%3A%2F%2Faka.ms%2Fcert_revalidation%22%3C%2FA%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22%22%3E%3CSPAN%3E%22.%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22%22%3E%3CSPAN%3EWhat%20does%20that%20mean%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2816575%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2816575%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Hello%20once%20more%20Microsoft%20Team!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Any%20news%20about%20this%20problem%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20I%20see%20a%20lot%20of%20similar%20problems%20as%20my%20problem%20here.%20And%20see%20no%20answer%20for%20a%20lot%20of%20time.%20Also%20I%20have%20no%20answer%20for%20my%20ticket%20from%20tech%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20It%20seems%20like%26nbsp%3B%3CSTRONG%3EExtended%20Validation%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BCode%20Signing%20Certificate%3C%2FSPAN%3Es%20from%20COMODO%20and%20DigiCert%20are%20interpreted%20by%20DashBoard%20as%20%3CSTRONG%3ENON%3C%2FSTRONG%3E%20%3CSTRONG%3EExtended%20Validation.%26nbsp%3B%20So%20companies%20are%20not%20verified%20And%20we%20all%20can%20not%20sign%20our%20files.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EGood%20Luck%20for%20ALL%20here%2C%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EIgor%20Arsenin%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2816800%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2816800%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BWe%20are%20also%20facing%20the%20same%20Issue%2C%20the%20hlkx%20file%20has%20been%20rejected%20while%20registering%20for%20signing.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%2C%20after%20reading%20the%20Microsoft%20doc%20and%20following%20the%20procedure%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fupdate-a-code-signing-certificate%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fupdate-a-code-signing-certificate%3C%2FA%3E).%20Now%20it%20is%20giving%20error%20as%20%22Unfortunately%20there%20is%20no%20valid%20EV%20certificate%20associated%20with%20your%20account.%20To%20make%20submissions%20to%20the%20Hardware%20Dev%20Center%2C%20your%20account%20needs%20to%20be%20verified%20with%20at%20least%20one%20EV%20certificate%20upload.%20You%20can%20upload%20a%20new%20certificate%20here%20and%20read%20more%20about%20this%20policy%20here.%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20seems%20very%20confusing.%20Our%20code%20signing%20certificate%20is%20from%20COMODO%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EDue%20to%20this%20issue%20our%20company%20release%20is%20on%20hold.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20any%20one%20has%20any%20idea%2C%20kindly%20help%20us.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2822112%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2822112%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CSPAN%20class%3D%22%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1175889%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3EMichele_Canini%20%2C%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%20class%3D%22%22%3E%26nbsp%3B%20Thanks%20for%20that%3B%20I%20tried%20resubmitting%20with%20my%20cert%20and%20those%20options.%26nbsp%3B%20It%20was%20accepted%20but%20is%20still%20coming%20up%20as%20CodeSign%20and%20not%20EV.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2826140%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2826140%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20just%20been%20told%20by%20a%20contact%20I%20have%20who%20works%20for%20Microsoft%20that%26nbsp%3B%3CSTRONG%3EMicrosoft%20have%26nbsp%3Brecently%20discovered%20that%20Comodo%20isn%E2%80%99t%20issuing%20properly%20formed%20certificates%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAssuming%20this%20is%20correct%20I%20have%20asked%20Sectigo%2FComodo%20for%20a%20corrected%20EV%20Certificate%20and%20plan%20to%20add%20a%20new%20comment%20once%20I%20have%20more%20information%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2793571%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2793571%22%20slang%3D%22en-US%22%3E%3CP%3EDear%26nbsp%3Bkevintremblay%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20post.%20I%20have%20read%26nbsp%3B%3CSPAN%3E%26nbsp%3Bsee%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fhardware-dashboard-faq%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPartner%20Center%20FAQ%20-%20Windows%20drivers%20%7C%20Microsoft%20Docs%3C%2FA%3E%3CSPAN%3E%26nbsp%3B(several%20times)%20and%20it%20does%20not%20address%20the%20issue%20I%20have%20that%20I%20have%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fhardware-dev-center%2Fimportant-all-partners-must-reassociate-their-signing%2Fba-p%2F2770529%22%20target%3D%22_blank%22%3Ereassociated%20my%20signing%20certificate%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Eseveral%20times%20and%20I%20still%20get%20the%20%22Unfortunately%20there%20is%20no%20valid%20EV%20certificate%20associated%20with%20your%20account%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20reached%20out%20to%20your%20support%20team%20via%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-gb%2Fwindows%2Fhardware%2Fsupport%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.microsoft.com%2Fen-gb%2Fwindows%2Fhardware%2Fsupport%2F%3C%2FA%3E%26nbsp%3Band%20thus%20far%20I%20have%20not%20had%20a%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20the%20driver%20I%20signed%2016-Sep-2021%20still%20works%2C%20but%20I%20made%20a%20change%20to%20my%20driver%20on%2023-Sep-2021%20and%20need%20to%20use%20that%20driver%20on%20my%20Windows%2011%20systems.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2826372%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2826372%22%20slang%3D%22en-US%22%3E%3CP%3EDigicert%20also%20said%20me%20that%20now%20the%20token%20must%20be%203072%20bits%20or%20more....%20My%20is%202048bits%20and%20even%20if%20i%20can%20sign%20the%20certified%20as%20sha256%2C%20when%20I%20try%20to%20uplaod%20it%20the%20system%20reject%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2827190%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2827190%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20interesting%20that%20the%20token%20must%20be%20%26gt%3B%3D%203072%20bits%20given%20that%20MS%20WHQL%20sign%20with%20a%202048%20bit%20certificate!%20I%20though%20this%20may%20be%20down%20to%20my%20driver%20being%20WHQL%20signed%20before%2021-Sep-2021%20on%2015-Sep-2021%2C%20so%20I%20checked%20a%20driver%20signed%20on%2003-Oct-2021%20and%20that's%20also%20only%20using%202048%20bits%20which%20makes%20me%20wonder%20if%20MS%20should%20fix%20their%20certificate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22MS%20only%20use%202048%20bits.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F316210i8D9BC3FE74448FE0%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22MS%20only%20use%202048%20bits.png%22%20alt%3D%22MS%20only%20use%202048%20bits.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2842350%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2842350%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20recently%20purchased%20an%20EV%20certificate%20to%20sign%20our%20software%20kernel%20driver%2C%20however%2C%20when%20trying%20to%20load%20it%20in%20Windows%2010%20it%20fails%20with%20code%200x800B010C%20aka%20CERT_E_REVOKED%20-%20A%20certificate%20was%20explicitly%20revoked%20by%20its%20issuer.%3CBR%20%2F%3EWe%20checked%20the%20driver%20with%20%22signtool%20verify%20%2Fv%20%2Fall%20%2Fpa%22%20as%20suggested%20by%20our%20cert%20provider%20and%20everything%20is%20still%20valid%20and%20the%20cert%20provider%20also%20confirmed%20it%20didn't%20revoke%20our%20certificate.%3CBR%20%2F%3EWe%20followed%20the%20instructions%3CSPAN%3E%26nbsp%3Bfor%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fattestation-signing-a-kernel-driver-for-public-release%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eattestation%20signing%20a%20kernel%20driver%20for%20public%20release%3C%2FA%3E%26nbsp%3Byet%20the%20driver%20is%20not%20loading%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20also%20tried%20contacting%20Microsoft's%20dev%20support%20but%20MS%20closed%20it%20down%20recently%20and%20they're%20not%20replying%20anymore...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20appreciated%2C%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2800778%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2800778%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1171551%22%20target%3D%22_blank%22%3E%40danshov%3C%2FA%3E%26nbsp%3BI%20have%20the%20same%20problem.%20The%20certificate%20is%20called%26nbsp%3B%22COMODO%20RSA%20%3CSTRONG%3EExtended%20Validation%3C%2FSTRONG%3E%20Code%20Signing%20CA%22.%3C%2FP%3E%3CDIV%3EBut%20in%20certificate%20list%20Microsoft%20marked%20it%20as%20Codesign%20instead%20of%20EV.%20Previously%20we%20used%20it%20many%20times%20to%20receive%20a%20driver%20signature.%20It%20stopped%20working%20after%20cerificate%26nbsp%3B%3CSPAN%3Ereassociation.%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2845862%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2845862%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20followed%20procedure%20to%20update%20Signable.bin%20with%20our%20certificate.%20Procedure%20was%20successful%2C%20however%2C%20I%20still%20get%20following%20error%3CBR%20%2F%3E%3CSPAN%3EATTENTION%3A%20We%20recently%20made%20changes%20to%20signature%20validation%20on%20all%20Partner%20Center%20for%20Windows%20Hardware%20submissions.%20You%20must%20take%20action%20before%20you%20can%20create%20new%20submissions%2C%20or%20publications.%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fcert_revalidation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fcert_revalidation%3C%2FA%3E%3C%2FP%3E%3CP%3EPlease%20suggest%20what%20needs%20to%20be%20done%20to%20get%20successful%20submission.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2846268%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2846268%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20have%20a%20Sectigo%2FComodo%20EV%20cert%20you%20should%20talk%20to%20them%3B%20the%20issue%20may%20be%20with%20your%20cert%20and%20they%20are%20aware%20of%20it%20now%2C%20although%20it%20may%20not%20apply%20to%20all%20certs%20they%20have%20issued.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2847260%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2847260%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20last%20things%20MS%20specified%20to%20me%20is%20as%20below%2C%20at%20the%20moment%20I%20am%20half%20way%20through%20getting%20my%20EV%20Certificate%20reissued.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3EAs%20per%20engineering%3A%20About%20the%20Comodo%2FSectigo%20EV%20Certificate%20issue.%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3ESectigo%20confirms%20that%20the%20EV%20certs%20they%20issued%20prior%20to%20May%202020%20were%20improperly%20formed.%20Partners%20impacted%20will%20need%20to%20contact%20Comodo%2FSectigo%20to%20get%20a%20replacement%20certificate%20issued.%20Some%20EV%20certs%20issued%20prior%20to%20May%202020%20are%20missing%20the%20EV%20CS%20OID%20and%20therefore%20they%20are%20failing%20validation%20as%20EV%20certificates%2C%20and%20the%20portal%20is%20showing%20them%20as%20codesign.%20This%20is%20not%20a%20bug%20on%20Microsoft%E2%80%99s%20side%2C%20this%20is%20an%20issue%20with%20the%20certificate%20itself.%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3ESo%2C%20we%20request%20you%20to%20please%20work%20directly%20with%26nbsp%3BComodo%2FSectigo%20to%20get%20your%20EV%20cert%20reissued.%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2848713%22%20slang%3D%22zh-CN%22%3EReply%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2848713%22%20slang%3D%22zh-CN%22%3E%3CP%3EOur%20company%20have%20a%20new%20digicert%20EV%20certificate%2C%20when%20i%20upload%20a%26nbsp%3BSignableFile.bin%2C%20show%20a%20error%20just%20follow%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Sigen_0-1634273393524.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317579i9FE60C9C6C775E11%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Sigen_0-1634273393524.png%22%20alt%3D%22Sigen_0-1634273393524.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Emy%20certificate%20has%20updated%20to%20SHA384%2C%20how%20can%20i%20resolve%20this%20issue%2C%20thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2849947%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2849947%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20solve%20my%20issue%2C%20after%20have%20buy%20a%20new%204096bits%20token%20and%20ask%20to%20Digicert%20a%20certified%20reissue.%3C%2FP%3E%3CP%3EI%20have%20install%20the%20new%20token%20with%20the%20new%20certified%20and%20sucesufully%20upload%20the%20new%26nbsp%3B%3CSPAN%3ESignableFile.bin.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAfter%20this%20I%20aslo%20do%20with%20success%20a%20new%20hardware%20submission.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2851075%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2851075%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20a%20Symantec%20EV%20cert%20still%20qualify%20or%20do%20we%20need%20a%20new%20certificate%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2845951%22%20slang%3D%22en-US%22%3ERe%3A%20IMPORTANT%3A%20All%20Partners%20must%20reassociate%20their%20signing%20certificates!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2845951%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CSPAN%20class%3D%22%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1182816%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3EFarooq1979%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Efrom%20what%20you%20had%20specified%20I%20can't%20even%20guess%2C%20post%20your%20reported%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3ECertificate%20list%20as%20I%20did%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fhardware-dev-center%2Fimportant-all-partners-must-reassociate-their-signing%2Fbc-p%2F2826140%2Fhighlight%2Ftrue%23M90%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fhardware-dev-center%2Fimportant-all-partners-must-reassociate-their-signing%2Fbc-p%2F2826140%2Fhighlight%2Ftrue%23M90%3C%2FA%3E%20and%20I%20may%20be%20able%20to.%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Sep 21 2021 07:49 AM
Updated by: