Table of contents
Collapse the table of content
Expand the table of content

Installing a Release-Signed Catalog File for a Non-PnP Driver

Last Updated: 1/24/2017

To comply with the kernel-mode code signing policy of 64-bit versions of Windows Vista and later versions of Windows, a non-boot, non-PnP kernel-mode driver must have either an embedded release signature or a released-signed catalog file that is installed in the system component and driver database. In addition, if you use a release-signed catalog file to authenticate a user-mode driver or a 32-bit non-PnP kernel-mode driver, the Windows code-signing policy requires that the catalog file be installed in the system component and driver database. PnP device installation automatically installs the catalog file of a PnP driver in the driver database. However, for non-PnP drivers, the installation application that installs a non-PnP driver must install the catalog file in the driver database.

To install a catalog file for a non-PnP driver that is released to the public, a redistributable installation application should use the CryptCATAdminAddCatalog cryptography function, as described in Installing a Catalog File by using CryptCATAdminAddCatalog.

Note In general, a redistributable installation application cannot use the SignTool tool to install a catalog file because SignTool is not a redistributable tool.

Tip Using embedded signatures is generally easier and more efficient than by using a signed catalog file. For more information about the advantages and disadvantages of using embedded signatures versus signed catalog files, see Test Signing a Driver.

© 2017 Microsoft