The process for kernel mode drivers has changed as of April 2021. Microsoft will no longer allow kernel mode drivers to be signed solely by a publicly-trusted CA certificate. Microsoft now requires a kernel mode driver to be signed first by a publicly-trusted CA certificate, and then submitted for signing by Microsoft through the Microsoft development portal. More details can be found here.
Microsoft's new process for driver submissions
Starting in 2021, Microsoft will be the sole provider of production kernel-mode code signatures. Microsoft has implemented a new process for signing kernel-mode driver packages. You will need to sign any new kernel-mode driver packages by following Microsoft's updated Hardware Submission instructions. See Partner Center for Windows Hardware.
Create a new hardware submission
To prepare your hardware for the Windows Hardware Compatibility Program for Windows 10 (or the separate certification program for previous operating systems), you must create and submit an .hlkx file (for Windows 10) or .hckx file (for previous operating systems). This file is created using the Windows HLK Studio (or Windows HCK Studio, for previous operating systems) and contains all of the test results, drivers, and symbols for your product. Submitting this file allows the dashboard to review your test results, evaluate any drivers tested, and return Microsoft digitally signed catalog files.
To submit a file
|Device type||Indicate if your device is:
- An internal component, if your device is part of a system and connects inside the PC.
- An external component, if your device is an external device (peripheral) that connects to a PC.
- Both, if your device can be connected internally (inside a PC) and externally (peripheral).
|Device metadata category||Select an incon for your device from a list of default icons based on your device category. This determines which icon appears in Devices and Printers. If your device should not appear, select "Internal device".
For information about delivering a rich experience with Windows Device Stage, see Device Metadata.
|Device metadata model ID||These GUIDs are used to validate your Device Metadata submissions to the legacy Sysdev dashboard. If provided, they must match the model IDs in your device metadata package.|
|Announcement date||Enter the date when you want your product included on the Windows Server Catalog, the Windows Certified Products List, and the Universal Driver List.|
|Marketing name||Enter the marketing name(s) for your submission. Marketing names allow you to provide aliases for your product. You can provide as many names as you want.|