Disable Secure Boot on the HLK client, reboot it, reselect the test target, and rerun TDI filters and LSPs are not allowed; this test explicitly requires Secure Boot to be disabled, and the matching CheckTDIFilterTest service-start failure was resolved that way.^1^^2^
Apply the required configuration
- On the HLK client, open the UEFI firmware settings:
- Hold Shift while selecting Restart.
- Select Troubleshoot > Advanced options > UEFI Firmware Settings.
- Locate Secure Boot, usually under Security, Boot, or Authentication, and set it to Disabled.
- Save the firmware changes and restart Windows. Firmware changes carry a boot risk, so change only Secure Boot and follow the system manufacturer’s instructions.^3^
- Confirm Windows booted with Secure Boot disabled.
- In HLK Studio, reselect the machine/device target so HLK refreshes the client configuration, then rerun the test.
Reselecting a target invalidates and removes its previous results. Preserve the current project/package first if those results are needed.^4^
This requirement is specific to the test. Other certification tests—particularly Secure Boot tests—can require Secure Boot to be enabled, so restore the appropriate firmware configuration before running that test group. Microsoft’s system-testing sequence explicitly includes TDI filters and LSPs are not allowed among the tests run with Secure Boot protections disabled.^5^
If chktdif still cannot start
Because the playlists and filters have already been updated and applied, do not repeat that step unless Microsoft publishes a newer erratum. Instead:
- In HLK Studio > Results, right-click the failed result.
- Open Task Error, Task Log, and Additional Files.
- Record the complete
StartServicemessage and its numeric Windows error code. - On the client, open Event Viewer:
- Check Windows Logs > System for driver/service-load failures.
- Check Windows Logs > Application for a test executable failure.
- If this was a multi-device run, use Run Tests Individually and rerun only this target; combined logs can obscure which device produced the failure.^4^
- Review the applicable WDTF prerequisites, including the LAN requirement that the client have an IPv6 address, an IPv6 default gateway, and an operational network adapter.^6^
The available test guidance does not identify a chktdif limitation specific to build 26100.8328. A separate report for that build concerns tests not queuing, which is a different symptom from this service-start failure.
Escalation package
If the failure remains after Secure Boot is disabled, submit a separate HLK support issue for this test and include:
- Exact test name as shown in HLK Studio.
- The complete
.hlkxpackage. - Task Error, Task Log, execution logs, and Additional Files.
- Relevant System and Application event logs from the failed run.
- Any user-mode dump if the test process crashed.
- A kernel dump—not only a minidump—if the system crashed.
- HLK version, client OS/build, applied playlist/filter dates, exact
StartServiceerror code, and confirmation that Secure Boot was disabled during the run.
These are Microsoft’s required artifacts for investigating an HLK test issue.^7^
References