HLK Test Failures on Windows 11 25H2 (Passed on 24H2 with Same Driver)

Windows HLK tests and content are versioned and updated per OS release, and issues like the ones described must be investigated using the standard HLK troubleshooting flow rather than assumed to be platform regressions.

Based on the available information, the following actions are recommended:

1. Confirm correct HLK kit and content for 25H2
   • Ensure that the HLK kit in use is the Windows 11, version 25H2 kit (or VHLK) from the current download table, not a down-level kit. For 25H2, use the “Windows HLK (Updated February 2026) for Windows 11, version 25H2” or the corresponding VHLK image.
   • Verify that the test content is fully up to date and that all applicable filters are installed. HLK filters and content updates often address newly discovered test issues and misalignments with the OS.
   • To do this, follow step 1 in the HLK troubleshooting guide and install the latest updates and filters from the Windows Hardware Lab Kit Filters page.
2. Verify that tests are being run correctly on 25H2
   • Some HLK tests (including networking/WFP-related ones) require special configuration or supplemental content that is not included in the base HLK package.
   • In HLK Studio, check whether the failing tests show the toolbox icon in the Type column. If so, open the test reference (select the test and press F1) and verify that all special configuration requirements are met on the 25H2 client.
   • If any of the failing tests require user interaction (person icon), confirm that the manual steps are being followed exactly as documented in the test reference.
   • If the tests were scheduled as multi-device runs, rerun the failing tests individually against a single 25H2 target. Multi-device runs can complicate analysis and sometimes mask per-target issues.
3. Re-check HLK environment and configuration changes
   • Confirm that the HLK infrastructure and the 25H2 test client configuration have not changed after selecting the test targets. If configuration (networking, drivers, roles, etc.) changed after target selection, re-select the test target so HLK can refresh system configuration.
   • Be aware that re-selecting the test target invalidates and removes previous test results, so archive any logs needed before doing this.
   • If status icons show tests stuck in Queued or other infrastructure-related states, review the HLK environment using the guidance in the HLK troubleshooting article and the environment troubleshooting topic.
4. Use HLK logs and task error messages to isolate the failures
   • For each failing test, open the HLK Studio test log and task logs and look for specific task error messages.
   • Use the “Windows HLK Studio task error message reference” to interpret common messages such as:
     • “Task <> is Marked as Failed from the Log File” → inspect the task log for the exact failure condition.
     • “Failed to determine Pass/Fail of the task <> Task will be marked as failed anyway.” → indicates incomplete or comment-only logs; check for missing configuration or prerequisites.
     • “Cause : The Execute Task with <> Failed with ExitCode <Error Code>” → map the exit code to Win32 or HRESULT to understand whether the failure is environmental, configuration-related, or due to driver behavior.
     • “Task cancelled because of an unexpected reboot” → investigate system crashes or reboots on the 25H2 client.
   • For WFP-related tests, also review any system crash information if the status icon indicates “Failed due to system crash,” and use the bugcheck information exposed by HLK Studio.
5. Treat 24H2 vs 25H2 differences as expected until ruled out
   • The fact that the same driver and configuration passed on 24H2 does not guarantee identical behavior on 25H2. HLK content and OS networking/WFP behavior can evolve between releases.
   • Use the HLK test reference (F1 from the failing test in HLK Studio) to confirm whether any requirements or expectations changed for 25H2 (for example, stricter architectural checks or firewall rule validation).
6. If issues persist after the above steps
   • After confirming:
     • Correct 25H2 HLK kit and latest filters are installed,
     • All special configuration/manual requirements are satisfied,
     • Tests are run individually on a clean, correctly configured 25H2 target,
     • Logs and task error messages have been reviewed and do not point to a clear configuration or driver issue,
   • Then follow step 6 of the HLK troubleshooting guide and contact Windows HLK Support with:
     • The exact HLK kit version and OS build,
     • The specific failing test names,
     • Collected HLK logs and any crash/bugcheck data.
   • HLK Support can confirm whether there are known issues with specific tests on 25H2 or with the particular HLK build against the 26200.x OS build, and provide filters or workarounds if applicable.

This process will determine whether the failures are due to HLK test issues, configuration/environment problems on the 25H2 client, or genuine behavioral changes that require driver or configuration adjustments.

References:

• Troubleshooting Windows Filtering Platform (WFP) Driver Testing
• Troubleshooting Windows HLK Test Failures
• Windows Hardware Lab Kit