Investigate driver signing (for production usage)

[forderud]

Investigate simplest approach for enabling driver deployment also on machines that are not configured for "test-signing".

Steps:

• Purchase an Extended Validation (EV) code signing certificate.
• Join the Microsoft HW developer program

EV certificate vendors

From https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-cert-manage

Code signing certificates can be purchased from one of the following certificate authorities:

• IdenTrust EV code signing certificate: $207/yr + SafeNet eToken 5110 CC USB token ($96) - NOT Microsoft endorsed
• Certum EV code signing certificate: €359.00/yr - NOT Microsoft endorsed
• DigiCert code signing certificate: $380/yr for individual document signing (link from https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-reqs)
• Entrust code signing certificate: $400/yr
• GlobalSign code signing certificate: $410/yr
• Sectigo (formerly Comodo) EV code signing certificate: $498/yr - NOT Microsoft endorsed
• SSL.com code signing certificate: $349/yr

Links

https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-program-register

Entra domain: [email protected]

[forderud]

The WDK download page opens the Feedback tool. A comment was created.

Please provide some kind of URL to the problem report, so that I can monitor Microsoft's progress on fixing it.