To prevent this, run the following command from an elevated command prompt on each Windows HLK Client computer: powercfg /setacvalueindex scheme_current sub_video videoidle 0 & Powercfg /setdcvalueindex scheme_current sub_video videoidle 0 & Powercfg /s scheme_currentĬlient computer is locked by an LLU account Client computer goes to sleep during a testĪn always on, always connected (AOAC) computer that is not an Arm machine can go to sleep during a test. Go to the Configuration menu and put the computer in a ready state. If you select a target but cannot select any of the tests, the computer is not in a ready state. Reinstall the Client using the steps in Remove and reinstall the Windows HLK Client.Ĭannot select tests after previous test failsĪfter a test fails, the checkboxes for the list of tests are dimmed and you cannot select additional tests.
Try the solutions in Client computers cannot communicate with the Windows HLK Controller. Try these solutions in the following order:
This problem can be caused by a lack of communication between the Windows HLK Controller computer and the Windows HLK Client computer, or by a trusted key mismatch between the two systems.
The Client does not change from the Debug state to the Ready state, even after changing the state to Reset in Windows HLK Manager. Cannot get a client computer out of Debug state This topic describes how to troubleshoot issues with the Windows Hardware Lab Kit (Windows HLK) Client.įor help with problems that occur during Windows HLK Client setup, see Troubleshooting Windows HLK Setup.
0 kommentar(er)
