AzureFeeds

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

Playlist updates: 

Removed 3 camera tests:

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

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?




1. 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 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?




• 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