Windows Driver Signing: Getting a Driver Installed on Customer PCs

On a development machine you can enable test signing and load almost anything. Customer PCs are different. Since Windows 10 version 1607, new kernel-mode drivers must be signed by Microsoft through the Hardware Dev Center to load on systems with Secure Boot enabled, and a vendor certificate alone is not enough. There are two main routes to that signature.

At a glance

1607
The Windows 10 release from which new kernel-mode drivers need a Microsoft signature.
EV cert
Registering for the hardware program has required an extended validation certificate; check current rules.
HLK
The Hardware Lab Kit, whose test results support a compatibility submission.
.cat
The catalog file whose signature covers every file in the driver package.

The problem

The usual surprise comes late: the driver is finished, the test machine has test signing enabled, and the first customer install fails because the package carries only a test or vendor signature. Getting a production signature then means account registration, certificate purchase and possibly a full test pass, none of which is quick.

A second surprise is security features. Memory integrity, also called hypervisor-protected code integrity, is enabled on many current Windows 11 systems and blocks drivers that are not compatible with it, so a correctly signed driver can still fail to load.

Signing is part of the driver design, not a step after it, so choose the route on day one.

Attestation or compatibility testing

Attestation signing is the quicker route. You submit the driver package to the Hardware Dev Center and Microsoft signs it without requiring HLK results. It covers Windows 10 and Windows 11 client editions but not Windows Server, and the driver does not gain Windows compatibility status.

A Windows Hardware Compatibility Program submission requires running the HLK tests for the device type and submitting the results. It takes more effort, but it covers Windows Server where needed, qualifies the driver for the compatibility program and widens the options for distribution through Windows Update. Rules change, so check current Partner Center guidance.

What good looks like

Register a Partner Center hardware program account and obtain the certificate it requires well before the driver is finished.

Choose between attestation and an HLK-tested submission from the Windows editions you must support and whether compatibility status matters to your customers.

Test the signed package on a clean machine with Secure Boot and memory integrity enabled, installed as a customer would.

Route to a production signature

  1. Build: Driver package with INF and catalog
  2. Sign: Your certificate on the submission
  3. Test: HLK pass, compatibility route only
  4. Submit: Hardware Dev Center
  5. Distribute: Installer or Windows Update
The test stage applies only to compatibility program submissions.
Attestation and HLK-tested submission
AttestationHLK-tested (WHCP)
Testing effortNo HLK run requiredFull HLK pass for the device type
Windows ServerNot coveredCovered
Compatibility programNot includedIncluded
Time to first signatureShorterLonger
Summarised from Microsoft documentation. Check current rules before planning a release.

What it changes

Clean Installs

Customers install the driver without warnings, test mode or security changes.

Predictable Release

Signing time is built into the schedule instead of discovered at the end.

Right Coverage

The chosen route covers every Windows edition the product supports.

Security Compatibility

The driver loads with memory integrity and Secure Boot enabled.

Where to go next

Never ask customers to enable test signing or disable Secure Boot. It weakens their systems, and many corporate policies forbid it.

Keep signing keys in hardware tokens or a managed service, and restrict who can submit packages.

Problems this prevents

  • Drivers that load only in test-signing mode
  • A late scramble for a signing certificate
  • Attestation signing chosen for a server product
  • Drivers blocked by memory integrity

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.