Windows 11 Hardware Lab Kit Requirement

Question

With the expiration of Cross Signing Certificates our company has found that we can no longer sign CAT files.

https://learn.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates

Our company does not write kernel drivers. We either use the CyUSB3.sys driver or the WinUSB.sys driver. We only create the INF and CAT file that are needed to install our hardware with the appropriate driver.

The Windows 11 Hardware Lab Kit now has the "Static Tools Logo Test" which requires running certain tests on the source code to create a Driver Verification Log (DVL) that the HLK uses to verify that the driver meets certain Microsoft requirements.

https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/6ab6df93-423c-4af6-ad48-8ea1049155ae

Because our company did not write the drivers (Cypress/Infineon and Microsoft wrote the drivers in question) we don't have the source code to run this test.

In the cases where we use the Cypress driver our driver install is literally three files (SYS, INF, and CAT).

In the cases where we use the Microsoft driver our driver install is the INF and CAT files plus the WDFCoInstaller01009.dll and WinUSBCoInstaller2.dll. The WinUSB.sys driver comes with Windows.

Given that the driver(s) has been previously approved by Microsoft is this test really needed in order to get the CAT file signed by Microsoft?

Is there a way that our company can continue to sign the CAT file ourselves?

Will Microsoft provide the source code for the WinUSB.sys driver so that we can run the tests and create the necessary DVL?

Thanks

Answer 1

You might find information on this page as helpful:

https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/6ab6df93-423c-4af6-ad48-8ea1049155ae

In particular...

The goal of the Static Tools Logo test is to require you, as a driver developer, to run CodeQL on your driver prior to submission to help eliminate bugs. However, we have received reports in the past of the test mistakenly asking for CodeQL results for other drivers on the stack due to an architectural limitation, blocking certification. To resolve this issue in Windows 24H2, we have moved to a model where the signature of the driver for the device under test is checked. With this change, inbox Windows drivers will not be flagged by the test. Additionally, to unblock developers who are performing HLK testing on another third-party's devices, the test will also avoid flagging results for WHCP-signed drivers. When running this test for certification, your driver should be test signed to ensure the test functions correctly. Failing to do so may result in the test failing to warn about CodeQL violations, or the test failing to enumerate.

So, in theory, if the SYS file of the driver is already signed, the HLK test lab should not require you to perform the Static Tools Logo Test.