InfVerif /h

InfVerif /h is a new mode of InfVerif that validates using a set of INF requirements that change with each release to align with the requirements for a WHQL signature from Hardware Dev Center. Over time, the requirements will become stricter and will eventually align with driver package isolation requirements.

InfVerif /h examines all the OS versions where the INF may install, and evaluates the INF using the appropriate rules for that OS version automatically. For example, in an INF file that uses version decorations to change the behavior for different OS versions:

Contoso = Models, NTAMD64, NTAMD64.10.0...22000

InfVerif /h will internally validate this INF twice, once validating the [Models] section [Models.NTAMD64] using the rules for build 21999 (the highest OS version where that [Models] section will be used), and once validating the [Models] section [Models.NTAMD64.10.0...22000] using the latest ruleset. An INF file that only has a single [Models] section will only be validated against the latest ruleset.

Usage

To use InfVerif /h using the default behavior:

infverif.exe /h <INF file> [<INF file>]

InfVerif /h also allows you to specify the highest ruleset that InfVerif will use using the '/rulever' argument, for example:

infverif.exe /h /rulever 10.0...17763 <INF file>

Using the '/rulever' argument may cause some portions of the INF to be ignored. Using the above arguments with the previous example, the [Models] section [Models.NTAMD64] will be validated using the rules for build 17763, and [Models.NTAMD64.10.0...22000] won't be validated since the specified ruleset does not apply to it.

Adding the verbose option will cause InfVerif to print out the maximum ruleset used during its evaluation:

infverif.exe /h /v <INF file>

Running in Verbose
Running signature requirements check
Using rules from OS build: 10.0.26080

infverif.exe /h /rulever 10.0...17763 <INF file>

Running in Verbose
Running signature requirements check
Using rules from OS build: 10.0.17763

InfVerif /h can also use a future ruleset. There's a built-in 'vnext' OS version that will use the rules expected to be required one OS release in the future. The rules enforced by 'vnext' aren't final and subject to change for the final release, but are intended to provide a good insight into future requirements.

infverif.exe /h /rulever vnext <INF file>

Requirements

The InfVerif /h rulesets are aligned with the requirements of the WHCP program. The requirements are defined as the full driver package isolation requirements, with some set of exceptions applied to the requirements. Some exceptions will be removed each release until InfVerif /h enforces all driver package isolation requirements.

Current Requirements

Registry

INF files must not modify any global registry locations and instead only use the HKR registry root to modify or create registry information with an AddReg directive. The following paths are current exceptions to this requirement:

File Paths

DIRID 13 must be specified in the INF as the destination location for all entries in the [DestinationDirs] section. The following values are exceptions to this requirement: