Inf-only driver update - Is this process correct?

NTDEV
1

Hi all,

I'm new to this process. I need to submit a inf-only (inf+cat, usbser) driver replacement which has a couple of added VID/PID's.

I've read through the MS docs on the process, but its VERY hard to follow, especially as (as far as ive been told), inf-only driver submissions are different to kernel mode driver submissions.

Do i have the process correct here?

  • generate the cat with Inf2Cat
  • signing the new CAT with signtool
  • open the old signed Shell_xxx HLKX with HLK Studio as a replacement, selecting the new inf+cat, then create the package and sign with the digicert EV certificate
  • submit the new HLKX for test signing
  • submit for deployment

Thanks!

2

INF-only driver packages are no different from a full driver package. They just don't happen to have a .SYS file.

Are you hoping to modify your old HLKX file without running the HLK testing again? I'm not sure that's possible.

What you're asking seems like a good candidate for attestation signing. If you submit for attestation, you don't actually have to generate a CAT. You can create a CAB file with the INF (in a subdirectory), and submit that. Microsoft will generate a new signed CAT for you.

1 Like
3

Thanks for your reply.

We do publish our inf-only driver on Windows Update, so it doesn't sound like attestation signing is useful to us?

Attestation signing has the following restrictions and requirements:

  • Attestation signed drivers can't be published to Windows Update for retail audiences
4

Yes, you are correct.