Fact-checked by Grok 2 weeks ago

WHQL Testing

WHQL Testing, formally known as Windows Hardware Quality Labs Testing, is a certification program developed and administered by to evaluate the compatibility, reliability, and quality of hardware devices and their associated drivers for integration with Windows operating systems. It ensures that third-party hardware meets stringent technical standards before being distributed through channels like , thereby minimizing system instability, crashes, and security vulnerabilities for end users. The process is essential for independent hardware vendors (IHVs) seeking official endorsement under the Windows Hardware Compatibility Program. Central to WHQL Testing is the Windows Hardware Lab Kit (HLK), a comprehensive test framework that automates the validation of devices and drivers across various Windows versions, including Windows 11 (versions 24H2 and 25H2), Windows 10, and Windows Server 2016 and later. The HLK includes tools such as the Hardware Certification Kit (HCK) and Driver Test Manager (DTM), which run thousands of automated tests covering functionality, performance, power management, and security compliance. Vendors must set up a controlled testing environment, often using virtual machines via the Virtual HLK (VHLK) for efficiency, and address any failures through filters or supplemental test content provided by Microsoft. Successful completion generates test logs that are submitted through the Partner Center hardware dashboard for review. Upon approval, vendors receive a WHQL release signature, a digital catalog file that authenticates the driver package without modifying its core files, enabling seamless installation and updates on Windows systems with Secure Boot enabled. For development and pre-release phases, the WHQL Test Signature Program allows temporary test-signing of drivers, which requires enabling test mode on the system (via bcdedit /set testsigning on) and disabling Secure Boot, displaying a visible to indicate non-production status. This iterative testing is conducted through the Partner Center hardware dashboard, where submissions are created and tracked for certification. The program's significance lies in its role in upholding ecosystem-wide stability; certified hardware reduces compatibility issues and enhances user trust, while non-compliance can block distribution via official Microsoft channels. Recent updates, such as the May 2025 HLK refresh addressing security vulnerability CVE-2024-29187 in the build process, support version 24H2, version 25H2, and 2025. Overall, WHQL Testing represents a collaborative standard between and hardware manufacturers to deliver robust, interoperable technology.

History

Origins in Windows Logo Program

The Windows Logo Program was launched by in 1995 as part of its compatibility initiative for , focusing on peripherals designed to work seamlessly with the operating system and the forthcoming , aiming to simplify installation and reduce support costs for users. This program required hardware vendors to submit products for independent testing to verify reliability, ease of use, and compatibility, with certified items earning the "Designed for Windows" logo to assure consumers of quality integration. To support this effort, established the Windows Hardware Quality Labs (WHQL) in the late , creating dedicated testing facilities to evaluate device drivers for core functionality, stability, and adherence to Windows standards, progressively moving beyond third-party labs like VeriTest to in-house validation. These labs conducted rigorous assessments using tools like the Hardware Compatibility Test (HCT), ensuring drivers could handle basic operations without crashes or conflicts in the Windows environment. In 1998, the program expanded to include system-level certifications linked to , prioritizing plug-and-play () support to enable automatic hardware detection and configuration without user intervention. This milestone emphasized comprehensive testing of entire PC systems, including motherboards, peripherals, and drivers, to verify end-to-end compatibility under the "Windows 2000 Ready" branding. From its inception, the initiative targeted hardware conflicts prevalent in consumer PCs by promoting driver signing, where approved drivers received digital signatures from after WHQL validation, laying the groundwork for mandatory signing policies in later Windows versions to enhance security and reliability.

Evolution Through Windows Versions

The Windows Hardware Quality Labs (WHQL) testing program expanded significantly with the release of in 2001, introducing the "Designed for Windows XP" logo to certify hardware and drivers that met enhanced compatibility standards. This iteration incorporated rigorous security tests, such as those for anti-virus software integration and digital signing verification, alongside performance benchmarks for system stability and device functionality, ensuring third-party components aligned with XP's improved networking and multimedia capabilities. Products passing these WHQL tests received the logo, promoting consumer confidence in hardware reliability on the new OS. With in 2006, WHQL testing integrated mandatory requirements for 64-bit drivers, mandating digital signatures via a Publisher Identity Certificate to enforce kernel-mode policies and prevent unsigned drivers from loading on 64-bit systems. This shift addressed security vulnerabilities in legacy drivers while ensuring compatibility with Vista's (UAC), which required hardware and drivers to handle elevated privilege prompts without compromising system integrity. WHQL tests thus verified UAC-aware behaviors, such as proper handling of non-administrative operations, to maintain seamless functionality across Vista's security framework. The introduction of the Windows Logo Kit (WLK) in 2006 enabled vendors to perform initial compatibility testing in-house. Windows 7, released in 2009, brought further WHQL enhancements focused on , including mandatory support for Selective Suspend on bus-powered devices like USB peripherals to optimize and extend battery life on mobile systems. device testing was also bolstered, with expanded audio and video certification criteria to support high-definition content playback and improved driver stability under multi-threaded workloads, aligning with Windows 7's emphasis on media extensibility. These updates ensured certified hardware contributed to the OS's refined performance profile without excessive power draw. By in 2012, WHQL shifted toward certifying touch-enabled hardware, incorporating tests for gestures, precision input, and integration with the interface to support the OS's touch-first design paradigm. Secure Boot prerequisites became integral, requiring firmware compatibility and validation through the Hardware Certification Kit to enforce signed bootloaders and drivers, thereby mitigating threats during system startup. This evolution prioritized modern input methods and boot security as core certification pillars.

Rebranding to Hardware Certification

In 2011, during the development of , officially rebranded the Windows Hardware Quality Labs (WHQL) Testing program to the Windows Hardware Certification program, expanding its scope to include comprehensive system-level certification that extended beyond traditional lab-based evaluations. This shift aligned with the evolving demands of the Windows ecosystem, particularly the introduction of support for ARM-based devices, touch interfaces, and diverse form factors like tablets, which necessitated a more holistic approach to ensuring and quality across entire hardware configurations. A key aspect of this rebranding was the introduction of self-testing mechanisms through the Windows Logo Kit (WLK), a predecessor to the modern Windows Lab Kit (HLK), designed to minimize reliance on Microsoft's centralized labs by empowering vendors to conduct tests in-house. The WLK facilitated automated test execution on vendor premises, allowing for quicker iterations and reduced logistical burdens associated with shipping samples to remote facilities. By 2013, the program had fully phased out requirements for physical submissions to WHQL labs, transitioning entirely to automated digital submissions of test results via online portals, which streamlined the certification pipeline. This evolution was driven by the need to accelerate certifications in response to the rapid proliferation of diversity, including and devices, enabling and partners to maintain quality standards without bottlenecks in lab capacity or turnaround times.

Overview

Purpose and Objectives

The Windows Quality Labs (WHQL) Testing, now integrated into the broader Windows Compatibility Program (WHCP), serves as Microsoft's primary mechanism to verify that third-party components and drivers adhere to stringent and reliability standards for the Windows operating system. This process aims to minimize system crashes, blue screens of death, and conflicts by ensuring that devices function seamlessly across Windows platforms, thereby upholding the operating system's stability. By subjecting submissions to rigorous testing via the Windows Lab Kit (HLK), WHQL confirms that meets baseline requirements for functionality, performance, and interoperability, reducing end-user issues in diverse configurations. Key objectives of WHQL Testing include promoting the adoption of digitally signed drivers, which are essential for enabling Secure Boot—a UEFI feature that prevents unauthorized code from loading during system startup. This signing requirement not only enhances security by validating driver authenticity but also contributes to a consistent through reliable, high-quality performance across certified devices. Furthermore, the program fosters a standardized where vendors can confidently integrate their products with Windows, avoiding fragmentation that could arise from unverified components. In Microsoft's overarching strategy, WHQL Testing plays a pivotal role in maintaining Windows as a robust, dependable platform that supports innovation from hardware partners while prioritizing ecosystem-wide reliability. Unlike voluntary testing, which vendors may conduct independently for internal validation, WHQL certification is mandatory for earning official compatibility logos and enabling pre-installation of drivers and hardware on new Windows devices, ensuring only vetted products bear the Microsoft endorsement. This distinction underscores the program's enforcement of quality gates, directly benefiting the platform's long-term viability.

Scope of Hardware and Drivers Covered

The Windows Hardware Compatibility Program, formerly known as , certifies device drivers and hardware components to ensure compatibility with Windows operating systems, covering peripherals such as USB devices, printers, graphics cards, audio controllers, and input devices like keyboards and mice. It also includes drivers for system components, including motherboards, storage controllers, network adapters, and processors. Full PC builds, such as complete desktops, laptops, and tablets, are eligible when their integrated hardware passes the required tests. Certification excludes software-only applications, non-driver firmware, and mobile applications, which are addressed through separate programs like the Universal Windows certification. The program focuses on kernel-mode and user-mode drivers that interact directly with , rather than standalone software. Since the release of Windows 10, the scope has evolved to incorporate emerging technologies, including AI accelerators such as neural processing units (NPUs) integrated into client systems and IoT devices under embedded categories. This expansion supports compatibility for AI-enabled hardware in Copilot+ PCs and Windows IoT Enterprise deployments.Eligible categories are divided into client hardware for desktops and laptops running and 11, server hardware for Windows Server environments, and embedded systems for specialized IoT and industrial applications. These categories ensure broad coverage across consumer, enterprise, and edge computing scenarios.

Certification Process

Preparation and Prerequisites

Preparation for WHQL testing, now integrated into the Windows Hardware Compatibility Program, requires vendors to establish a controlled testing and fulfill administrative and prerequisites to ensure compliance with Microsoft's standards. This involves configuring dedicated setups, securing necessary software credentials, registering with Microsoft's , and compiling required prior to executing tests. Hardware setup begins with assembling dedicated test machines that meet specific configuration guidelines to support reliable testing across targeted Windows versions. A typical setup includes at least one test server running English-language editions of (such as 2016, 2019, 2022, or 2025, depending on the HLK version) with a minimum single x64 2.0 GHz , 2 GB , 300 GB hard disk, and 100 Mbps network connectivity; optimal configurations use multicore , 4 GB , storage, and 1 Gbps networking. Client test systems must align with the OS being certified, such as or 11, featuring OS-recommended and memory, at least 300 GB dedicated storage per machine, and clean installations without virtual or drive swapping to prevent contamination. Secure Boot should be disabled during initial setup, and machines operate in a domain-joined (requiring a ) or workgroup mode with guest accounts enabled for simpler configurations. These isolated, clean-install systems ensure consistent test conditions across multiple OS versions as needed for . Software prerequisites focus on securing authentication for submissions and formatting driver packages correctly. Vendors must obtain an Extended Validation (EV) code-signing certificate from a Microsoft-partnered certification authority, which is essential for signing driver binaries and submission packages to verify authenticity and enable attestation signing through the Hardware Dev Center. Driver packages must adhere to INF file standards, including a required Version section specifying the target Windows versions (e.g., via Signature="Windows NT" and ClassGUID), Manufacturer and Models sections for device identification, and DDInstall sections for installation directives, all validated using tools like InfVerif to confirm syntax and compliance before testing. Installation of the Windows Hardware Lab Kit (HLK) is also required on the test server to access testing tools, though detailed configuration follows hardware setup. Vendor registration is a mandatory step to gain access to submission and resources. Manufacturers join the Microsoft Hardware Developer Program by creating an account in the Hardware Dev Center , associating it with the EV certificate, and verifying organizational details as a global administrator; this portal provides submission tools, test result uploads, and status tracking. Documentation preparation involves compiling test plans outlining the scope of (e.g., targeted categories and OS versions) and compatibility reports detailing device specifications, driver versions, and preliminary self-assessments against Windows requirements. These materials, generated from HLK tools post-testing but planned in advance, form the basis of the submission package, including signed binaries and HLK-generated .hlk files for review.

Testing Procedures Using HLK

The Windows Hardware Lab Kit (HLK) testing procedures for WHQL certification involve a structured that automates the validation of and drivers against Microsoft's requirements. The process starts with installing the HLK Controller and Studio on a dedicated test server running supported Windows Server editions, such as , 2019, 2022, or 2025, using the HLK setup executable (HLKSetup.exe) or pre-configured HLK (VHLK) images to streamline deployment. This installation, which typically takes about 45 minutes, configures the server to manage orchestration, including opening necessary ports and integrating with 4.5 or later. Next, the HLK Client is installed on target machines—the physical or virtual systems hosting the hardware and drivers under —ensuring they meet minimum hardware specifications like sufficient and for the environment. Once set up, testers use the HLK Studio interface to add these target machines to a project, select appropriate playlists and filters tailored to the device category (e.g., or ), and schedule jobs for automated execution, allowing to run sequentially or in parallel across multiple machines without manual intervention. HLK tests are organized into distinct phases to comprehensively evaluate performance: functional, reliability, and . Functional tests, often part of the level, verify basic operation and compliance, such as ensuring a network adapter correctly handles data packets or a renders without errors. Reliability tests, aligned with scenario-based assessments, subject the to prolonged stress under load, including endurance simulations like (MTBF) runs that mimic real-world usage over hours or days to detect instability or degradation. tests focus on seamless OS integration, confirming that the adheres to Windows , policies, and features without conflicts, such as verifying plug-and-play functionality during system boot or transitions. These phases build progressively, with results logged in real-time for analysis, and filters can be applied to exclude non-applicable or known-failing tests specific to the . Common challenges in HLK testing arise from test failures, which require careful diagnosis to avoid unnecessary delays. Failures may manifest as result errors (e.g., assertion violations in logs), system crashes (indicated by bugcheck codes and dump files), or timeouts if a test exceeds three times its expected runtime, often due to environmental issues like insufficient resources or driver bugs. Testers handle these by reviewing execution logs, Event Viewer entries, and crash dumps, then initiating retries on individual failed tests—especially multi-device ones—to isolate issues without rerunning the entire suite. For partial passes, where a test succeeds in core aspects but fails minor criteria, clipboards in HLK Studio allow copying test details for documentation, and filters enable conditional passing if the failure is deemed non-critical and logged appropriately. Prerequisites like an Extended Validation (EV) code-signing certificate must be in place prior to scheduling to ensure signed binaries are tested. The overall duration of HLK testing procedures typically spans 1-4 weeks, influenced by device complexity, the number of selected filters, and the need for iterative after failures. Simpler drivers may complete in 2-4 days if pre-validated, but complex hardware like multi-function peripherals often requires multiple job cycles and manual interventions, extending the timeline to account for reliability stress tests that can run continuously for days.

Submission, Review, and Signing

After completing the testing procedures using the Windows Hardware Lab Kit (HLK), manufacturers submit their certification packages through the Partner Center hardware dashboard, formerly known as the Hardware Dev Center. This involves uploading the HLK test results in formats such as .hlkx or .hckx files (or .cab files for legacy WLK results), the driver packages themselves, and associated metadata including device types, model IDs, and marketing names. The submission process requires prior registration in the Windows Hardware Developer Program and an to ensure secure and authenticated uploads. Microsoft then conducts a review of the submitted packages, beginning with automated scans to validate the integrity and completeness of the files, such as checking for proper .cab or Zip64 compliance errors. If issues arise, such as test failures, invalid filters, or policy violations, manual checks are performed by engineers to assess compliance with Windows standards. The typical turnaround time for this review is within 5 business days, though it may extend if manual intervention is required. Upon successful review, issues a WHQL release , which is a applied to the driver package's catalog file without modifying the binaries or INF files. This authenticates the driver's origin and compatibility, enabling its distribution through channels like and granting the manufacturer rights to use the Windows Compatible logo. If a submission is rejected due to failures or non-compliance, provides specific feedback through the , detailing the required fixes such as re-running tests or correcting package errors. Manufacturers can then address these issues and resubmit the updated package via the same , iterating until is achieved.

Technical Components

Windows Hardware Lab Kit (HLK)

The Windows Hardware Lab Kit (HLK) is a comprehensive test framework developed by to validate devices and drivers for compatibility with Windows operating systems, including , , and versions from 2016 onward. Its architecture comprises three primary components that enable efficient testing workflows. The HLK Controller acts as the central orchestrator, scheduling and distributing tests across networked machines while managing dependencies and resources. The HLK Studio serves as the for test configuration, device selection, and result analysis, allowing administrators to clip tests, schedule runs, and generate reports. Target machines represent the client systems—physical or virtual—where the and drivers are installed and subjected to the , supporting up to 150 clients per controller in a typical setup. HLK versions are aligned with Windows release cycles to incorporate new compatibility requirements and features. The latest iterations, such as the 25H2 release (2025), provide full support for 25H2 across all editions, 24H2, and 2025. The 24H2 HLK was refreshed in May and July 2025, with the January 2025 update adding compatibility for hosting the controller on Server 2025. Earlier versions like 21H2 and later extend support to as a host OS. For enhanced flexibility, the HLK (VHLK) offers a pre-configured controller environment in a virtual hard disk (VHDX) format, bootable in , which facilitates cloud-based testing by deploying virtual machines in platforms like with minimum specifications of 4 GB RAM and 2 virtual processors. This virtual option reduces setup overhead for manufacturers without dedicated physical labs. Installation of the HLK requires downloading the kit from Microsoft's official distribution link, typically as an installer. The controller and integrated Studio are compatible with dedicated host machines running English versions of , 2019, 2022, or 2025 (with 24H2 or later for Server 2025), necessitating at least a 2.0 GHz x64 , 2 RAM (4 recommended), and 300 disk space. Standalone Studio can operate on or 11 hosts for remote management. Network setup is essential, involving a with at least 100 Mbps (1 Gbps optimal), open ports for controller-to-target communication, and of machine pools to group targets logically; firewalls must be adjusted to allow HLK traffic, and all machines should use static addresses for reliability. The process includes uninstalling prior Hardware Certification Kit (HCK) or older HLK versions and may require .NET Framework 4.5 or later. Among its core features, the HLK supports automated scripting via the HLK Automation Tool, which enables programmatic control over test selection, execution, and iteration, ideal for in pipelines. Result logging occurs natively in the Studio, storing comprehensive data including logs, screenshots, and XML outputs in a SQL Server database for querying and export to HLKX submission packages. The framework also integrates with static analysis tools, such as PREfast within the , through required tests like the Static Tools Logo Test in HLK releases, which scans driver to generate a Driver Verification Report identifying potential defects before runtime evaluation.

Key Test Categories and Filters

The Windows Hardware Lab Kit (HLK) organizes tests into key categories to evaluate and drivers for functionality, , , and , ensuring compliance with Windows standards. Functional tests verify core device operations, while reliability tests assess endurance under stress. Compatibility filters allow selection of relevant tests based on operating system versions and device types, and tests enforce protections against vulnerabilities. These categories guide manufacturers in targeting specific aspects of performance without running exhaustive suites. Functional tests focus on basic device behaviors, such as , where the system detects and configures like USB devices or graphics adapters during or plug-in events. They also examine power state transitions, ensuring devices properly enter and exit or low-power modes without , and I/O operations, including USB transfer rates that must sustain specified throughput (e.g., up to 5 Gbps for ) under varied loads. These tests confirm that drivers handle standard interactions correctly, using automated scripts to simulate real-world usage. Reliability tests emphasize long-term stability through stress scenarios, such as 72-hour loops of continuous I/O or rendering tasks to detect leaks, overheating, or intermittent failures in components like network adapters. Error handling simulations introduce faults, like simulated cable disconnections or power fluctuations, to verify graceful without system crashes or . These tests run on dedicated client machines to isolate endurance, often requiring multiple iterations to achieve pass criteria. Compatibility filters in the HLK Studio enable precise test selection by operating system, such as mandating Windows 11-specific checks for Secure Boot compatibility that validate firmware integration and boot loader integrity. Device-class filters differentiate tests for categories like graphics (e.g., rendering compliance) versus audio (e.g., playback ), ensuring only pertinent evaluations are applied to avoid irrelevant failures. Filters update dynamically via errata packages to reflect OS evolutions, streamlining for diverse ecosystems. Security tests enforce driver signing requirements, where all kernel-mode drivers must be digitally signed with an Extended Validation (EV) certificate to prevent unsigned code execution, as verified during HLK submission. Vulnerability scans, integrated into Device Fundamentals tests, probe for common weaknesses like buffer overflows or privilege escalations using static analysis tools and runtime checks. These measures align with Windows security baselines, including support for features like Virtualization-Based Security (VBS), to mitigate risks in certified hardware.

Benefits and Impact

Advantages for Manufacturers

WHQL certification provides hardware manufacturers with eligibility to use the "Designed for Windows" or "Certified for Windows" logos, enabling them to market their products as officially with Windows operating systems and thereby enhancing sales potential through increased customer trust and visibility in Microsoft's compatibility catalogs. By undergoing rigorous testing via the Windows Hardware Lab Kit (HLK), manufacturers can identify and resolve compatibility issues early, leading to fewer post-release customer complaints, reduced (RMA) rates, and lower overall support costs associated with troubleshooting hardware-software conflicts. The certification process streamlines submissions through the Hardware Dev Center , supporting distributed and merged testing methodologies that minimize redundant efforts across product families, ultimately accelerating product qualification and integration with Windows updates for faster time-to-market. Furthermore, WHQL-certified satisfies Microsoft's standards, granting manufacturers a compliance advantage by meeting prerequisites for original equipment manufacturers (OEMs) to pre-install Windows on new devices, facilitating broader distribution channels without risking license violations.

Value for End Users and Compatibility

WHQL certification significantly enhances system stability for end users by subjecting and to rigorous testing through the Windows Hardware (HLK), which identifies and mitigates potential issues that could lead to crashes, including blue screens of death (BSOD) and driver failures. This process ensures that certified devices operate reliably under various conditions, reducing the likelihood of system instability and update conflicts that might otherwise disrupt daily computing tasks. For instance, the certification verifies with core Windows mechanisms, minimizing errors that arise from untested interactions between and the operating system. A key value lies in the seamless provided by WHQL-certified hardware, which guarantees support for essential Windows features such as modes (e.g., and ) and configurations. These tests confirm that devices integrate smoothly without compromising functionality, allowing users to leverage advanced capabilities like efficient power transitions and extended display setups without hiccups. This reliability extends to everyday scenarios, ensuring that peripherals and components perform as expected across Windows environments. The certification fosters -wide trust by signaling to end users that meets Microsoft's stringent standards, thereby encouraging confident adoption of new Windows versions such as Windows 11. Users can rely on the Windows Compatible Products List to select devices that align with the latest OS requirements, promoting broader and reducing hesitation in upgrades. This trust is reinforced by the program's emphasis on verified performance, helping users avoid suboptimal that might fail under updated system demands. Furthermore, WHQL-certified drivers benefit from long-term support through priority integration into update channels, including , where they receive timely security patches and compatibility enhancements. This mechanism ensures ongoing maintenance for the reasonable product lifetime, with certified packages undergoing malware scans and validation to maintain security without user intervention. As a result, end users experience sustained protection and functionality, as these drivers are distributed securely and efficiently, aligning with Microsoft's commitment to reliable post-certification support.

Current Developments

Integration with Windows 11 and Server 2025

WHQL testing for incorporates mandatory verification of (TPM) 2.0 support to align with the operating system's core security requirements, ensuring hardware devices enable features like Device Health Attestation and secure boot processes. This testing is integrated into the Windows Hardware Lab Kit (HLK) filters, where systems must demonstrate TPM 2.0 compatibility during certification to prevent installation barriers on non-compliant hardware. Additionally, AI hardware filters in WHQL playlists address Neural Processing Unit () compatibility, particularly for Copilot+ PCs that demand an NPU capable of at least 40 to support on-device AI workloads such as and Windows Studio Effects. These filters validate NPU performance and , ensuring seamless execution of AI-accelerated features in hybrid work environments that emphasize remote and tools. For 2025, the WHQL playlist uses HLK version 24H2, which includes tests for networking and . timelines for these OS versions feature HLK playlists initially released in late 2024 for preview and testing, enabling vendors to prepare ahead of general availability. Full support was achieved by Q1 2025 through the February HLK refresh, which finalized test suites for version 24H2 and 2025 submissions to the Windows Program. Subsequent quarterly updates, such as the May and July 2025 refreshes, incorporated errata fixes and new tests to refine compatibility. A notable change in WHQL processes for these releases is the increased emphasis on remote testing via the updated Virtual Hardware Lab Kit (VHLK), now supporting Generation 2 virtual machines to facilitate distributed setups for global vendors. This shift reduces the need for physical lab proximity to Microsoft facilities, allowing international manufacturers to conduct comprehensive HLK tests in virtual environments while maintaining submission integrity through the Hardware Dev Center.

Recent Updates and Static Analysis Requirements

In July 2025, mandated that all driver submissions for Windows Hardware Compatibility Program (WHCP) certification must pass updated static using to detect vulnerabilities, replacing prior tools like PREfast for enhanced scanning. This requirement applies to the Static Tools Logo Test, ensuring comprehensive of driver before approval, with developers required to use CodeQL CLI version 2.22.1 or later and the latest Microsoft query pack. The Windows Hardware Lab Kit (HLK) saw significant enhancements in 2025, including a refreshed release in May for compatibility with version 24H2 and 2025, incorporating fixes and updated test filters to streamline workflows. A further July refresh introduced improved submission tools in HLK Studio, facilitating easier package creation (.hlkx files) and integration with the Partner Center dashboard for faster review processes. Policy changes in 2025 emphasized stricter enforcement on driver quality, with initiating the removal of legacy drivers from to mitigate security risks from outdated software, beginning with an initial cleanup phase followed by a six-month for partners to address concerns. provides a six-month following each cleanup phase for partners to address concerns regarding legacy drivers. These updates collectively aim to strengthen Windows in response to escalating cyber threats, reducing vulnerabilities in certified drivers and promoting more robust ecosystem compatibility.

References

  1. [1]
    Windows Hardware Lab Kit | Microsoft Learn
    Sep 24, 2025 · The Windows Hardware Lab Kit (Windows HLK) is a test framework used to test hardware devices and drivers for Windows 11, Windows 10 and all versions of Windows ...
  2. [2]
    WHQL Release Signature - Windows drivers - Microsoft Learn
    Jul 11, 2025 · Learn how to obtain a WHQL release signature for your driver package by testing it with the Windows Hardware Lab Kit (HLK).
  3. [3]
    WHQL Test Signature Program - Windows drivers - Microsoft Learn
    Sep 20, 2024 · The Windows Hardware Quality Labs (WHQL) test signature program supports test-signing of drivers to be submitted for a WHQL release ...
  4. [4]
    Create a New Hardware Submission - Windows drivers
    Oct 16, 2025 · Create a new hardware submission on the Partner Center hardware dashboard for your Windows tested drivers to obtain certification.
  5. [5]
    Safe deployment best practices for Windows drivers - Microsoft Learn
    Even when drivers are deployed outside of Windows Update, they should still complete WHQL testing and be digitally signed. WHQL testing and driver signing ...
  6. [6]
    Microsoft Windows Logo Program Tackles Total Cost of Ownership
    Microsoft Corp. today announced the release of an updated Designed for Windows NT® and Windows® 95 Logo ...Missing: introduction WHQL origins
  7. [7]
    WHQL Presentation | PDF | Device Driver | Microsoft Windows - Scribd
    The document discusses Windows Hardware Quality Labs (WHQL) which tests and certifies third party hardware and software for compatibility with Windows ...Missing: introduction | Show results with:introduction
  8. [8]
    Microsoft Announces Certified for Windows 2000 Program - Source
    Jul 26, 1999 · The Rational TestFoundation for Windows 2000 is scheduled to be available in October 1999. Compliance testing for server applications will ...
  9. [9]
    [DOC] Microsoft Windows Logo Program System and Device Requirements
    ​ Anti-virus software: WHQL launched a test program, related to the “Designed for Windows XP” Applications Logo Program, for anti-virus applications that ...
  10. [10]
    Windows Hardware Quality Labs v1 | PDF - Scribd
    Windows Hardware Quality Labs. WHQL Testing is a testing process which ... purchase products that display the "Designed for Windows XP" logo. Products ...
  11. [11]
    Kernel-Mode Code Signing Requirements - Windows drivers
    Jun 7, 2022 · Starting with Windows Vista, the kernel-mode code signing policy controls whether a kernel-mode driver will be loaded.
  12. [12]
    Microsoft to require signed drivers for 64-bit Vista - Ars Technica
    Feb 1, 2006 · To be signed, each driver must obtain and use a Publisher Identity Certificate (PIC) from Microsoft. Unlike the more lengthy and costly WHQL ...Missing: account | Show results with:account
  13. [13]
    Windows 7 Audio Logo Changes - Studylib
    To increase power savings, all bus-powered USB devices must support Selective Suspend on Windows 7, as shown in the following requirement: Requirement Title ...<|separator|>
  14. [14]
    [PDF] Windows Certification Program - Microsoft Download Center
    This publication of the Windows Hardware Certification Program Requirements provides an update to the. Windows 8 and Windows 8.1 Certification Program. These ...
  15. [15]
    Windows Secure Boot Key Creation and Management Guidance
    Sep 5, 2025 · This document helps guide OEMs and ODMs in creation and management of the Secure Boot keys and certificates in a manufacturing environment.Secure Boot, Windows and... · Key Management Solutions
  16. [16]
    Microsoft's Windows 8 Certification Requirements Revealed
    Jan 17, 2012 · Speaking of which, tablet and convertible PCs will have to sport at least 10GB of free space, UEFI firmware, WLAN and Bluetooth 4.0 + LE (low ...
  17. [17]
    Updates to Driver Testing — Not Just for Certification - OSR
    Mar 18, 2015 · Long ago, Microsoft created the Windows Hardware Quality Lab designedforxp s (WHQL, pronounced “wickle”) program. The goal of this program ...
  18. [18]
    Windows Hardware Certification Kit - Win32 apps - Microsoft Learn
    Sep 1, 2020 · The Windows Hardware Certification Kit enables hardware certification and driver filtering for Windows OS, replacing the Windows Logo Kit.
  19. [19]
    Windows Hardware Compatibility Program | Microsoft Learn
    Jun 24, 2021 · The Windows Hardware Compatibility Program is designed to help your company deliver systems, software and hardware products that are compatible with Windows.
  20. [20]
    Windows Hardware Compatibility Program Specifications and Policies
    Sep 23, 2025 · The specifications define how to build Windows-compatible devices, systems, and filter drivers across all Windows Platforms.
  21. [21]
    Driver code signing requirements - Windows - Microsoft Learn
    May 29, 2025 · This article provides general information on the types of code signing available for your drivers, and the associated requirements for those drivers.Missing: objectives | Show results with:objectives
  22. [22]
    Windows Hardware Compatibility Program Certification Process
    Mar 21, 2022 · The Windows Hardware Compatibility Program lets you show customers that your hardware is reliably compatible with Windows 10 and Windows 11.Step 1: Review Hardware... · Step 2: Register on Hardware...
  23. [23]
    HLK Product Type Matrix - Microsoft Learn
    Jan 18, 2019 · The Windows 10 HLK Product Type Matrix lists all of the product types that can be included in the Windows Hardware Compatibility Program.
  24. [24]
    Search the Windows Compatible Products List - Microsoft Learn
    Aug 21, 2025 · Learn to search the Windows compatible products list, a comprehensive list of certified devices and systems.Missing: categories | Show results with:categories
  25. [25]
    Digital Signatures and PnP Device Installation (Vista and Later)
    Mar 28, 2022 · Driver packages certified and signed through the Windows Hardware Quality Labs (WHQL); Windows Sustained Engineering (SE) updates. Signatures ...<|control11|><|separator|>
  26. [26]
    Copilot+ PCs developer guide - AI - Microsoft Learn
    a specialized computer chip ...Missing: 10 | Show results with:10
  27. [27]
    What is Windows IoT Enterprise? - Microsoft Learn
    May 22, 2024 · Windows IoT Enterprise LTSC is supported for security, reliability, and compatibility on the latest silicon available at the time of release.What's new in Windows 11 IoT... · What's new in Windows 10 IoT... · Licensing
  28. [28]
    Windows HLK Prerequisites - Microsoft Learn
    Oct 1, 2021 · To test systems and filter drivers, you need at least 1 test server and 1 test system. To test external devices, you need at least 1 test server ...
  29. [29]
    Register for the Microsoft Windows Hardware Developer Program
    May 13, 2025 · This article shows you how to register for the Microsoft Windows Hardware Developer Program. When you register for the Hardware Developer ...Missing: objectives | Show results with:objectives
  30. [30]
    Overview of INF Files - Windows drivers - Microsoft Learn
    Apr 22, 2025 · A setup information (INF) file is a text file in a driver package that contains all of the information that device installation components use to install a ...
  31. [31]
    INF Version Section - Windows drivers - Microsoft Learn
    Apr 10, 2023 · By convention, the Version section appears first in INF files. Every INF file must have this section.
  32. [32]
    Validating Windows Drivers - Microsoft Learn
    Aug 14, 2024 · InfVerif is a tool that validates INF syntax and checks that the INF conforms to requirements and restrictions. Use InfVerif with /w to ...Missing: standards | Show results with:standards
  33. [33]
    Step 8 Create a submission package | Microsoft Learn
    Jul 11, 2025 · All submissions must be digitally signed. Starting with Windows 10, you must also include an EV (extended validation) code signing certificate.
  34. [34]
    Step 1 Install Controller and Studio on the test server - Microsoft Learn
    Feb 19, 2025 · In this step, you install Windows HLK software on the designated test server. The setup program installs the Windows HLK Controller and Studio, in addition to ...Missing: workflow target job scheduling WHQL<|separator|>
  35. [35]
    HLK Testing Concepts | Microsoft Learn
    Nov 5, 2020 · Use the test levels to test basic, functional, reliability and certification tests in that order as the different levels provide testing ...Missing: phases | Show results with:phases
  36. [36]
    Troubleshooting Windows HLK Test Failures - Microsoft Learn
    Nov 5, 2020 · This article describes possible test failures and provides step-by-step instructions on how to troubleshoot them.
  37. [37]
    WHQL Driver Testing & Hardware Certification by Microsoft - Apriorit
    Sep 3, 2025 · Windows Hardware Quality Labs is a framework that allows you to test the reliability and compatibility of your device or driver with Windows.Whql Infrastructure... · Whql Testing Flow · Build Whql-Compliant Drivers...Missing: history | Show results with:history<|control11|><|separator|>
  38. [38]
    Partner Center for Windows Hardware - Microsoft Learn
    With the Windows Hardware Compatibility Program you can design, create, and test your hardware and drivers. Then submit the final version through the Partner ...
  39. [39]
    What's new in the Hardware Lab Kit - Microsoft Learn
    Sep 23, 2025 · To create a Compatibility Program test pass, download the official Hardware Compatibility Program Playlist and apply to your HLK project.
  40. [40]
    VHLK Getting Started Guide
    ### Summary of Virtual HLK (VHLK)
  41. [41]
    Step 1 Install the HLK Controller - Microsoft Learn
    Oct 3, 2024 · The Windows Hardware Lab Kit should only be installed on machines that are dedicated solely for testing purposes. Do not install any HLK ...<|control11|><|separator|>
  42. [42]
    https://go.microsoft.com/fwlink/p/?LinkId=733613
  43. [43]
    HLK Automation Tool | Microsoft Learn
    Jun 24, 2022 · Step 1: Install Controller and supporting programs on the test server. Step 2: Install HLK Client on the test computer(s). Step 3: Create a test ...Missing: WHQL | Show results with:WHQL
  44. [44]
    Step 6 Select and run tests | Microsoft Learn
    Jun 8, 2022 · Run the selected tests by choosing Run Selected. If any additional input is needed, Windows HLK Studio will prompt you. A progress bar appears.
  45. [45]
    Windows 11 Hardware Lab Kit Requirement - Microsoft Q&A
    Feb 26, 2024 · 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 ...
  46. [46]
    Windows Hardware Lab Kit (HLK) Tests for USB - Microsoft Learn
    Dec 15, 2021 · To run the HLK tests, you need: Your host controller (either integrated or as add-in cards), hubs, or device to certify. Open Device Manager on ...Missing: machine configuration
  47. [47]
    Review common Device Fundamentals Reliability test failures
    Mar 25, 2021 · This topic describes common test failures that you can encounter when you run Windows Hardware Lab Kit (Windows HLK) Device Fundamentals Reliability tests.
  48. [48]
    Windows Hardware Lab Kit Filters - Microsoft Learn
    Jan 18, 2019 · Many errata use filters to automatically filter the failure from the submission results. Filters are applied within Windows HLK Studio.Missing: class | Show results with:class
  49. [49]
    Driver security checklist - Windows - Microsoft Learn
    Feb 26, 2025 · This article provides a driver security checklist for driver developers to help reduce the risk of drivers being compromised.
  50. [50]
    Secure Boot Logo Test | Microsoft Learn
    This test verifies the out-of-box configuration and basic functionality of Secure Boot. Most of this test is automated.
  51. [51]
    [DOC] WHCP Policies and Processes - Microsoft Download Center
    This paper provides information about the Windows Hardware Compatibility Program and Windows Hardware Certification Program (both referred to as WHCP). It ...
  52. [52]
    [DOC] Hardware Certification Policies and Processes
    The policies and processes for testing and submitting Windows RT systems are covered in a separate document. For clarification, contact sysdev@microsoft.com ...
  53. [53]
    [DOC] Desktop and Mobile PC Requirements - Microsoft Download Center
    ​ Minimum driver compatibility. Each driver must pass minimum compatibility, functionality, and stress testing as verified by the testing suites published by ...
  54. [54]
    Distributing a Driver Package - Windows - Microsoft Learn
    Jan 14, 2025 · Passes the Windows Hardware Lab Kit (HLK) testing. · Qualifies for the Windows Certification Program. · Receives a WHQL release signature.Missing: standards | Show results with:standards<|control11|><|separator|>
  55. [55]
    TPM recommendations | Microsoft Learn
    Aug 15, 2025 · Windows 11 requires TPM 2.0 by default to facilitate easier enablement of this enhanced security for customers. Device Health Attestation, Yes ...
  56. [56]
    Windows 11 Specs and System Requirements - Microsoft
    Trusted Platform Module (TPM) version 2.0. Check here for instructions on how your PC might be enabled to meet this requirement. Compatible with DirectX 12 or ...Get Windows 11 · Compare Windows 10 & 11 · Worldwide sitesMissing: WHQL testing
  57. [57]
    Windows Server 2025 hardware certification - Microsoft Q&A
    Sep 15, 2025 · The Windows Hardware Compatibility Program lets you show customers that your hardware is reliably compatible with Windows 10 and Windows 11.
  58. [58]
    Features Removed or No Longer Developed in Windows Server
    Sep 24, 2025 · Learn about the features and functionalities removed or no longer developed in Windows Server.
  59. [59]
    https://techcommunity.microsoft.com/t5/windows-driver-developer-blog/announcing-updated-static-analysis-requirement-for-windows/ba-p/4433579
  60. [60]
    What's new in Windows Server 2025 | Microsoft Learn
    Feb 28, 2025 · Hotpatch is now available for Windows Server 2025 machines connected to Azure Arc after Hotpatch is enabled in the Azure Arc portal. You can use ...Server 2022 · DTrace on Windows · Mica material
  61. [61]
    HLK Feb Refresh Release for Windows 11 Version 24H2 and ...
    Feb 18, 2025 · Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 will be available, February 18, ...Missing: remote | Show results with:remote
  62. [62]
    HLK May Refresh Release for Windows 11 Version 24H2 and ...
    May 6, 2025 · Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 is available starting May 6, 2025 ...Missing: WHQL timelines
  63. [63]
    HLK July Refresh Release for Windows 11 Version 24H2 and ...
    Jul 8, 2025 · Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 is available starting July 8, 2025.Missing: WHQL remote global
  64. [64]
    Announcing Updated Static Analysis Requirement for Windows ...
    Jul 15, 2025 · This article outlines how to obtain the latest CodeQL query pack and validate your drivers against the updated Microsoft static analysis ...Missing: WHQL | Show results with:WHQL
  65. [65]
    Run CodeQL Analysis on Windows Driver Code - Microsoft Learn
    Jul 25, 2025 · This article explains how to use CodeQL analysis to create a Driver Verification File for Windows Hardware Compatibility Program (WHCP) certification.Missing: July PREfast
  66. [66]
    Microsoft will start removing legacy drivers from Windows Update
    Jun 23, 2025 · Microsoft will start removing legacy drivers from Windows Update to improve driver quality for Windows users but, most importantly, to increase security.Missing: WHQL compliance penalties
  67. [67]
    Microsoft is removing legacy drivers from Windows Update - Neowin
    Jun 19, 2025 · Once the Redmond tech giant completes its first phase of this cleanup, it will give partners a six-month grace period to share any concerns.Missing: WHQL | Show results with:WHQL
  68. [68]
    Microsoft to Phase Out Legacy Drivers from Windows Update
    Jun 20, 2025 · Microsoft is set to remove legacy drivers from Windows Update as part of a major push to strengthen system security and improve compatibility.Missing: WHQL penalties<|separator|>