
End of Support for Windows 10: Microsoft Enforces Stricter WHCP Policies
Microsoft recently announced the cessation of support for Windows 10 under its Windows Hardware Compatibility Program (WHCP), coinciding with the operating system reaching its end of life. This decision aligns with the firm’s strategy to focus on newer technologies and security enhancements available in more recent operating systems.
Understanding the Windows Hardware Compatibility Program
The WHCP serves as a vital workflow for hardware manufacturers, OEMs, and partners. It facilitates testing to ensure that new devices and components are compatible with Windows, utilizing tools such as Microsoft’s Hardware Lab Kit (HLK).Successful certification by WHCP allows products to carry a Microsoft badge, bolstering buyer confidence and promoting informed purchasing decisions.
Upcoming Changes: InfVerif /h Validation
Starting later this year, Microsoft will implement the InfVerif /h validation process as a critical step in driver attestation. Introduced in Windows 11, version 24H2, this procedure ensures driver packages maintain integrity against external alterations while simplifying installation and updates.
Mandatory Compliance for Enhanced Security
Microsoft has reiterated that while the InfVerif /h ruleset was initially part of WHCP and Attestation workflows, it will now be mandatory for compliance attestation. The company’s goal is to bolster the security and overall quality of the Windows driver ecosystem, responding to increasing demands for secure computing environments.
Guidance for Hardware Manufacturers
OEMs and partners are advised to apply the InfVerif /h validation to their driver packages before submission. If testing with the Windows 11, version 25H2 HLK, the ruleset will automatically apply, streamlining the process. The latest version of the InfVerif ruleset can be accessed through the updated Windows Driver Kit (WDK).
For further details on executing the InfVerif ruleset and managing potential errors and warnings, you can refer to Microsoft’s in-depth blog post here.
Leave a Reply