Changes to the Static Tools Test for Windows Server 2016


Starting in April 2016, the Windows Hardware Lab Kit will include changes to the Static Tools Test for Windows Server 2016. This test is required for Certification of NDIS [Network Driver Interface Specification] and StorPort model drivers, as well as for drivers now designated as “Other” – more information below.

Microsoft’s Static Analysis Tools, namely, Code Analysis for Drivers (CA) and Static Driver Verifier (SDV) have been found to be highly effective in improving driver reliability by identifying coding issues that would be otherwise difficult to find.

The resulting Driver Verification Log (DVL) file output by the Static Analysis tools will be captured by the Hardware Lab Kit for inclusion in the device submission package. Issues discovered by CA and SDV that are determined to be “Server: Must Fix” must be corrected in driver code for Windows Server 2016 submission. Any other issues discovered will be recorded in a Static tools log, but there is no requirement to fix those issues.

More information on “Other” device and driver classification

Some devices and drivers have features and functionality for which Windows has no specific design scenario. The Windows Driver Kit uses the same CA Rules as above and the Kernel Mode Driver Framework Rules in SDV to examine these drivers. The Windows Hardware Lab Kit tests the specific features these devices expose to the operating system. The “Other” classification allows for signing of the drivers and distribution on Windows Update, but the device or driver does not receive a Windows Server 2016 Certification or Logo. See the Windows Hardware Compatibility Program Policies and Processes document, in the “Other” products and conditional WHCP section, for more information about “Other” products.


Comments (0)

Skip to main content