WHLK USB Selective Suspend Test 25H2 24H2 are FAILED

Hi @志遠 郭 ,

Thanks for reaching out!

From my understanding, the USB Selective Suspend Test checks whether your device and driver correctly handle USB power management states, especially entering and exiting selective suspend. Failures on 24H2/25H2 usually happen because of environment setup or missing updates rather than OS bugs.

I would recommend you try out these simple workarounds first:

1. Use the correct HLK playlist for 25H2

The latest HLK builds and playlists are required for these OS versions. You can check for details here: WHCP guidance for Windows 11, version 25H2.

2. Apply HLK filters after importing the newest CAB

Filters don’t apply automatically to existing results. After importing, click Apply Filters in HLK Studio: Windows HLK Filters.

3. Check SuperMUTT firmware revision

Make sure your SuperMUTT device reports REV ≥ 0044. If it’s older, update using CMuttUtil/MuttUtil from the MUTT package: MuttUtil tool.

4. Confirm xHCI compliance even with USB4 setups

If your system uses USB4, ensure the DUT still enumerates through an xHCI root port at SuperSpeed, as HLK tests validate against xHCI requirements: HLK Tests for USB.

In your previous post, since you've already checked HLK version, USB setup, and SuperMUTT configuration so let’s make sure the remaining prerequisites for 24H2/25H2 are covered.

Most issues at this stage come down to playlist alignment, filters, or firmware not OS bugs so verifying these details usually gets you to green.

I hope this helps! If you have any question, please comment below. I'll be happy to help!

The WHLK USB Selective Suspend Test failures for versions 25H2 and 24H2 may indicate that the USB devices connected to the system are not properly entering a low power state, which is necessary for the system to utilize selective suspend effectively. Here are some steps to troubleshoot the issue:

1. Check Device Compatibility: Ensure that the USB devices support selective suspend. Devices that do not support this feature can cause the test to fail.
2. Review Sleep Study Reports: Use a Sleep Study report to identify any USB devices that remain active during standby. This can help pinpoint which device is preventing the USB host controller from entering a low power state.
3. ETL Trace Analysis: If necessary, perform an ETL trace to identify which USB device is staying in an active state (D0) during standby. This can provide insights into why the selective suspend is failing.
4. Driver Updates: Ensure that the drivers for the USB devices are up to date. Outdated drivers can lead to compatibility issues with power management features.
5. Firmware Updates: Check if the firmware for the USB devices is up to date, as this can also affect their ability to enter selective suspend.
6. Report Issues: If you identify a specific device that is not entering selective suspend, report the issue to the hardware vendor or Microsoft if the device is managed by a Microsoft driver.

By following these steps, you can diagnose and potentially resolve the issues causing the WHLK USB Selective Suspend Test to fail.

References:

• USB Selective Suspend Test (XHCI)
• Exercise 4 - Identify Problems with USB Devices