Windows Hardware Certification articles

Hardware Lab Kit API Updates and New Unreferenced File Check in February Refresh

Cymoki — Wed, 18 Feb 2026 20:44:54 GMT

What’s Changing?

The refreshed Windows Hardware Lab Kit (HLK) available starting February 2026 for Windows 11, version 25H2, Windows Server 2025, and Windows 11, version 24H2 will introduce a new check during HLK packaging. If the attached driver package includes one or more files that were not referenced by an .inf, the following warning will display at the end of packaging:

This will not affect package generation. Even if the warning appears, an .hlkx will still be created regardless.
It is highly recommended to validate that all files are referenced before testing. To do so, attach the driver package, create an .hlkx package (test results not necessary), and observe whether the warning appears. This validation can be performed any time after target selection.
The PackageWriter class in the Microsoft.Windows.Kits.Hardware.ObjectModel.Submission namespace will include the following updates:
- The AddDriver and AddReplacementDriver methods will include a new check for files in the driver package that were not referenced by an .inf file. This information will be available through the warningMessages output arg.
- There will also be new AddDriver and AddReplacementDriver overloads that expose the unreferenced file information through new output arguments in addition to warningMessages.
- See Creating a Package for code samples accessing data on unreferenced files using the updated API.
See Microsoft Learn for more details.

Actions Required

To address an unreferenced file, first navigate to the log path to see which attached files were not referenced.

If creating an original submission package...
- Option 1 (recommended): Remove the driver package from the project. Remove the unreferenced files from the driver package, then re-attach.
- Option 2 (recommended): Remove the driver package and modify the .inf to reference all the files. Re-test the driver and attach the modified driver package.
- Option 3: Keep the driver package attached, even with the unreferenced files. If submitting to HDC, please see this documentation for any policy updates regarding submissions with unreferenced files.
If creating a DUA package...
- Option 1 (recommended): Replace the attached driver package with a new one. Before re-attaching, remove any unreferenced files from the driver package.
- Option 2: Create a new original submission. Modify the .inf to reference all the attached files. Re-test the driver and attach the modified driver package.
- Option 3: Keep the driver package attached, even with the unreferenced files. If submitting to HDC, please see this documentation for any policy updates regarding submission with unreferenced files.

Tips

The new unreferenced file check supports most compressed files.
- If a file is compressed and its extension ends in “_”, the new warning will not appear so long as the decompressed version of the file is properly referenced by the .inf.
- If a .cab is included as a source location in the .inf’s [SourceDisksNames] section, HLK will examine the .cab’s contents during the unreferenced file check.
- If a .cab is referenced as a driver file in the .inf, it will be treated as such during the unreferenced file check, and the .cab’s contents will not be examined.
What is not supported:
- Attaching compressed .cat files.
- Attaching double-compressed files (e.g. A user compresses a file individually, and then packs the already-compressed file into a cab. Or a user compresses files into a .cab, and then compresses the .cab a second time so it now ends with an underscore).

Troubleshooting

Issue: “Failed to analyze driver package for unreferenced files”

This means that the HLK was not able to successfully finish the unreferenced file check. It does not indicate whether the attached files were referenced or not. Confirm there are no files missing from the attached driver package (i.e. the .inf referenced a file, but the file wasn’t attached).

Issue: A file is being identified as unreferenced, but the .inf includes the file.

It could be that the file is included in the .inf, but the .inf section that it’s in is not referenced properly. Run infverif to identify any unreferenced sections.

Also, check whether the file should (or should not) be placed under a subdirectory. The relative path of each driver file in the attached package must exactly mirror what is specified in the .inf file.

Issue: An .inf is being identified as an unreferenced file.

Confirm that the .inf is placed at the top root of the driver package (not in a subdirectory).

Issue: How do I check whether a file is signed?

Please see How to validate the Microsoft signature - Windows drivers | Microsoft Learn

PackageWriter.AddDriver Method | Microsoft Learn

PackageWriter.AddReplacementDriver Method | Microsoft Learn

Creating a Package | Microsoft Learn

For additional questions/assistance, please reach out to Microsoft support team by creating a support ticket here - Windows HLK Support

Updates to HLK Waiver Management - Coming Soon

AndyW — Wed, 18 Feb 2026 18:02:48 GMT

The HLK Team is making some updates to how waivers are tracked internally. This will not have any effect on the submission process at a high-level; filters will be published/downloaded in the same way, filters will get applied in the HLK the same way, and manual waivers will be applied to submissions in the same way. However, the IDs of all manual waivers will be updated because of the switch (IDs for waivers with automatic filters will remain the same).

We are aware that many of you keep track of waiver numbers internally so that you can track status/expiration and report to Microsoft if there are issues. So, if you have a list of waiver numbers that you track, please check the linked conversion table to prepare for the updated IDs for manual submissions.

To make the transition easier, there will be a grace period of 4 months after the effective date where submissions with manual waivers that still use the old IDs will still be accepted.

What Changes:

- IDs for manual waivers

What Doesn’t Change:

- How filters are downloaded

- How filters get applied to HLK projects

- How manual waivers get applied to submissions

Effective Date:

This change will go into effect in mid-March.

Action Required:

Download the linked waiver ID conversion table
Effective July 15, 2026 (after the grace period), submissions that reference legacy manual waiver IDs will be rejected. Partners should update the submission README to reference the new manuals waiver IDs during the transition period.

Questions?

If you have any questions now or have issues with waivers after the effective date, please reach out to HLK support.

HLK February Refresh Release for Windows 11 Version 25H2 and Windows Server 2025

Cymoki — Fri, 20 Feb 2026 17:03:00 GMT

Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 25H2 and Windows Server 2025 is available starting February 17, 2026.

See below for detailed information on what’s new with this HLK refreshed version. The refreshed version of the HLK will replace the RTM version that is available on the HLK Download site. The VHLK version will be available in a week. Partners can submit to WHCP using either the RTM version of the HLK for Windows 11, version 25H2 and Windows Server 2025 or the refreshed HLK so long as passing results can be obtained (waivers acceptable).

What's new with this refresh?

We’ve introduced a small update to the HLK ARM64 Client setup experience by defaulting the emulation test setting to x86. This change aligns ARM64 client testing more closely with the existing AMD64 workflow, allowing partners to use a single, unified playlist for ARM64 testing, including both full and emulation scenarios. By reducing the need to manage multiple architecture specific playlists, we’re making it faster and easier for partners to stand up an ARM64 emulation test environment, minimize playlist configuration overhead, and focus on validating driver quality.  In the February refresh, partners can point to x86 as default emulation during automated script setup and enjoy the benefit of the single playlist deployment; in the following quarterly refresh, the default UI change will be available as well.

In addition, the refreshed kit includes a new check for unreferenced files. If the attached driver package includes one or more files that were not referenced by an .inf, a new warning will display at the end of packaging. The PackageWriter class in the Microsoft.Windows.Kits.Hardware.ObjectModel.Submission namespace has been updated to provide access to this new information from the HLK API. Please see Attention: HDC is changing the policy on signing unreferenced files in driver packages | Microsoft Community Hub for details.

25H2 Playlist updates: 

The following tables describe the playlist changes included with this refresh.

Removed tests:

GUID	TestName
7bcca3c4-3853-4f22-8eb2-effa2feeba57	Bluetooth - LE Audio VSAP (Broadcast) - [Render] Default, 32_1, 1 channel
4a3813a2-b24c-4784-b932-f2aa1e559747	Bluetooth - LE Audio VSAP (Broadcast) - [Render] Default, 32_1, 1 channel
25a4e032-246f-491d-b246-5be7dd8abb3e	Bluetooth - LE Audio VSAP (Broadcast) - [Render] Default, 32_2, 1 channel
4981e0a5-3583-4c49-896f-8342c70d75dc	Bluetooth - LE Audio VSAP (Broadcast) - [Render] Default, 32_2, 2 channels
b88a8d7b-4e43-41c2-b8e6-e6cb63a1f431	DXGI - Hybrid WDDM 3.0
f4f5a8a2-91fe-4508-a75c-24fe46c2b1f3	Display capture tests - Display Mode Change Performance
b80af82b-6d0b-4ac5-b649-4c02c1242570	DisplayMux Acpi block test
d0aaac5c-7c4c-488c-8352-14c49bc2ac67	NDISTest 6.0 - [1 Machine] - 1c_NdisRequestCov
5d6ac688-70fd-4163-8313-ffa2922b2afd	NDISTest 6.0 - [1 Machine] - 1c_WMICoverage
5f53cf62-a767-4469-92e6-1bca087193fd	NDISTest 6.0 - [2 Machine] - 2c_Priority
16084044-7baf-48ca-abe8-ae68062bebef	RepeatPublishWriteTag
d7e5b99f-d655-484c-a4ed-6467976d7813	RepeatTagReading
0cc234e0-9513-48fd-8b5d-1ef9ce168941	RepeatTagReadingLonghaul

Added tests:

GUID	TestName	Additional Information
9d59f9d8-ca18-42db-8bc7-a50bf071af00	Driver Attribute Test	This test is being added to the playlist. It reports the version of the WDK used to build the driver package. This test does not currently cause any failures as it is reporting only.
9f351400-f4fa-42b1-8c53-7affb526ee78	GRFX Adapter - Unreleased Features Block	Our new GRFX Adapter Unreleased Features Block Test will prevent graphics drivers from showing full support for unreleased features. Once a feature has been released, we will check that the system passes the corresponding HLK tests associated with the feature and remove it from the unreleased feature list.
d3d5e718-9313-4de6-9b38-41facdfd6314	Wlan Test - Connect to an enterprise network using MLO	Adding missing test that supports existing WHCP requirements.

26H1 Playlist (only) updates, no new HLK Kit: 

Removed tests:

GUID	Test Name
b88a8d7b-4e43-41c2-b8e6-e6cb63a1f431	DXGI - Hybrid WDDM 3.0
16084044-7baf-48ca-abe8-ae68062bebef	RepeatPublishWriteTag
d7e5b99f-d655-484c-a4ed-6467976d7813	RepeatTagReading
0cc234e0-9513-48fd-8b5d-1ef9ce168941	RepeatTagReadingLonghaul
067dba2c-6ee8-48a8-bb23-11182608f64c	BitLocker TPM + PIN + USB and Recovery Password Tests
ce9e5b64-8903-4025-bccf-a99d65663cf8	BitLocker TPM and Recovery Password Tests for NONAOAC devices with Legacy PCRs
5aac52da-a57c-4a12-aaac-de878a62bb08	BitLocker Tpm And Recovery Password tests for AOAC devices with PCR[7]
8a4641a2-4fc6-4447-9d94-fdf402ca263c	BitLocker Tpm And Recovery Password tests for AOAC devices with Legacy PCR's
8c7a62bb-7f02-4a16-b37d-711cc9026e17	BitLocker TPM and Recovery Password Tests for NONAOAC devices with PCR[7]

Added tests:

GUID	Test Name	Additional Information
d3d5e718-9313-4de6-9b38-41facdfd6314	Wlan Test - Connect to an enterprise network using MLO	Adding missing test that supports existing WHCP requirements.
067dba2c-6ee8-48a8-bb23-11182608f64c	BitLocker TPM + PIN + USB and Recovery Password Tests	Replacing existing BitLocker Tpm+PIN+ USB and Recovery Password tests.
721864b7-a33e-4831-bfb3-7e04e67a6f87	BitLocker Device Encryption Test	New HLK test, doesn't raise WHCP bar as we use software APIs to determine hardware capability for DE.
ba380fe0-7d56-432e-b504-56b73201d08a	BitLocker TPM and Recovery Password Tests for AOAC devices	Replacing BitLocker Tpm and Recovery password tests for AOAC devices with PCR[7] and  BitLocker Tpm and Recovery password tests for NONAOAC devices with Legacy PCRS.
008d97d3-1535-4abe-b0c4-9663e5e12b1f	BitLocker TPM and Recovery Password Tests for NONAOAC devices with Legacy PCRs	Replacing BitLocker Tpm and Recovery password tests for NONAOAC devices with Legacy PCRS.
e922e6ac-a3ca-4e7f-a4c6-4b3ce685ec4f	BitLocker TPM and Recovery Password Tests for NONAOAC devices with PCR[7]	Replacing  BitLocker Tpm and Recovery password tests for NONAOAC devices with PCR[7].

Troubleshooting and Known Issues: 

Issue: "Failed to open package. Could not open package: (hlkx filename)" when opening HLKX generated from this release on separate system.

Submission packages from this release are generated in a new schema and a newer version of the HLK Studio is required to open it.

Solution: Install/Update to a newer of HLK or HLK Studio

Existing HLK Controller installations may be kept as is and do not need to be reinstalled as it is not supported to update just the HLK Studio on an existing HLK Controller instance. An HLK Studio only instance from the latest HLK may be installed on a separate system to open these HLKXes.

Issue: Wi-Fi tests regressed due to removal of TestNetv2.0 dependencies.

The TestNetv2.0 was removed from the HLK test infrastructure, causing some Wi-Ffi tests to regress due to not being able to invoke “testnetv2.0/ccrun.exe”. The list of affected tests can be found below:

Wi-Fi Direct Basic Discovery Tests – Functional
Wi-Fi Direct Basic Pairing Tests – Functional
Wi-Fi Direct Basic Reconnect Tests – Functional
Wi-Fi Direct Legacy Pairing Tests – Functional
Wi-Fi Direct Service Discovery Tests – Functional
Wi-Fi Direct Service Pairing and Reconnect Tests – Functional

This issue will be fixed on a future refresh of the 25H2 Hardware Lab Kit

Frequently Asked Questions

What HLK version is being refreshed?
- The 25H2 RTM HLK is being refreshed, this HLK helps support certifying drivers for Windows 11, version 25H2 and Windows Server 2025. For the following FAQ’s, the 25H2 RTM release will be referenced to as “RTM HLK” and the upcoming release in February 2026 will be referenced as “refresh HLK.”
How can I tell what version of the HLK I have?
- The distinction between RTM HLK and refreshed HLK will be in the last digits of the HLK studio version, 10.1.26100.X
  - The RTM HLK Studio version is 10.1.26100.1
  - The refresh HLK Studio version is 10.1.26100.X

The HLK Studio version information can be located by clicking ‘About’ in the upper right corner of studio.

How do I install the refreshed version of the HLK?

1. To install the refreshed version of the HLK, visit the HLK download page: Windows Hardware Lab Kit | Microsoft Learn
2. Download the refreshed HLK
3. Run HLKSetup.exe

Notes

- Ensure your current HLK projects are finished before attempting to use the same system for the HLK refresh.
- The refreshed HLK cannot be installed on a system that already has the RTM HLK, this goes for both Controller and Client. It is highly recommended to start with a clean install of the OS for both.

How should I address a test that was passing on the RTM HLK but now failing on the refreshed HLK?
- Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
- Next, open a CSS case. Click the following link for more information on opening a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

Going forward, will Microsoft be updating the HLK regularly?
- Yes, Microsoft is transitioning into this servicing model for the HLK, which maintains overall test quality and reduces dependency on errata.

How often are the HLK refresh releases expected?
- Our current plan is to evaluate releasing a refreshed HLK each quarter.

Does this update apply to client and server?
- Yes

Can results from an RTM test run and a Refreshed test run be merged and used for submission?
- No, submission should be completed with either the RTM or refreshed HLK.

Will the refreshed HLK continue to support merged packages for multiple-OS submissions?
- Yes

Is the VHLK also going to be updated?
- Yes

Windows Hardware Compatibility Program - Guidance for Windows 11, version 26H1 Release

AndyW — Tue, 18 Nov 2025 22:55:15 GMT

Building on the recent WIP Blog post, we’re releasing WHCP and HLK for Windows 11, version 26H1 to support partners working on engineering efforts.

This release is focused on enabling new platforms and is not intended for existing or previously released silicon. For mainstream products, continue using Windows 11 version 25H2 and its HLK to maintain compatibility with the current Windows 11 release.

There’s no expectation for most devices or components to certify on both 25H2 and 26H1.

Submission Pre-requisites

If you’re submitting for 26H1, please ensure:

OS Version: Windows 11, version 26H1 (Build 28000)
HLK Version: Windows 11, version 26H1 (Build 28000), and using the matching 26H1 Playlist
Downloads:

o HLK - Windows Hardware Lab Kit

o Playlists - https://aka.ms/HLKPlaylist

Target Architecture

Required Playlist(s)

ARM64

HLK Version 26H1 CompatPlaylist x64 ARM64.xml

HLK Version 26H1 CompatPlaylist ARM64_x86_on_ARM64.xml

X64

HLK Version 26H1 CompatPlaylist x64 ARM64.xml

System-Level Submissions: Must use 26H1 certified/signed drivers

This alignment ensures consistency across WHCP and HLK for silicon enablement and validation.

To avoid submission rejection, all required playlists and tests must be fully executed. For devices with ARM64 processors, HLK must run on each required playlist listed above, and the resulting logs should be included for submission.

Please refer to the HLK Getting Started Guide for details on HLK client setup and playlist use.

Partner Dev Center Opening Date

Starting from 11/18/2025, Partner Dev Center will accept submissions for Windows 11, version 26H1 packages that meet the pre-requisites mentioned above.

FAQ

Q: Will there be a 90-day transition period for system-level submission?

A: No – Since this release emphasizes new platform support, all components and drivers are expected to qualify under the same release. Therefore, the traditional 90-day transition period does not apply. In other words, system-level submissions for 26H1 must preinstall with drivers that are certified and signed for 26H1.

Q: Can a pre-released version of OS and/or HLK be used for submission?

A: No – To ensure full compatibility, HLK logs generated from the final release of both the OS and HLK are required for 26H1 submissions.

Windows Hardware Compatibility Program - Windows 10 Certification Deprecation Plan

AndyW — Tue, 07 Oct 2025 19:14:52 GMT

As part of our ongoing commitment to transparency and ecosystem readiness, we are sharing the Windows Hardware Compatibility Program (WHCP) and Hardware Lab Kit (HLK) end-of-support plan for Windows 10, in alignment with its upcoming end-of-support (EOS) milestone on October 14, 2025.

Key Updates

WHCP Windows 10 Certification Deprecation

WHCP will begin deprecating the certification process for Windows 10 following its official end-of-support date on October 14, 2025. Windows 10 LTSC 2021 release (22H2) and HLK 22H2, which will remain supported through the Extended Security Updates (ESU) program in 2026.

For Windows Server certification, HLK versions 1809 and 22H2 will continue to be used for Windows Server LTSC releases until their respective EOS dates described under Server Policy. https://aka.ms/WHCP

How this deprecation affects you

Hardware Dev Center

o HDC will continue to accept HLK packages for all Windows 10 versions. We will announce timelines for when HDC will stop accepting packages built on unsupported HLK and Windows 10 versions. Further announcements on the timeline will be shared on our blog.

o Partners are strongly encouraged to transition to supported HLK versions to avoid disruptions in certification workflows.

HLK & Windows 10 Supports

o Effective October 14, 2025, Microsoft will end support for all unsupported Windows 10 versions and their corresponding HLK releases, except for the versions supported through Extended Security Updates (ESU) and Windows Server LTSC programs. After this date, Microsoft Premier Support will no longer accept HLK cases for unsupported versions.

o As of October 14, 2025, downloads for unsupported HLK releases will be removed from https://learn.microsoft.com/en-us/windows-hardware/test/hlk/.

This deprecation plan is designed to provide clarity and predictability as we collectively transition toward modern platforms. For additional context on the Windows 10 ESU program and lifecycle, please refer to the public announcement: https://techcommunity.microsoft.com/blog/windows-itpro-blog/when-to-use-windows-10-extended-security-updates/4102628.

Stay secure with Windows 11, Copilot+ PCs and Windows 365 before support ends for Windows 10 | Windows Experience Blog

We appreciate your continued partnership and look forward to supporting your success through this transition.

Windows Hardware Compatibility Program - Guidance for Windows 11, version 25H2 Release

AndyW — Fri, 03 Oct 2025 21:14:45 GMT

To support the Windows 11, version 25H2 release, the Windows Hardware Compatibility Program is set to accept submission for the release. However, any submission package must meet the pre-requisites to help ensure compatibility between OS and HLK.

Windows Hardware Compatibility Requirements – Windows 11, version 25H2

https://aka.ms/whcp

Submission Pre-requisites

OS and HLK minimum acceptable build

o Windows 11, version 25H2 (Build 26200.6584)

o HLK Kit version will display as 26100.6584

Playlist and Kits –
- https://aka.ms/HLKPlaylist
- https://go.microsoft.com/fwlink/?linkid=2335804

The table below illustrates the required playlists for testing each processor architecture:

Target Architecture

Required Playlist(s)

ARM64

HLK Version 25H2 CompatPlaylist x64 ARM64.xml

HLK Version 25H2 CompatPlaylist ARM64_x86_on_ARM64.xml

X64

HLK Version 25H2 CompatPlaylist x64 ARM64.xml

Please refer to the HLK Getting Started Guide for details on HLK client setup and playlist use.

Deferment of Partner Dev Center SBOM Validation

The WHCP SBOM requirement (Device.DevFund.Security.SoftwareBillofMaterials) is deferred and will be enforced by Hardware Dev Center for CRA compliance beginning in H2 of 2026. However, Microsoft recommends all driver submissions to include SBOMs. Additional guidance for Device.DevFund.Security.SoftwareBillofMaterials will be provided in advance to H2 2026.
Partners will be given notice as soon as there is a set enforcement date during a future release, along with guidance on how to meet any new requirements.

WHCP continues to support a secure supply chain throughout our signing process. That said, the EO on Cyber Security is a call to action from the U.S. Government, so we continue to encourage that our partners seek to enable a secure supply chain as stated in the NIST guidance.

90-day N-1 Driver Transition Period for System-level submissions

To qualify for Windows 11, version 25H2 system-level qualification with Windows 11, 24H2 qualified drivers, the standard 90-day transition period can be applied through 01/09/2026.
Errata 225900 is available to filter the “System Logo Check” failure when testing Windows 11, version 25H2 system with Windows 11, version 24H2 qualified drivers. To apply, please download and apply the latest Errata Filter Package

HLK July Refresh Release for Windows 11 Version 24H2 and Windows Server 2025

Cymoki — Tue, 08 Jul 2025 20:53:43 GMT

Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 is available starting July 8, 2025.

This release of the HLK contains only infrastructure changes. See below for detailed information on what’s new with this HLK refreshed version. The refreshed version of the HLK will replace the RTM version that is available on the HLK download site. The VHLK version will be available in a week. Partners can submit to WHCP using either the RTM version of the HLK for Windows 11, version 24H2 and Windows Server 2025 or the refreshed HLK so long as passing results can be obtained (waivers acceptable).

What's new with this refresh?

Upcoming HLKX Packager changes

This HLK refresh will increment the HLKX packager version to a newer version, the data format will not be readable by previous versions of the HLK Studio. Opening an HLKX saved from this version will fail with the message text "Failed to open package. Could not open package: (hlkx filename)" when opened from previous releases of the HLK Studio and will require installation of this version or newer to read it. HLK Studio in this refresh will continue to be backwards compatible and will be able to read, merge, and add drivers to submission packages that were saved from current and previous releases of the HLK.

Note that the HLK Installer supports installation of the HLK Studio components only to read and write HLKXes if HLK Controller functionality is not needed.

The submission portal will continue to accept HLKXes from older versions of the HLK, but any HLKX submitted after the switchover will return Driver Update Acceptable (DUA) HLKX shells in the new format when requested, while HLKXes submitted prior to the switchover will continue to be in the previous format. Without the refreshed HLK, the update will not be able to read and process DUA HLKX shells in the new format.

Action Required:

Note that HLKX files created in this release of the HLK will be generated in an updated format version. The user should be aware of scenarios which will and will not require an update to this version of the HLK or HLK Studio.

HLKXes generated from this release will be readable by this and future versions of the HLK Studio.
HLK Studio from previous releases of the HLK will not be able to read the data format of the upcoming version.
This release of the HLK is backwards compatible and will also be able to read HLKXes and HCKXes from current and past versions of the HLK.

Troubleshooting and Known Issues:

Issue: "Failed to open package. Could not open package: (hlkx filename)" when opening HLKX generated from this release on separate system.

Submission packages from this release are generated in a new schema and a newer version of the HLK Studio is required to open it.

Solution: Install/Update to a newer of HLK or HLK Studio

Issue: "Failed to open package. Could not open package: (hlkx filename)" when opening DUA shell downloaded from submission portal.

After the portal switches over to processing submissions in the new format, DUA shells for submission packages submitted to the portal after the switchover will return them in the new format. These DUA shells will not be readable without an HLK Studio installation that does not have the updated changes and will return the error "Failed to open package. Could not open package: (hlkx filename)"

Solution: HLK/HLK Studio instance should be updated to newer version.

Issue: Reinstall of HLK Controller fails with “Install did not complete successfully: An error occurred installing ‘Windows Hardware Lab Kit Infrastructure’”

This issue is caused by a missing check in the HLK installer to detect whether a newly supported version of SQL is already installed. When this occurs, the HLK SQL installer fails due to an existing instance with the same instance name.

Workaround:

After uninstalling the Hardware Lab Kit on the HLK Controller system:

Right-click on the “Start” button on the Windows taskbar and select the “Settings” menu option to launch the Windows Settings app.
From the Windows Settings app, select the “Apps” option, then select “Installed Apps”
Look for the item “Microsoft SQL Server 2022 (64-bit)” and uninstall it.
Attempt to install the Hardware Lab Kit again and confirm that it completes without errors.

This issue will be fixed on a future refresh of the 24H2 Hardware Lab Kit.

Issue: HLK Studio may throw InvalidOperationException when selecting targets

Enabling the Distributed Target Selection feature in HLK Studio may cause HLK Studio to crash with the error: “System.InvalidOperationException: A TwoWay or OneWayToSource binding cannot work on the read-only property 'RedistributeTests.'”

Workaround:

If this issue occurs in HLK Studio, disable the Distributed Target Selection feature.

From HLK Studio, select the “Configuration” menu option.
Select the “Options” item on the left side of the user interface
Under the “Distributed Testing” group box, look for the “Show Distributed Target Selection dialog when multiple matching targets are found” checkbox and uncheck it.
Confirm that the InvalidOperationException is no longer thrown when selecting targets in HLK Studio.

This issue will be fixed on a future refresh of the 24H2 Hardware Lab Kit.

Issue: Wifi tests regressed due to removal of TestNetv2.0 dependencies

The TestNetv2.0 was removed from the HLK test infrastructure, causing some Wifi tests to regress due to not being able to invoke “testnetv2.0/ccrun.exe”. The list of affected tests is:

- Wi-Fi Direct Basic Discovery Tests – Functional

- Wi-Fi Direct Basic Pairing Tests – Functional

- Wi-Fi Direct Basic Reconnect Tests – Functional

- Wi-Fi Direct Legacy Pairing Tests – Functional

- Wi-Fi Direct Service Discovery Tests – Functional

- Wi-Fi Direct Service Pairing and Reconnect Tests – Functional

This issue will be fixed on a future refresh of the 24H2 Hardware Lab Kit

Frequently Asked Questions

What HLK version is being refreshed?

The May refresh HLK is being refreshed, this HLK helps support certifying drivers for Windows 11, version 24H2 and Windows Server 2025. For the following FAQ’s, the May 2024 release will be referenced to as RTM HLK and the upcoming release in July 2025 will be referenced as refresh HLK.

How can I tell what version of the HLK I have?

The distinction between RTM HLK and refreshed HLK will be in the last digits of the HLK studio version, 10.1.26100.X

The RTM HLK Studio version is 10.1.26100.1
The refresh HLK Studio version is 10.1.26100.X

The HLK Studio version information can be located by clicking ‘About’ in the upper right corner of studio

How do I install the refreshed version of the HLK?

Visit the HLK download page: Windows Hardware Lab Kit | Microsoft Learn
Download the refreshed HLK
Run HLKSetup.exe

Notes

Ensure your current HLK projects are finished before attempting to use the same system for the HLK refresh.
The refreshed HLK cannot be installed on a system that already has the RTM HLK, this goes for both Controller and Client. It is highly recommended to start with a clean install of the OS for both.

How can I tell if the errata I use was fixed in the refreshed HLK?

The list of errata fixed is available below

What do I do if the errata I use doesn’t appear to be fixed in the refreshed HLK?

If the errata is not on the fixed list the waiver can be used on both the RTM HLK as well as the refreshed HLK

What do I do if the errata I use is listed as fixed, but failures are still being seen in the test?

Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

How should I address a test that was passing on the RTM HLK but now failing on the refreshed HLK?

Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

Going forward, will Microsoft be updating the HLK regularly?

Yes, Microsoft is transitioning into this servicing model for the HLK, which maintains overall test quality and reduces dependency on errata.

How often are these refresh releases expected?

Current plan is to evaluate releasing a refreshed HLK each quarter.

Does this update apply to client and server?

Can results from an RTM test run and a Refreshed test run be merged and used for submission?

No, submission should be completed with either the RTM or refreshed HLK.

Will the refreshed HLK continue to support merged packages for multiple-OS submissions?

Is the VHLK also going to be updated?

Action Required: HLK Submission Packager Changes Coming in July

AndyW — Tue, 24 Jun 2025 21:55:10 GMT

The Hardware Lab Kit (HLK) packaging component is important for reading, writing, and packaging test results, as well as submitting drivers to the Hardware Dev Center (HDC) portal for certification and signing.

What’s Changing?

In July, an upcoming HLK refresh will update the submission packager version and format. Submission packages generated using this HLK refresh will be saved in a new data format and will not be readable by previous versions of HLK Studio.
The updated packaging components can read both current and previous data formats but will always write HLKX files in the new format. Older versions of the HLK Studio will not be able to read submission packages written in the new format.
The above applies to DUA HLKX packages as well.
The HDC portal will synchronize deployment of the new submission package format with the upcoming HLK refresh. .

Actions Required

To enable compatibility with the new format:

Watch for a notification and an upcoming HLK release announcement regarding the switch to the new submission package version and format on this blog and on the HDC portal.
Installations of older HLK Controller versions do not require updates for this scenario as submission packages from older versions of the HLK will continue to be accepted by the portal. An HLK Studio only instance can be installed on a separate system for opening and processing a DUA shell package returned after the update,
If the error "Failed to open package. Could not open package: (hlkx filename)" is encountered when opening a submission package in HLK Studio, it is recommended to install a newer version of HLK/HLK Studio. This error message may be indicating that the updated version of HLK Studio is necessary to read the latest submission package format.
Automation and tools utilizing the HLK Object Model may require additional dependencies to be deployed due to updates in these dependencies. These changes will be detailed in the HLK Documentation upon the release of the update.

HLK May Refresh Release for Windows 11 Version 24H2 and Windows Server 2025

AndyW — Tue, 10 Jun 2025 18:38:54 GMT

Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 is available starting May 6, 2025.

This release of the HLK contains test errata fixes, HLK test removals, and HLK test additions. All these changes will help keep the overall test quality high while helping reduce triage time for known test issues. See below for detailed information on what’s new with this HLK refreshed version. The refreshed version of the HLK will replace the RTM version that is available on the HLK download site. The VHLK version will be available in a week. Partners can submit to WHCP using either the RTM version of the HLK for Windows 11, version 24H2 and Windows Server 2025 or the refreshed HLK so long as passing results can be obtained (waivers acceptable).

Errata that are fixed in the refreshed version are expected to expire 90 days after the release of the refreshed HLK. As we transition into this servicing model, which maintains overall test quality and reduces dependency on errata, we acknowledge that the refreshed HLK may not address all scenarios. If any errata remain relevant after using the refreshed HLK, please contact CSS for assistance. For more details, please review the Frequently Asked Questions.

What's New with this Refresh?

HLK Errata Fixed

Errata ID	Title	OS Platform
125009	HLK Errata: Bluetooth - Audio - Sink/Source increase music volume with A2DP offload failed with "Assertion failed: initialSinkVolume.VolumeLeft < currentSinkVolume.VolumeLeft"	Client
10746	Errata Waiver: DF - *: Disk Data Plugin reporting MPIO/SCSI Disk doesn't have volume (Server folks to help with Server hardware repro)	Client, Server
138640	HLK Errata - Human Presence Settings UpdateSettings Validation Test Failure after the deprecation of IsAttentionAwareDimmingEnabled	Client
167069	Light Sensor Calibration Test Crash due to Null Reading	Client
170261	Multi person Sensors tests do not need to support distance Test: Data Field Verification	Client
181716	Light Sensor Color Calibration Test Crash due to Null Reading	Client
195343	HLK Errata: Update Settings Validation Test is Failing with AreEqual(settingsAfterUpdate->WakeOptions->DisableWhenBatterySaverOn, !settings->WakeOptions->DisableWhenBatterySaverOn) - Values (0	Client
196092	Human Presence capable Proximity Sensor Data Field Properties Verification Test	Client
200026	HLK Errata: Update Settings Validation Test is Failing with AreEqual(settingsAfterUpdate->LockOnLeaveDistanceInMillimeters->Value, unsigned int{42}) - Values (1200, 42)	Client
201650	Errata: Human Presence capable Proximity Sensor Thresholds Verification Test	Client
201651	Errata: Human Presence capable Proximity Sensor Dynamic Range Tests	Client
163077	[OS ERRATUM] Lullaby2's asynchronous test fails on Ge due to policy changes for Modern Standby	Client, Server
205750	HLK Manual Errata: Bluetooth - HciExtensions OR HciExtensionsV2 OR LEExtendedAdvertising tests fail	Client
196263	HLK Errata: DisplayPolicy OEM::VerifyCommonColorProfileProblems() test failing	Client Server

Playlist updates:

Removed 3 camera tests:

GUID	TestName
4fc2e6cb-a474-404b-85d9-59b14b7e894e	Camera Driver System Test - MediaCapture - TestAlternateSecureAndClearMode
b4ee9abe-2b7c-4170-8da1-108bfedc91f4	Camera Driver System Test - MediaCapture - TestSecurePinAllMediaTypes
a7d4a8d2-99f1-4460-8d5b-5deb340e87c8	Camera Driver System Test - MediaCapture - TestSecureTimeStamps

Added 21 Bluetooth tests, as “if-implemented” tests only:

GUID	TestName
51daf9fb-626b-42f8-bc5c-1b8e86c116f7	Bluetooth LE Audio VSAP - 16_1 stereo render; 16_1 mono capture
e16b9436-2c56-4d13-9bd7-4282e38067f4	Bluetooth LE Audio VSAP - 16_1 stereo render; 16_2 mono capture
1c45b432-9c35-485f-bcd1-187518434fdf	Bluetooth LE Audio VSAP - 16_2 stereo render; 16_1 mono capture
f1958295-ac52-4434-b78e-6ce070ea9dfb	Bluetooth LE Audio VSAP - 16_2 stereo render; 16_2 mono capture
dd3b3fe6-a1f5-4657-a693-11c4f4003961	Bluetooth LE Audio VSAP - 24_1 stereo render; 24_1 mono capture
b5d3685f-8c23-4e0e-82de-8df15e9b7b9b	Bluetooth LE Audio VSAP - 24_1 stereo render; 24_2 mono capture
7af31d38-8793-4fa6-82f9-10ee34445cb3	Bluetooth LE Audio VSAP - 24_2 stereo render; 24_1 mono capture
1aaf70cd-f0a9-4152-b41d-dce5f8777432	Bluetooth LE Audio VSAP - 24_2 stereo render; 24_2 mono capture
4ce0fc40-7e5b-4550-8c01-f429b12fd7e3	Bluetooth LE Audio VSAP - 32_1 stereo render; 32_1 mono capture
c1bb6468-0178-4990-8e4a-c8ce4c88930b	Bluetooth LE Audio VSAP - 32_1 stereo render; 32_2 mono capture
0f03e870-01d1-4676-ae94-539d306beec5	Bluetooth LE Audio VSAP - 32_2 stereo render; 32_1 mono capture
7ea8bb1-f906-4644-9146-bb262ba55513	Bluetooth LE Audio VSAP - 32_2 stereo render; 32_2 mono capture
9f461832-16db-434a-ae84-c512d24cf960	Bluetooth LE Audio VSAP - 48_1 stereo render; 32_1 mono capture
657686f6-a61b-4c02-9aeb-bbd0b49af46c	Bluetooth LE Audio VSAP - 48_1 stereo render; 32_2 mono capture
940128a4-61fb-4904-b1d3-23482035cfdf	Bluetooth LE Audio VSAP - 48_2 stereo render; 32_1 mono capture
849e0fd7-8010-445b-a7ef-29d40f79bb94	Bluetooth LE Audio VSAP - 48_2 stereo render; 32_2 mono capture
0784f26f-6575-4146-9f1a-7e71aca282c1	Bluetooth LE Audio VSAP - 48_3 stereo render; 32_1 mono capture
345a0037-8cfa-4608-861b-490207661438	Bluetooth LE Audio VSAP - 48_3 stereo render; 32_2 mono capture
188ad2c2-2efd-422f-bd08-6df77165dbd7	Bluetooth LE Audio VSAP - 48_4 stereo render; 32_1 mono capture
d2a0e70f-ed79-4c0b-a338-8128dad0f59d	Bluetooth LE Audio VSAP - 48_4 stereo render; 32_2 mono capture
ed8298b0-d1de-4ef1-ad1e-2af4a0e57aa6	Bluetooth LE Audio VSAP - Mandatory formats

Update to Gen2 VM for VHLK

To help enhance compatibility with the latest technologies and offer customers optimal VM options, the VHLK's vhdx image has been updated to operate as a Generation 2 VM. As a result, during the VHLK VM setup, you should select Generation 2 instead of Generation 1. All other setup steps remain unchanged.

Action Required:

After this update is released, please modify your VHLK setup process or automation to configure the VM as Generation 2.

Known Issues:

Issue:

Users running the HLK Controller on Windows Server 2016 have reported missing content starting with the September HLK refresh. This issue is caused by a regression where the HLK Controller installer no longer installs .Net Framework 4.7.1 on systems with an older version of the framework (Windows Server 2016 only includes .Net Framework 4.6.2).

.Net Framework 4.7.1 or greater is required for all HLK content to be imported properly.

Workaround:

For users running the HLK Controller on Windows Server 2016 OS, please install .Net Framework 4.7.1 or a later version (4.8 is latest version supporting Windows Server 2016) onto your system before installing the HLK Controller.

No action is required for users running Windows Server 2019 or later as their HLK Controller OS, since these server versions already include .Net Framework 4.7.2 or greater.

Please note, in future CD refresh, we plan to remove support for running the HLK Controller on Windows Server 2016 OS. It is highly recommended to switch to Windows Server 2019, 2022, or 2025 for the HLK Controller.

Frequently Asked Questions

What HLK version is being refreshed?

The February refresh HLK is being refreshed, this HLK helps support certifying drivers for Windows 11, version 24H2 and Windows Server 2025. For the following FAQ’s, the May 2024 release will be referenced to as RTM HLK and the upcoming release in May 2025 will be referenced as refresh HLK.

How can I tell what version of the HLK I have?

The distinction between RTM HLK and refreshed HLK will be in the last digits of the HLK studio version, 10.1.26100.X

The RTM HLK Studio version is 10.1.26100.1
The refresh HLK Studio version is 10.1.26100.X

The HLK Studio version information can be located by clicking ‘About’ in the upper right corner of studio

How do I install the refreshed version of the HLK?

Visit the HLK download page: Windows Hardware Lab Kit | Microsoft Learn
Download the refreshed HLK
Run HLKSetup.exe

Notes

Ensure your current HLK projects are finished before attempting to use the same system for the HLK refresh.
The refreshed HLK cannot be installed on a system that already has the RTM HLK, this goes for both Controller and Client. It is highly recommended to start with a clean install of the OS for both.

How can I tell if the errata I use was fixed in the refreshed HLK?

The list of errata fixed is available below

What do I do if the errata I use doesn’t appear to be fixed in the refreshed HLK?

If the errata is not on the fixed list the waiver can be used on both the RTM HLK as well as the refreshed HLK

What do I do if the errata I use is listed as fixed, but failures are still being seen in the test?

Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

How should I address a test that was passing on the RTM HLK but now failing on the refreshed HLK?

Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

Going forward, will Microsoft be updating the HLK regularly?

Yes, Microsoft is transitioning into this servicing model for the HLK, which maintains overall test quality and reduces dependency on errata.

How often are these refresh releases expected?

Current plan is to evaluate releasing a refreshed HLK each quarter.

Does this update apply to client and server?

Can results from an RTM test run and a Refreshed test run be merged and used for submission?

No, submission should be completed with either the RTM or refreshed HLK.

Will the refreshed HLK continue to support merged packages for multiple-OS submissions?

Is the VHLK also going to be updated?

HLK Feb Refresh Release for Windows 11 Version 24H2 and Windows Server 2025

AndyW — Tue, 18 Feb 2025 21:51:18 GMT

Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 will be available, February 18, 2025.

This release of the HLK contains test errata and HLK infrastructure fixes, which will help keep the overall test quality high while helping reduce triage time for known test issues. See below for detailed information on what’s new with this HLK refreshed version. The refreshed version of the HLK will replace the RTM version that is available on the HLK download site. This version of the HLK will be available in ISO format for download. The VHLK version will be available in a week. Partners can submit to WHCP using either the RTM version of the HLK for Windows 11, version 24H2 and Windows Server 2025 or the refreshed HLK so long as passing results can be obtained (waivers acceptable).

What's New with this Refresh?

HLK Release

In this HLK refresh release, the update will be provided through an ISO file. To enable a smooth deployment, please mount the ISO file before your automation system initiates the deployment process. Mounting the ISO is important, as it helps make the contents of the file accessible to the system, allowing the automated process to detect and install the update properly. If the ISO is not mounted beforehand, the deployment may fail or experience delays.

Update to Gen2 VM for VHLK

Action Required:

After this update is released, please modify your VHLK setup process or automation to configure the VM as Generation 2.

Errata Fixed

ID	Title	Job/Task Failing
192434	[HLK Errata] Driver Isolation DV failures for snxppamd.sys accessing 'PARALLEL PORTS' registry key	DV - EnumerateEvents
193981	Delayed enforcement for 2411 DrvIso enforcement bar tightening	DV - EnumerateEvents
165636	HLK Errata: DF-Sleep with IO During (reliability) test failure when targeting the USB controller when this has a USB WLAN device connected	DF-Sleep with IO During (reliability) test
168780	Auto Triage: Elan USB HID driver "DF-PNP Surprise Remove Device Test(Reliability)" and "DF-PNP Rebalance Fail Restart Device Test (Reliability) failed on HLK : Win11 24H2 Build_26090 and 26100	DF-PNP Surprise Remove Device Test(Reliability) DF-PNP Rebalance Fail Restart Device Test (Reliability)
185842	Manual Errata Windows Server 2025 DF - PNP DIF Remove Device Test (Reliability)	DF - PNP DIF Remove Device Test (Reliability)
190205	[HLK Errata] DF test failures with NtCreateFile API failed - Windows Lan Manager Redirector error on Location driver	DF- *
187878	HLK Errata: Multiple DF - PNP test items fail with Timeout	DF - PNP Cancel Remove Device Test (Reliability) DF - PNP Cancel Stop Device Test (Reliability) DF - PNP DIF Remove Device Test (Reliability) DF - PNP Disable And Enable Device Test (Reliability) DF - PNP Rebalance Fail Restart Device Test (Reliability) DF - PNP Rebalance Request New Resources Device Test (Reliability) DF - PNP Remove Device Test (Reliability) DF - PNP Stop (Rebalance) Device Test (Reliability) DF - PNP Surprise Remove Device Test (Reliability)
160201	HLK Errata: Non Power 2 Conditional on 9on12	Non Power 2 Conditional
75335	HLK Errata: Win6_4.MBN.GSM.TestMPDP is failing with error "Attempt to download web doc, failed"	Win6_4.MBN.GSM.TestMPDP
193247	TpmAuxiliary Test ActivateCredentialTest RSA 3k failure	TPM 2.0 TpmAuxiliaryTest::ActivateCredentialTest
178481	Manual Errata tests not applicable to Windows Server 2025 Server Virtualization Validation Program (SVVP) validated solutions	Secure Boot Manual Logo Test
196263	HLK Errata: DisplayPolicy OEM::VerifyCommonColorProfileProblems() test failing	InternalPanel - Common color profile problems
176497	Delayed Enforcement Errata: Pending implementation and support in MSFT pluton driver	Directed FX System Verification Test
166550	Manual Errata: Non Power 2 Conditional Test (DX9) (WoW64) Non Power 2 Conditional Test (WoW64) failures (tests should not be on the playlist)	Non Power 2 Conditional Test (DX9) (WoW64) Non Power 2 Conditional Test (WoW64)
175039	[HLK Manual Errata]: NDIS test failed due to the certificate in HLK Studio is out of date	[NdisStudio] OidRequestTest - OID_GEN_VENDOR_DRIVER_VERSION Verification [NdisStudio] OidRequestTest - OID_GEN_VENDOR_ID Verification [NdisStudio] OidRequestTest - OID_GEN_XMIT_OK and OID_GEN_RCV_OK Verification [Network Adapter] Verification for network

General HLK Infrastructure bug fixes

Fix for special cases of creating Partial Package
The gatherer has been updated to better help handle systems with large sets of sibling devnodes
Minor update to address edge-case scenario is scheduling logic

Playlist updates:

Removed EDID 1.3 and DDC (WoW64) test from the WHCP x86 on ARM64 emulation playlist
Removed Non Power 2 Conditional Test (DX9) (WoW64) Non Power 2 Conditional Test (WoW64)
Moved WoW64 graphics tests from x64Emulation playlist to x86Emulation playlist as these tests use x86 path instead of x64, moving these tests left the HLK Version 24H2 CompatPlaylist ARM_x64_on_ARM64.xml playlist without any tests, leading to its removal.

Known Issues:

Issue:

.Net Framework 4.7.1 or greater is required for all HLK content to be imported properly.

Workaround:

No action is required for users running Windows Server 2019 or later as their HLK Controller OS, since these server versions already include .Net Framework 4.7.2 or greater.

Frequently Asked Questions

What HLK version is being refreshed?

The October refresh HLK is being refreshed, this HLK helps support certifying drivers for Windows 11, version 24H2 and Windows Server 2025. For the following FAQ’s, the May 2024 release will be referenced to as RTM HLK and the upcoming release in February will be referenced as refresh HLK.

How can I tell what version of the HLK I have?

The distinction between RTM HLK and refreshed HLK will be in the last digits of the HLK studio version, 10.1.26100.X

The RTM HLK Studio version is 10.1.26100.1
The refresh HLK Studio version is 10.1.26100.X

The HLK Studio version information can be located by clicking ‘About’ in the upper right corner of studio

How do I install the refreshed version of the HLK?

Visit the HLK download page: Windows Hardware Lab Kit | Microsoft Learn
Download the refreshed HLK
Run HLKSetup.exe

Notes

Ensure your current HLK projects are finished before attempting to use the same system for the HLK refresh.
The refreshed HLK cannot be installed on a system that already has the RTM HLK, this goes for both Controller and Client. It is highly recommended to start with a clean install of the OS for both.

How can I tell if the Errata I use was fixed in the refreshed HLK?

The list of errata fixed is available below

What do I do if the errata I use doesn’t appear to be fixed in the refreshed HLK?

If the errata is not on the fixed list the waiver can be used on both the RTM HLK as well as the refreshed HLK

What do I do if the errata I use is listed as fixed, but failures are still being seen in the test?

Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

How should I address a test that was passing on the RTM HLK but now failing on the refreshed HLK?

Triage the failure first. There have been cases where a test issue is fixed, and the failure is still present, but it is due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

Going forward, will Microsoft be updating the HLK regularly?

Yes, Microsoft is transitioning into this servicing model for the HLK, which maintains overall test quality and reduces dependency on errata.

How often are these refresh releases expected?

Current plan is to evaluate releasing a refreshed HLK each quarter.

Does this update apply to client and server?

Can results from an RTM test run and a Refreshed test run be merged and used for submission?

No, submission should be completed with either the RTM or refreshed HLK.

Will the refreshed HLK continue to support merged packages for multiple-OS submissions?

Is the VHLK also going to be updated?

HLK Refresh Release for Windows 11 HLK 24H2 and Windows Server 2025

Cymoki — Mon, 14 Oct 2024 22:14:16 GMT

Microsoft is pleased to announce that a refreshed HLK for Windows 11, version 24H2 and Windows Server 2025 is available today. October 14, 2024.

This release of the HLK will contain fixes for test Errata which will help keep the overall test quality high while helping reduce triage time for known test issues. The refreshed version of the HLK will replace the RTM version that is available on the HLK download site. The VHLK version will be available in a week. Partners can submit to WHCP using either the RTM version of the HLK for Windows 11, version 24H2 and Windows Server 2025 or the refreshed HLK so long as passing results can be obtained (waivers acceptable).

Errata that are fixed in the refreshed version are expected to be expired 90 days after the release of the refreshed HLK. As we transition into this servicing model, which maintains overall test quality and reduces dependency on errata, we acknowledge that the refreshed HLK may not address all scenarios. If any errata remain relevant after using the refreshed HLK, please contact CSS for assistance. For more details, please review the Frequently Asked Questions.

Frequently Asked Questions

What HLK version is being refreshed?

The HLK released in May 2024 to support certifying drivers for Windows 11, version 24H2 and Windows Server 2025. For the following FAQ’s, the May 2024 release will be referenced to as RTM HLK and the upcoming release in October will be referenced as Refresh HLK.

How can I tell what version of the HLK I have?

The distinction between RTM HLK and Refreshed HLK will be in the last digits of the HLK studio version, 10.1.26100.X

The RTM HLK Studio version is 10.1.26100.1
The Refresh HLK Studio version is 10.1.26100.X

The HLK Studio version information can be located by clicking ‘About’ in the upper right corner of studio

How do I install the Refreshed version of the HLK?

Visit the HLK download page: Windows Hardware Lab Kit | Microsoft Learn
Download the Refreshed HLK
Run HLKSetup.exe

Notes

Ensure your current HLK projects are finished before attempting to use the same system for the HLK Refresh.
The Refreshed HLK cannot be installed on a system that already has the RTM HLK, this goes for both Controller and Client. It is highly recommended to start with a clean install of the OS for both.

How can I tell if the Errata I use was fixed in the Refreshed HLK?

The list of Errata fixed is available below

What do I do if the Errata I use doesn’t appear to be fixed in the Refreshed HLK?

If the Errata is not on the fixed list the waiver can be used on both the RTM HLK as well as the Refreshed HLK

What do I do if the Errata I use is listed as fixed, but failures are still being seen in the test?

Triage the failure first, there have been cases where a test issue is fixed, and the failure is still present but its due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

How should I address a test that was passing on the RTM HLK but now failing on the refreshed HLK?

Triage the failure first, there have been cases where a test issue is fixed, and the failure is still present but its due to a driver issue that has the same failure message
Next Open a CSS case: Get support for Partner Center dashboard and HLK issues - Windows drivers | Microsoft Learn

Going forward, will Microsoft be updating the HLK regularly?

Yes, Microsoft is transitioning into this servicing model for the HLK, which maintains overall test quality and reduces dependency on errata.

How often are these refresh releases expected?

Current plan is to evaluate releasing a refreshed HLK each quarter.

Does this update apply to client and server?

Can results from an RTM test run and a Refreshed test run be merged and used for submission?

No, submission must be completed with either the RTM or Refreshed HLK.

Will the refreshed HLK continue to support merged packages for multiple-OS submissions?

Is the VHLK also going to be updated?

Errata Fixed in the October 24’ Refresh

ID	Title	Job/Task Failing
91345	[HLK Errata] AudioLogo (system) enforces channel count on default mode	System Audio - Audio Logo Test
127433	[Auto-triage] New binary with endpoint stabilization delay	Audio Codec - Lullaby Test - Certification - Desktop
161095	[HLK Errata]: Voice Clarity Driver Timestamp Test requires small mic spk stream drift	Voice Clarity HLK Test Driver Timestamp
163288	[HLK Errata] Validation of UVC MJPG Translation Opt-in always fails for UVC IR Camera	Camera Driver System Test - Validation of UVC MJPG Translation Opt-in
163289	[HLK Errata] Camera Driver Registration Test IMFSampleAllocator check fails on Platform DMFT	Camera Driver Registration, Metadata, and Dependency System
164528	[HLK Errata] DF - PNP tests failure with Failed to open the EDT device (device specific)	Multiple
164532	[HLK Errata] Driver Isolation DV failures for serial.sys accessing SERIALCOMM registry key.	DV - EnumerateEvents
164702	[HLK Errata] Driver Isolation DV failures for wudfrd.sys accessing SERIALCOMM registry key.	DV - EnumerateEvents
167195	[HLK Errata] Camera Driver Registration Test IMFSampleAllocator check fails on Platform DMFT	Camera Driver Registration, Metadata, and Dependency System
167196	[HLK Errata] [Camera Driver Controls System Test - Framerate Throttle - Verify Mode Switching] - Does not account for Step Sizes	Camera Driver Controls System Test - Framerate Throttle - Verify Mode Switching
167197	[HLK Errata] Sensor Camera Profiles - Photo Sequence with MEP Camera fails	Sensor Camera Driver Controls System Test - CAMERA_PROFILES - Photo Sequence
167453	[HLK Errata] Media Capture TestFrameExposureControlWithCapture uses wrong Table Entry	TestFrameExposureControlWithCapture
167494	[HLK Errata] Camera Driver Controls System Test - VFR - Verify correct Pin fails for MEP devices	Camera Driver Controls System Test - VFR - Verify correct Pin fails for MEP devices
167738	[HLK Errata] Camera Driver System Test - MediaCapture - TestInfraredTorchControlMetadata fails for filtered Legacy Profile	Camera Driver System Test - MediaCapture - TestInfraredTorchControlMetadata
167884	[HLK Errata] Camera Driver System Test - MediaCapture - ValidateExposureCompensationValues fails due to IR camera	Camera Driver System Test - MediaCapture - ValidateExposureCompensationValues
168217	Human Presence Proximity Test Failing on Non Human Presence based Proximity Sensors	Human Presence capable Proximity Sensor Enumeration Property Verification Test
168478	[HLK Errata] [NdisStudio] NDIS keyword validation tests are listed under incorrect feature, causing failures for devices not advertising NDIS	[NdisStudio] NdisPoll keyword validation [NdisStudio] NdisPoll keyword functional validation
168710	[HLK Errata] Display Capture Tests failing for Indirect Display devices	Display capture tests
170424	[HLK Errata] Camera Driver System Test - MediaCapture - Digital Window Metadata fails for combined IR RGB Sensor Group	Camera Driver System Test - MediaCapture - Digital Window Metadata
171184	[HLK Errata] [NdisStudio] OidRequestTest - OID_GEN_XMIT_OK and OID_GEN_RCV_OK Verification test fail when link speed is less than 1Gbps	[NdisStudio] OidRequestTest - OID_GEN_XMIT_OK and OID_GEN_RCV_OK Verification
173553	[HLK Errata] Camera Driver Hardware Privacy Manual Test fails due to Kill Switch behavior	Camera Driver Hardware Privacy Manual Test
173718	[HLK Errata] NDISTest 6.5 - [2 Machine] - PM_PowerStateTransition & PM_WolMagicPacket & PM_WolPattern test fail	NDISTest 6.5 - [2 Machine] - PM_PowerStateTransition NDISTest 6.5 - [2 Machine] - PM_WolMagicPacket NDISTest 6.5 - [2 Machine] - PM_WolPattern
173736	[HLK Errata] Camera Driver Controls System Test - VIDEOSTABILIZATION - Iterate through possible settings while Preview fails with MEP due to Pin re-mapping	Camera Driver Controls System Test - VIDEOSTABILIZATION - Iterate through possible settings while Preview
175039	[HLK Manual Errata]: NDIS test failed due to the certificate in HLK Studio is out of date	[NdisStudio] OidRequestTest - OID_GEN_VENDOR_DRIVER_VERSION Verification [NdisStudio] OidRequestTest - OID_GEN_VENDOR_ID Verification [NdisStudio] OidRequestTest - OID_GEN_XMIT_OK and OID_GEN_RCV_OK Verification [Network Adapter] Verification for network
177219	[HLK Errata] Camera Driver System Test - Mediacapture - TestEffectOptInCameraEnumeration does not check regkey value	Camera Driver System Test - Mediacapture - TestEffectOptInCameraEnumeration
177825	[ERRATUM] KS Topology Test Fails Custom Audio Modes	System Audio - KS Topology Test
179949	[HLK Errata] Camera Control Pin Verification Tests failing due to MEP Pin remapping	Sensor Camera Driver Controls System Test - * - Verify correct Pin
181916	[HLK Errata] Driver Isolation DV failures for snxpsamd.sys accessing SERIALCOMM registry key.	DV - EnumerateEvents
184662	[HLK Manual Errata]: A crash with exception code 0xC0000005 occurred when running InternalPanel - Common color profile problems test	InternalPanel - Common color profile problems
188557	AutoTriage: HLK USB Secure Camera Controller Dual BDF Test - Compat test failure.	USB Secure Camera Controller Dual BDF Test - Compat

ACTION REQUIRED: HDC API users may need to update code for accessing submission blobs by Aug 28th

Cymoki — Tue, 30 Jul 2024 18:21:18 GMT

On August 28th, 2024, Hardware Dev Center APIs will change the type of blob urls that are returned in various API calls from service sas urls to user delegated sas urls. Partners using HDC Hardware dashboard API to automate driver submission process may be affected. The specific area affected is the upload and downloads through the download links in the submission response. All other aspects of the submission process that can be accessed through the API are not affected. Partners are recommended to update to latest version of the libraries they use to upload and download from Azure Blobs during the driver submission process.

Partners using C# are encouraged to move to Azure.Storage.Blobs or Azure.Storage.Blobs.Specialized library to ensure that driver submissions are not interrupted. Any partner already managing blob interactions through these libraries is not affected by this change. The following is an example of the BlockBlobClient:

If you experience any issues, please open a support ticket with HDC support. For details about how to contact the support team, visit https://aka.ms/GetHardwareSupport .

Windows Hardware Compatibility Program - Guidance for Windows 11, version 24H2 Release

AndyW — Wed, 22 May 2024 19:48:50 GMT

To facilitate the release of Windows 11, version 24H2, and Windows Server 2025, the Windows Hardware Compatibility Program is set to accept submissions. The submission package must fulfill the prerequisites to guarantee compatibility between the operating system and the Hardware Lab Kit (HLK).

New Agreement - Please review and take action on the latest agreement update to avoid service interruption following the effective date of the new agreement.

Windows Hardware Compatibility Requirements – https://aka.ms/whcp

Submission Pre-requisites

OS and HLK minimum acceptable build:
- Windows 11, version 24H2 (Build 26100 or greater)
- Windows Server 2025 (Build 26100 or greater)

Playlist – https://aka.ms/hlkplaylist

The table below illustrates the required playlists for testing each processor architecture:

Target Architecture	Required Playlist(s)
Client (ARM64)¹	HLK Version 24H2 CompatPlaylist x64 ARM64.xml HLK Version 24H2 CompatPlaylist ARM64_x86_on_ARM64.xml HLK Version 24H2 CompatPlaylist ARM64_x64_on_ARM64.xml
Client (X64)	HLK Version 24H2 CompatPlaylist x64 ARM64.xml
Server (X64, ARM64)	HLK Version 24H2 CompatPlaylist x64 ARM64 SERVER.xml

¹For Client system-level x64 and ARM64 submission, the only playlist required is the HLK Version 24H2 CompatPlaylist x64 ARM64.xml

Please refer to the HLK Getting Started Guide for details on HLK client setup and playlist use.

Deferment of Partner Dev Center SBOM Validation

The WHCP requirement, for partner SBOM submissions alongside driver packages submitted to HDC, will be deferred at HDC. Partners will be given notice as soon as there is a set enforcement date during a future release, along with guidance on how to meet any new requirements.
WHCP continues to support a secure supply chain throughout our signing process. That said, the EO on Cyber Security is a call to action from the U.S. Government, so we continue to encourage that our partners seek to enable a secure supply chain as stated in the NIST guidance.

Device.DevFund.StaticTools Requirement

The Device.DevFund.StaticTools requirement applies to Windows 11 Client x64 and Windows Server x64.
Helpful information about how to use CodeQL and generate DVL files is available here - CodeQL and the Static Tools Logo Test - Windows drivers | Microsoft Learn

ACTION REQUIRED: New Agreement governing access to Hardware Dev Center

AndyW — Mon, 13 May 2024 17:07:36 GMT

We have updated the agreements on Partner Center for the Windows Hardware Program. We made these updates to clarify our terms and ensure that they are transparent, as well as to address usage of new logos.

All participants in the Hardware Program are required to have their authorized personnel review, acknowledge, and accept the agreements. New submissions will be blocked after August 14, 2024 until the agreements are accepted.

Partners who have accepted prior versions of the agreement via other means will still need to accept the agreement on Partner Center. For partners who have already been a part of the program, you will see the previous agreement, the Windows Logo License Agreement from 2021, has been renamed and is now listed in the Agreements section of Partner Center as "Microsoft Marks License Agreement (formerly Windows Logo License Agreement)" with the value in the Agreement column of Version 2021.

As a result, partners who previously accepted the Windows Logo License Agreement will see two entries in the Agreements section:

The new Microsoft Marks License Agreement, with Version 2024.
The previous Windows Logo License Agreement, now renamed to "Microsoft Marks License Agreement (formerly Windows Logo License Agreement)" with the value in the Agreement column of Version 2021.

Going forward, the four agreements listed below will govern your access to the Hardware Program. Legacy agreements will be deprecated.

· Code Signing Agreement

· Windows Hardware Compatibility Agreement

· Microsoft Marks License Agreement 2024 (New)

· Windows Analytics Agreement v2.0

If you encounter issues accessing the new agreements, please reach out to our support team. For details on how to contact support, see Get support for Partner Center dashboard issues - Windows drivers | Microsoft Learn.

Windows Hardware Compatibility Program Guidance for Windows 11, version 23H2

AndyW — Wed, 27 Sep 2023 16:12:49 GMT

Microsoft is pleased to announce the release preview of Windows 11, version 23H2 annual feature update, which shares the same servicing branch and code base as Windows 11, version 22H2, and will be delivered via an enablement package (eKB). See Windows 11 Release information for more information on the annual feature update cadence.

In support of the annual feature update, the Windows Hardware Compatibility Program (WHCP) will also release a Hardware Lab Kit (HLK) update to complement the feature updates within the Windows release. There is no plan to update the certification status issued by the HLK: the certification status that was used for the HLK for Windows 11, version 22H2, which is “Certified for Microsoft Windows 11 Client family version 22H2”, will continue to be used for this this HLK release for the Windows 11, version 23H2 update.

While there are no changes to WHCP or certification status, the updated HLK release with Windows 11, version 23H2 will be required when using Windows 11, version 23H2 to certify. Note, certifying for Windows 11, version 23H2 is optional.

Details

WHCP requirements – No change. Windows 11, version 22H2 requirements, remain the same for Windows 11, version 22H2 and the new 23H2.
Windows Hardware Lab Kit – For Submissions, HLK 22H2 to be used with Windows 11, version 22H2 and HLK 23H2 to be used with Windows 11, version 23H2
Driver signature – No change. Drivers that meet all the applicable Windows 11, version 22H2 requirements will be digitally signed with the same signature attributes.
WHCP qualification – No change. Qualification will be shown as Windows 11, version 22H2
Required OS version – Windows 11, version 22H2 or Windows 11, version 23H2.
WHCP Playlists – Please using the version matching HLK and playlist for the OS version

Windows 11, version 22H2 – HLK 22H2 and Playlist 22H2
Windows 11, version 23H2 – HLK 23H2 and Playlist 23H2
Differences is a total of 9 tests added to the “HLK Version 23H2 CompatPlaylist x64 ARM64.xml” playlist.

Windows HLK playlist – New HLK playlists will be available on the date of Windows 11, version 23H2 release, and can be found here.
Technology areas in HLK that took bug fixes:

Audio APO
Audio - Silicon and Pipeline
Bluetooth
Encoders

ACTION REQUIRED: New Agreements governing access to HDC

AndyW — Fri, 17 Feb 2023 17:28:19 GMT

As a reminder of the comm published on Jan 25, 2023, two new agreements are available on Partner Center for the Windows Hardware Compatibility Program. To avoid service disruption, please prioritize to review and decide the required agreements before they become effective on Feb 28, 2023

We recently added new agreements to Partner Center for the Windows Hardware Program. We made these updates to clarify our terms and ensure that they are transparent, as well as to cover new government mandates. All participants in the Hardware Program are required to have their authorized personnel review, acknowledge, and accept the agreements. New submissions will be blocked after February 28, 2023 until the agreements are accepted.

The four agreements listed below will govern your access to the Hardware Program. Legacy agreements will be deprecated.

Windows Server Catalog Changes to Support New Windows Server 2022 Network Additional Qualifications

Sandy_Arthur — Wed, 05 Mar 2025 00:29:49 GMT

Summary

On August 31^st Microsoft went live with an update to the Windows Server Catalog (www.windowservercatalog.com) that will ensure that customers who rely on the Windows Server logo will be able to identify components that will work best with Azure Stack HCI, using an updated set of Additional Qualifiers (AQ’s) that are now being displayed in the Catalog.

More information about the change is available at this blog link, https://aka.ms/RoleBasedNIC

Details

The Windows Server Catalog has some significant changes to the concept and “schema” of the Network Additional Qualifications for Windows Server 2022 (WS2022) network adapters (NICs), visible since the morning of Aug 31.

The change to the Windows Server Catalog was made to increase the “success rate” of Windows Server 2022 and Azure Stack HCI deployments, by ensuring that the NIC(s) used in a deployment are fully qualified for its role.

Now, for Windows Server 2022, the new Additional Qualification (AQ) schema is in place.

NICs can still be “just” Certified, but the majority of the listed network adapters should have at least one AQ. Many will have not just one, but two or even three new AQs for WS2022, as a NIC can have more than one of the new AQs. Example; the Management AQ, one of the Storage AQs, and one of the Compute AQs.

However, a NIC can only have one Storage AQ, either Standard or Premium, and the same for Compute, either Standard or Premium. In both cases, only the highest level AQ Storage or Compute is displayed in the Catalog Product entry page for any specific NIC.

Note: the WS2022 Storage and Compute AQs are “active” on the Server Catalog page left-hand pane in the sense that if either Standard or Premium is selected as a filter [click in the box to the left of the text], the other AQ option is removed from the left-hand pane until the first selection is cleared.

These new AQs are visible in the left-hand menu pane for Windows Server 2022 NICs. As well, the older AQs for SDDC, and the individual Additional Features (AFs) are visible for Windows Server 2019 and earlier submissions. Examples; IPSec support, or VMMQ support.

Here is a description of the Features needed for the Management AQ

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-management.htm.

There are two levels of Storage AQs, with the needed Features described here …

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-storage-standard.htm

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-storage-premium.htm

There are also two levels of Compute AQs, again with descriptive pages

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-compute-standard.htm

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-compute-premium.htm

These descriptive pages above can be accessed from the left-hand menu pane main page for NICs, by hovering the mouse over one of these AQs. Click the link in the in the box that then appears to get to the description. Clear the box by clicking the “X” in the upper right-hand corner of the box.

The old Network AQs [e.g., “Data Center Bridging”, or “SDDC Standard”] are still visible in the left-hand menu pane, but only apply to the WS2019 and earlier Windows Server operating system version submissions for any specific NIC. This way, end Customers can still filter using those older AQs and AFs for older OS version submissions. The same will be true for any new submissions made for older OS versions.

Finally, note that for the specific Product entry page, the older AQs for Networking do not appear under the text “Certified for Windows” for the WS2022 section of the entry, only the new AQs.

The older AQs and Additional Features (AFs) will continue to be visible for the WS2019 and earlier sections of the Product entry page.

Similar to the main NIC page, on any specific NIC Product entry page, the WS2022 AQs listed also have the same pop-up and “hover box”, w/ the same functionality. This way, no matter where in the Catalog the end Customer is searching for NICs, they will be able to get to the information about these AQs easily and quickly without hunting around in the FAQ pages.

There is a wide selection of Windows Server-certified NICs qualified for the Management, Storage and Compute AQs.

Supporting end Customers

This change is made to increase the “success rate” that Windows Server 2022 and Azure Stack HCI end Customers have when trying to design or build their own deployments. However, the recommended path for an end Customer is to work with a vendor that can provide a fully Integrated System. See this link, https://azurestackhcisolutions.azure.microsoft.com/#/catalog for more information.

WHCP guidance for Windows 10, version 22H2

Naim_Mohammad — Tue, 02 Aug 2022 16:38:00 GMT

The Windows 10, version 22H2 release will not bring updates to the Windows Hardware Compatibility Program (WHCP) and will follow the same guidelines as Windows 10, version 2004. Below are the more details with respect to all WHCP-related activities:

WHCP requirements – No change. Windows 10, version 2004 requirements remain applicable for Windows 10, version 22H2.
Windows Hardware Lab Kit – No change. Since WHCP requirements will persist in Windows 10, version 22H2, the Windows Hardware Lab Kit (Windows HLK) will also remain the same. There will not be a new Windows HLK release for Windows 10, version 22H2 and partners can continue using Windows 10, version 2004 HLK for certification.
Errata – No change. All Windows 10, version 2004 errata will continue to be valid for Windows 10, version 22H2.
Windows HLK playlist – No change. The Windows HLK version 2004 playlist can be used for Windows 10, version 22H2.
Driver signature – No change. Drivers that meet all the applicable Windows 10, version 2004 requirements will be digitally signed with the same signature attributes.
Submission – No change. Windows 10, version 2004, version 20H2, version 21H1, version 21H2 and version 22H2 can be used for WHCP submission.
WHCP qualification – Windows 10, version 2004
Required OS version – Windows 10, version 22H2
HLK version – HLK version 2004

Windows Hardware Compatibility Program for Windows 11, version 22H2

Naim_Mohammad — Fri, 12 Aug 2022 19:49:24 GMT

The updated version of the Requirements, Windows Hardware Lab Kit (HLK), along with updated playlists for testing Windows 11, version 22H2 hardware can be downloaded from below links. Compared to previous releases of the HLK, this version is intended for exclusive testing for Windows 11, version 22H2. Previous version of the HLK remain available at HLK Kits.

**Please note that Partner Center (Hardware Dev Center) will only start accepting submissions from 5/31/2022 onwards. Partners can download requirements and start hardware validation with updated kit now, but submissions can only be done starting 5/31/2022.

Windows 11, version 22H2 WHCP Requirements

WHCP requirements for Windows 11, version 22H2 can be found here - WHCP Specifications and Policies

Windows 11, version 22H2 certification build

Minimum acceptable build for Windows 11, version 22H2 certification is RTM build(i.e. 22621).

Windows 11, version 22H2 WHCP Playlists & Hardware Lab Kit

Windows Hardware Lab Kit can be found here - Windows Hardware Lab Kit

The table below illustrates the playlists needed for testing each architecture: Link - HLKPlaylist

Testing Target Architecture

Applicable Playlist(s)

x64

HLK Version 22H2 CompatPlaylist x64 ARM64.xml

ARM64*

HLK Version 22H2 CompatPlaylist x64 ARM64.xml

HLK Version 22H2 CompatPlaylist ARM64_x86_on_ARM64.xml

HLK Version 22H2 CompatPlaylist ARM64_x64_on_ARM64.xml

Please refer to the HLK Getting Started Guide for details on HLK client setup and playlist use.

Windows 11, version 22H2 – Submissions on Hardware Dev Center

Partner Center will start accepting submissions for Windows 11, version 22H2 starting 5/31/2022. When making WHCP submissions for the Windows 11, version 22H2 certification, use the following target in Partner Center:

Submission Target

Windows 11 Client x64, version 22H2 Full

Windows 11 Client ARM64, version 22H2 Full

Windows 11, version 22H2 based systems may ship with drivers that have achieved compatibility with Windows 11, version 21H2 until Oct 31st, 2022.
Partners looking to achieve compatibility for systems shipping with Windows 11, version 22H2 Release may use drivers for components that achieved compatibility with Windows 11, Version 21H2 until Oct 31st, 2022.

Errata 103871 is available to filter the “System Logo Check” failure seen when testing Windows 11, version 22H2 based systems with Windows 11, Version 21H2 qualified drivers. To apply, download the Latest Errata Filter Package.

Windows Hardware Compatibility Program guidance for Windows 10, version 21H2

Naim_Mohammad — Thu, 16 Sep 2021 20:24:43 GMT

When Windows 10, version 21H2 is released later this year, there will be no updates to the Windows Hardware Compatibility Program (WHCP). The program will utilize the same guidelines as Windows 10, version 2004, which include the following activities:

WHCP requirements – No change. Windows 10, version 2004 requirements remain applicable for Windows 10, version 21H2.
Windows Hardware Lab Kit (Windows HLK) – No change. Since WHCP requirements persist in Windows 10, version 21H2, the Windows HLK also remains the same. There will not be a new Windows HLK release for Windows 10, version 21H2. Both Windows 10, versions 2004 and 21H2 can be used for the Windows 10, version 2004 qualification.
Errata – No change. All Windows 10, version 2004 waivers will continue to be valid for Windows 10, versions 20H2, 21H1, and 21H2.
Windows HLK playlist – No change. The Windows HLK for Windows 10, version 2004 playlist can be used for Windows 10, versions 2004, 20H2, 21H1, and 21H2.
Driver signature – No change. Drivers that meet all the applicable Windows 10, version 2004 requirements will be digitally signed with the same signature attributes.
Submission – No change. Windows 10, versions 2004, 20H2, 21H1 21H2 can be used for WHCP submission.

WHCP qualification – Windows 10, version 2004
Required OS version – Windows 10, version 2004, version 20H2, version 21H1, and version 21H2
HLK version – Windows HLK for Windows 10, version 2004

For more information on the Windows Hardware Compatibility Program, visit https://aka.ms/WHCP.