Microsoft Windows Driver Signing With Code Signing Certificates

Simplify Driver Signing for Windows 10 and Other Operating Systems

Windows drivers are crucial bits of software that make it possible for devices’ software and hardware components to communicate. So, it’s vital to know whether verified third parties created drivers. This is why Windows drivers must be digitally signed using a code signing certificate and uploaded to the Windows Hardware Developer Center dashboard.  

The team at CodeSigningStore.com is here to help you meet these driver-signing requirements. We’ve partnered with the world’s leading certificate authorities to make the process of signing Microsoft drivers for Windows as easy and affordable as possible by providing:

• Competitive prices on Windows driver signing certificates
• Broader enrollment options
• Fast certificate issuance times
• Access to educational resources
• 24/7 technical support

What Types of Drivers Can You Sign?

What types of Windows drivers exist? They fall into one of two categories:

1. User-mode drivers. This category of drivers allows Win32 applications to run on a device and communicate with kernel-mode drivers. Examples of user-mode driver executions include printer and monitor drivers.
2. Kernel-mode drivers. These privileged software components operate at the heart of a device’s operating system. They enable core systems and devices to communicate. Starting in Windows 10, all kernel-mode and user-mode driver submissions must be signed using an extended validation (EV) code signing certificate.

Whether you’re creating user- or kernel-mode drivers, it’s vital to ensure that they meet specific Windows driver code signing requirements. For example, kernel-mode drivers must be uploaded to the Windows Hardware Dev Center Dashboard and digitally signed by Microsoft to be trusted for distribution via Windows Update.

Digitally Signing Drivers Is Just Part of the Windows Certification and Attestation Process

Windows driver signing is mandatory for all x64-based versions of Windows since Windows Vista and is recommended for all 32-bit systems as well. But in addition to digitally signing your code using a code signing certificate, you also must run tests using the appropriate framework for your driver to be Windows Certified:

• Windows Hardware Lab Kit (HLK) or (virtual HLK) for Windows 10 or later OS versions,
• Windows Hardware Certification Kit (HCK) for Windows version 8.1 or earlier OS versions, or
• Windows Logo Kit (WLK) hardware submission package for the 2008 or older versions of Windows Server.

Are Driver Attestation and Windows Certification Signatures the Same?

No. When you submit a driver to the Microsoft Windows Hardware Dashboard, you can do so for either attestation signing or for Windows’ Hardware Compatibility Program (WHCP) certification:

• Attestation Driver Signing. A driver that’s given a Microsoft attestation signature hasn’t been tested by Microsoft for compatibility or functionality to ensure it meets the requirements of the WHCP (or what was formerly known as the Windows Hardware Quality Labs [WHQL]). This is intended for use in development and testing.
• Certified Windows Driver Signing. A Windows-certified driver has undergone testing using one of the WHCP kits and has been officially certified by Microsoft. This is intended for publicly released drivers and those that are to be distributed via Windows Update.