So my company has purchased an EV code signing certificate from DigiCert to load our drivers on Windows 10 14939. Unfortunately, every time I attempt to submit it to the Microsoft Hardware Dev Center, it gets to Step 6/10 and then gets stuck. I have tried this at least 5 times with different drivers and it always gets stuck at 6/10. The last time I submitted was on 10/30 and it has not moved since then.
Does anybody know what’s up?
xxxxx@platinumdigitalgroup.net wrote:
So my company has purchased an EV code signing certificate from DigiCert to load our drivers on Windows 10 14939. Unfortunately, every time I attempt to submit it to the Microsoft Hardware Dev Center, it gets to Step 6/10 and then gets stuck. I have tried this at least 5 times with different drivers and it always gets stuck at 6/10. The last time I submitted was on 10/30 and it has not moved since then.
Does anybody know what’s up?
Generally, that indicates that your package was inadequate in some way.
You skipped a few steps there, so just let me verify. Did you create
your sysdev account using your new EV certificate? You’ve gone through
all of the agreements and signatures?
When you create the package for submission, remember that you cannot
just put the files in the root of the cabinet. The files must be
contained in a top-level directory. The examples use “DriverPackage1”,
but in fact you can call it anything. And you’ve checked that the INF
file passes chkinf?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Yeah, I had a similar problem and it turned out to be an .inf format
problem. I e-mailed the sysdev e-mail from the site, and it took a few days
but they got back to me and told me specifically what was going on.
This is a problem with the way the submission process is implemented by Microsoft. When something is not well formed, as opposed to detecting this and giving you informational feedback, it just hangs in one of the steps. To be fair, that’s not always true – I have seen cases where I did get an informative message that helped me fix the problem, but more often than not it hung. At least they should be noting all these hangs and adding specific tests and feedback for the cases that cause these hangs.
But, yes, for now send an email to sysdev to have them explain the nature of the hang. If nothing else, forcing them to check manually should encourage Microsoft to make this work better.
Eric
Jeremy Hurren wrote:
> Yeah, I had a similar problem and it turned out to be an .inf format
> problem. I e-mailed the sysdev e-mail from the site, and it took a few days
> but they got back to me and told me specifically what was going on.?
Same here. What we learned from that process was that Microsoft
SysDev is using INF2CAT to generate the .CAT they intend to sign.
So one thing that can be done pre-submission is to run INF2CAT against
the .INF you’re about to submit, even though you don’t need to send a
.CAT with the driver set being uploaded. (At least not for the
attestation signing process.)
Because if INF2CAT doesn’t work for you pre-submission, it’s not going
to work for Microsoft either. We had several syntax conventions in
our long-standing product .INF which worked for actual installation on
all the target platforms, but were not accepted by INF2CAT.
Alan Adams
Client for Open Enterprise Server
Micro Focus
xxxxx@microfocus.com