Windows HLK: the 24H2 and 25H2 download links are identical

Question

Scenario

We are certifying a KMDF kernel-mode driver for Windows 11, version 24H2. The test machine runs Windows 11 24H2 and we use the 24H2 compatibility playlist.

To set up the controller we used the "24H2" entry on the VHLK download page. However, that entry does not have its own link:

• On https://www.microsoft.com/en-us/evalcenter/download-virtual-hardware-lab-kit, the 25H2 and 24H2 VHLK entries both use go.microsoft.com/fwlink/?linkid=2327200. Only 26H1 has a distinct link (linkid=2341303).
• On https://learn.microsoft.com/en-us/windows-hardware/test/hlk/, the rows for 25H2, Windows Server 2025 and 24H2 all point to the same HLK link (linkid=2364011), and every VHLK link points to linkid=2196169.

The kit we ended up with reports:

Component	Version
HLK Controller	10.1.26100.8328
HLK Studio	10.0.26100.8328

Other Q&A threads identify build 26100.8328 as the 25H2 kit, so the "24H2" link appears to serve the 25H2 image.

Result

The Static Tools Logo Test fails on the DVL version check:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: CodeQL DVL version 1.0.0.0 is below the minimum required version 1.2.0.0 for driver 'mydriver' with the OS architecture 'x64'. Please regenerate your DVL with a current WDK and rerun CodeQL analysis before running this test again. at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes) at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)

Our toolchain follows the WHCP_24H2 row of [Run CodeQL Analysis for Windows Driver Certification (https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/static-tools-and-codeql):

Component	Version
CodeQL CLI	2.15.4
microsoft/windows-drivers pack	1.1.0
codeql/cpp-queries pack	0.9.0
Query suite	suites/windows_driver_recommended.qls (branch WHCP_24H2)
WDK	10.0.26100.0 (dvl.exe 10.0.26100.4202)

The CodeQL analysis reports 0 must-fix defects, and the DVL produced by msbuild /t:dvl is version 1.0.0.0.

What we already checked

• The known issue in How to Create a Driver Verification Log applies to 25H2 and asks partners to use WDK 28000.1761 plus waiver #320241.
• The May 2026 refresh announcement states the refreshed kit "supports certifying drivers for Windows 11, version 25H2 and Windows Server 2025", which does not list Windows 11 24H2 as a client target.

Question

• Which kit should be used to certify a Windows 11, version 24H2 client driver, and where can it be downloaded, given that the 24H2 entries on both download pages resolve to the 25H2 kit?
• If 24H2 certification is expected to use the May 2026 kit, does the minimum DVL version 1.2.0.0 requirement also apply to 24H2 submissions, and if so, which WDK produces a DVL that satisfies it?

Tags: Windows Hardware Performance / Windows Hardware Lab Kit (HLK)

Answer 1

Hi Laurie!

Yes, kits for 25H2 and 24H2 are the same, but this is normal, the same happened for 23H2 and 22H2.

It should work for both versions.

I would use the latest WDK available if possible.

Have you tried to apply HLK filters to your results?

Hope this helps.

Answer 2

any comments?