Driver Signing Fails at end scan phase

NTDEV
1

While submitting drivers I am suddenly getting this error:

Scanning Notes
{"code":"4001","details":{"errorInfo":"BlockingDetectionFound"},"innerError":null}

Our EV certificate is good. Packages I submitted before (.cab) fail.
I resubmitted the signableFile.bin with the EV certificate on the Hardware signing site. No change.

I tried signing a small driver from the Windows-driver-samples-master\usb\kmdf_enumswitches and submitting the .cab package.
It fails exactly the same way.

When asking for tech support I found this message:

We were unable to find an eligible support plan associated with your account. Please add a support plan from the options below.

You are currently signed in using an Azure Active Directory account. The purchase of Professional Support plans must be made using a Microsoft Account. To learn more about this process, please click here.

What I need is the easiest way to resolve the problem. I am helping you can tell us what to try.

2

With a lot of help from IT we came up with a solution that worked.
Needed the sample usb driver to figure it out because it is small.
Seems we needed sha384 and removed the coinitializer.dll we always shipped with.
OSR thank you for your site.
I was doing a lot of reading here on your site.

Jamie

3 Likes
3

Hi Jamie

We are experiencing the same issue as you described, and we are still unable to get our drivers signed. This problem started occurring in 2nd June.

We have already tried submitting the Windows driver example, but it still fails the signing process.

Could you please provide more details on how you resolved this issue?
Additionally, could you clarify whether you used the SHA384 signing method or another approach?

Thank you for your assistance.

4

Hi guys,
I've encountered the exact same issue as you.
Even when I re-upload the package that passed before, it still reports the same error now.

I'm really looking forward to hearing from you about the specific solution.

Thanks

5

Same issue.

Currently the problem we found is related to 2 conditions:

  1. PnpLockDown should set to 1 in .inf file
  2. Our driver is shipped with VMProtect packer, the signing process will success if without this packer.
1 Like
6

Hi Hacksign

Has your issue been resolved?

Regarding the two points you mentioned, both are correctly configured in our driver:

  1. pnplockdown=1
  2. No VMProtect packer added

Moreover, the same driver cannot be signed with my account, but can be signed successfully with other accounts.

Since when have you been experiencing this issue?
Are there any other ways to resolve it?

Thank you.

7

Has your issue been resolved?

Yes it is solved, sort of ... but not the way we want ;(

The same driver cannot be signed with my account, but can be signed successfully with other accounts.

I have only one account, cant tell any usefull information ...

BTW: I've created an issue at github: microsoft/Windows-driver-samples

8

Hi Hacksign

I just saw your issue submission on GitHub when I was about to submit mine.

I haven't found a solution yet.
We have tried the following methods, but still couldn't pass the signature process.

  1. Reinstall the operating system and set up the latest build environment.
  2. Reinstall the latest HLK environment.
  3. Rerun the HLK tests.
  4. Used the driver from the Windows driver examples.

Could you share your solution, or a workaround method if you have one?

Thx
BR.