Hello,
This could have happened for a number of reasons, was this Client used previously for another project on the same controller? How was the Client installed?
I would try
- Setting the Client into Not Ready state in the HLK Studio
- Move it to Default pool
- Delete the Client from the Default pool
- Restart the Client machine
If the system showed up again in the Default pool in HLK Studio then you should be good to go, if it did not, it has something to do with the way the HLK Client was installed, and i recommend reinstalling the Client following the steps highlighted in the HLK Getting Started guide
https://learn.microsoft.com/en-us/windows-hardware/test/hlk/
Also, you can take a look at the following troubleshooting doc that will go through a number of scenarios and their proposed resolution:
https://learn.microsoft.com/en-us/windows-hardware/test/hlk/user/troubleshooting-windows-hlk-client#jobs-do-not-run-after-reinstalling-the-windows-hlk-client
Thanks
Fidaab