Registration to hardware development program fails to upload SignableFile.bin

Question

Registration to hardware development program fails to upload SignableFile.bin

Alejandro Villarreal 10

When I try to register to Hardware Development Program the upload of the SignableFile.bin always fails, here is what I do and see:

Download the SignableFile.bin
I sign this file with my EV Certificate
I try to upload the file and I get this error message:

We encountered a problem processing the file you uploaded. Please ensure the file you sign and upload is the same file you downloaded.
Correlation ID a5ab1afc-9d5e-4dba-a3f3-dd7a95f47111,JRAPkUSP2kqQlzhj.0.

On the Console of the browser I see:
POST https://partner.microsoft.com/en-US/dashboard/Registration/Hardware/HardwareRegistrationCertificateCheck 500

o @ partner.min.js:1

XMLHttpRequest.send @ ai.min.js:1

send @ jquery-2.1.1.min.js:4

ajax @ jquery-2.1.1.min.js:4

PostForm @ Hardware?step=SignUpload:671

OnChange @ Hardware?step=SignUpload:714

onchange @ Hardware?step=SignUpload:797

Seems to me the server is failing with an unexpected error and returns a 500.

This is urgent I need to be able to register to sign my drivers!

Alejandro Villarreal 10 Reputation points

2023-05-19T16:54:21.0933333+00:00

I tried incognito, several browsers, clearing cache, nothing works
Alejandro Villarreal 10 Reputation points

2023-05-19T16:55:04.15+00:00

Is there any other way to get registered or a phone number to call for support or registration?
Alejandro Villarreal 10 Reputation points

2023-06-29T15:19:20.6333333+00:00

My problem was that I had and old key from DigiCert that only supports a public key of 384 bits. I requested a new certificate from DigiCert for driver signing (didn't get new key) and I installed it in my key, at first I couldn't I had to talk to support and they gave me a work around to make it work. I was ready to go but I was still failing registration after a lot of conversations with support of DigiCert they told me the size of my new public key is 4096 bits so it wont fit on my old key so I requested a new one, install it there and everything worked fine after that.

5 answers

Your answer

Alejandro Villarreal 10 Reputation points

2023-05-19T16:54:21.0933333+00:00

I tried incognito, several browsers, clearing cache, nothing works
Alejandro Villarreal 10 Reputation points

2023-05-19T16:55:04.15+00:00

Is there any other way to get registered or a phone number to call for support or registration?
Alejandro Villarreal 10 Reputation points

2023-06-29T15:19:20.6333333+00:00

My problem was that I had and old key from DigiCert that only supports a public key of 384 bits. I requested a new certificate from DigiCert for driver signing (didn't get new key) and I installed it in my key, at first I couldn't I had to talk to support and they gave me a work around to make it work. I was ready to go but I was still failing registration after a lot of conversations with support of DigiCert they told me the size of my new public key is 4096 bits so it wont fit on my old key so I requested a new one, install it there and everything worked fine after that.

Answer 1

Final Answer

On the webpage

https://partner.microsoft.com/en-us/dashboard/Registration/Hardware?step=SignUpload

I also got the error message:

We encountered a problem processing the file you uploaded. Please ensure the file you sign and upload is the same file you downloaded.

In the end, I signed my file wrongly.

My main problem was that the /ac commandline parameter was missing.

The command that worked for me for signing the file SignableFile.bin is

signtool.exe sign /v /fd sha256 /ac "<PATH TO ROOT CERTIFICATE G2 .cer FILE>" /s my /n "<ISSUED TO NAME OF YOUR USER CERT>" /t http://timestamp.digicert.com .\SignableFile.bin

Good luck to any future reader

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

brunnerelektronik 5

Greetings

We have the same problem.

On registering as hardware partner when signing the test file SignableFile.bin the uploaded file is rejected.

https://partner.microsoft.com/en-us/dashboard/Registration/Hardware?step=SignUpload

We can sign the file using the following commandline:

signtool.exe sign /tr http://timestamp.digicert.com /td sha256 /fd sha256 /n "<ISSUED TO NAME HERE>" .\SignableFile.bin

But the Registration website rejects the file with the following error message:

User's image

Anonymous

2023-07-11T02:13:10.7066667+00:00

Hi @brunnerelektronik

I was got same error as you, but I'm not sure about the ID. I can solve the issue by using signtool.exe that provided in windows SDK from link no 2.
brunnerelektronik 5 Reputation points

2023-07-13T12:16:02.04+00:00

Hi Eko

Downloaded newest SDK and tried again, no success.

Can you post the exact command line you used to sign?

We used

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\signtool.exe" sign /tr http://timestamp.digicert.com /td sha256 /fd sha256 /n "<ENTER SIGNEE NAME>" .\SignableFile.bin
Anonymous

2023-07-18T06:29:01.02+00:00

Hi @brunnerelektronik

I used this command "Signtool sign /v /fd sha256 /ac "Certificate-Name" /s my /n "Publisher-Name" /t http://timestamp.digicert.com ItemsToSign*

ItemToSign is my directory to store what file that need to sign.

I hope that can solve your problem.
Diego Bürgin 0 Reputation points

2023-07-20T14:12:20.2633333+00:00

Thanks Eko!

This solved it!

After your comment I read here:

https://stackoverflow.com/questions/6575424/how-to-include-entire-certification-path-when-signing-code-with-signtool

Then i used this command:

signtool.exe sign /v /fd sha256 /ac "<PATH TO ROOT CERTIFICATE G2 .cer FILE>" /s my /n "<ISSUED TO NAME OF YOUR USER CERT>" /t http://timestamp.digicert.com .\SignableFile.bin

Answer 4

Rainer Weg 5

Hi, we have the dame issue since months. @Limitless Technology the problem is even before uploading a driver. It is while the registration process, where you download a SignableFile.bin --> sign it --> and upload it again, then this error message is shown "We encountered a problem processing the file you uploaded. Please ensure the file you sign and upload is the same file you downloaded."

Anonymous

2023-06-28T01:48:24.0066667+00:00

Hi @Rainer Weg and @Limitless Technology ,

Are you find any solution through this problem? i got same issue since last month and still not find anything about this case. Please share here if you got solution or answer about this issue. Thank you so much
Alejandro Villarreal 10 Reputation points

2023-06-29T15:18:29.48+00:00

My problem was that I had and old key from DigiCert that only supports a public key of 384 bits. I requested a new certificate from DigiCert for driver signing (didn't get new key) and I installed it in my key, at first I couldn't I had to talk to support and they gave me a work around to make it work. I was ready to go but I was still failing registration after a lot of conversations with support of DigiCert they told me the size of my new public key is 4096 bits so it wont fit on my old key so I requested a new one, install it there and everything worked fine after that.

Answer 5

Limitless Technology 45,241

Hello there,

You may need to verify that it has been signed correctly first.

Right click the *.sys file of the driver and check the digital signatures tab. You can check the details of the signature there.

Please follow the steps from the below link https://answers.microsoft.com/en-us/windows/forum/all/upload-signablefilebin-failed-during-hardware-dev/c4fb5c43-5e9a-4196-b711-3b1822fc5697

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

0 comments

Share via

Registration to hardware development program fails to upload SignableFile.bin

5 answers

Your answer