AzureFeeds

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: 

Added tests: 

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

Removed tests: 

Added tests: 

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