Share via

HLK Studio shows “No targets in project” after successful Controller and Client setup (Windows Server 2019 + Windows 10)

Nitin Pardeshi 0 Reputation points
2026-03-30T07:12:53.35+00:00

Title: HLK Studio shows “No targets in project” after successful Controller and Client setup (Windows Server 2019 + Windows 10)


Summary

I am attempting to set up the Windows Hardware Lab Kit (HLK) environment following the official Microsoft documentation. The HLK Controller and Client installations complete successfully, and the client machine appears in HLK Studio. However, I am unable to see any targets when creating a project, and all views show:

“There are no selected targets in the project” “Selected machine pool does not contain any targets of this type”


Documentation Followed

I followed the official Microsoft guide: https://learn.microsoft.com/en-us/windows-hardware/test/hlk/getstarted/step-1-install-controller-and-studio-on-the-test-server


Environment Details

  • HLK Controller OS: Windows Server 2019 Version 1809 (OS Build 17763.8389)
  • HLK Client OS: Windows 10 Version 22H2 (OS Build 19045.6466) (for driver testing)

HLK Version: Windows HLK for Windows 10, version 22H2

Installation Type: Controller + Studio on same server

No pre-installed SQL Server or third-party software


Controller Installation Steps

Disabled Windows Firewall

Created a local user: HLKInstallUser and logged in with it

Disabled Internet Explorer Enhanced Security Configuration (IE ESC)

Verified system is clean (no existing software in Programs and Features)

Downloaded HLK (Windows 10 version 22H2)

Verified download contents:

HLKSetup.exe
Windows Kits folder

Granted full permissions to HLKInstallUser on the entire Windows Kits directory

Ran HLKSetup.exe as Administrator

Selected:

Install → Controller + Studio

Accepted firewall port opening

Accepted license agreement

Installation completed successfully (~10–15 minutes)

Rebooted server


Controller Validation

Verified services are running:

DTMService → Running

HLKsvc → Running

WttChangeScheduler → Running

WTTServer → Running

HLK Studio and HLK Manager launch successfully.


Client Installation Steps (Windows 10)

Created same user HLKInstallUser (same credentials as controller)

Mapped controller share:

\\<ControllerName>\HLKInstall\Windows Kits\

Navigated to:

\\<ControllerName>\Windows Kits\10\Hardware Lab Kit\Controller\WTTInstall\Client

Ran Setup.cmd as Administrator

Completed installation successfully

Verified installation in Programs and Features

Verified service:

HLKsvc → Running


HLK Studio Configuration

Opened HLK Studio as Administrator

Clicked Connect

Controller and datastore detected correctly

Navigated to Configuration → Machine Pools

Observed:

Client machine appears under Default Pool

  Status initially NotReady, then changed to Ready
  
     Heartbeat is visible and updating
     
     Created a new machine pool
     
     Moved client machine into the new pool
     
     Set client state to Ready
     

Issue

When creating a project and selecting the machine pool:

No targets are visible under:

Systems

  Device Manager
  
     Devices and Printers
     
        Software devices
        
        The UI displays:
        
        ```sql
        There are no selected targets in the project

Selected machine pool does not contain any targets of this type ```


Expected Behavior

The client machine and its devices should appear as selectable targets in the project.


Actual Behavior

No targets are detected in any view despite:

Client being visible

Machine being in Ready state

Heartbeat working correctly


Request for Assistance

Could you please help identify:

Why the HLK client machine is not exposing any targets?

Whether there is any missing configuration or step not covered in the documentation?

If additional components (filters, drivers, provisioning steps) are required before targets appear?


Additional Notes

Installation was performed strictly as per Microsoft documentation

No errors were shown during installation

Environment is clean and minimal


Any guidance or troubleshooting steps would be greatly appreciated.Title: HLK Studio shows “No targets in project” after successful Controller and Client setup (Windows Server 2019 + Windows 10)


Summary

I am attempting to set up the Windows Hardware Lab Kit (HLK) environment following the official Microsoft documentation. The HLK Controller and Client installations complete successfully, and the client machine appears in HLK Studio. However, I am unable to see any targets when creating a project, and all views show:

“There are no selected targets in the project”
“Selected machine pool does not contain any targets of this type”


Documentation Followed

I followed the official Microsoft guide:
https://learn.microsoft.com/en-us/windows-hardware/test/hlk/getstarted/step-1-install-controller-and-studio-on-the-test-server


Environment Details

HLK Controller OS: Windows Server 2019

HLK Client OS: Windows 10 (for driver testing)

HLK Version: Windows HLK for Windows 10, version 22H2

Installation Type: Controller + Studio on same server

No pre-installed SQL Server or third-party software


Controller Installation Steps

Disabled Windows Firewall

Created a local user: HLKInstallUser and logged in with it

Disabled Internet Explorer Enhanced Security Configuration (IE ESC)

Verified system is clean (no existing software in Programs and Features)

Downloaded HLK (Windows 10 version 22H2)

Verified download contents:

HLKSetup.exe
Windows Kits folder

Granted full permissions to HLKInstallUser on the entire Windows Kits directory

Ran HLKSetup.exe as Administrator

Selected:

Install → Controller + Studio

Accepted firewall port opening

Accepted license agreement

Installation completed successfully (~10–15 minutes)

Rebooted server


Controller Validation

Verified services are running:

DTMService → Running

HLKsvc → Running

WttChangeScheduler → Running

WTTServer → Running

HLK Studio and HLK Manager launch successfully.


Client Installation Steps (Windows 10)

Created same user HLKInstallUser (same credentials as controller)

Mapped controller share:

\\<ControllerName>\HLKInstall\Windows Kits\

Navigated to:

\\<ControllerName>\Windows Kits\10\Hardware Lab Kit\Controller\WTTInstall\Client

Ran Setup.cmd as Administrator

Completed installation successfully

Verified installation in Programs and Features

Verified service:

HLKsvc → Running


HLK Studio Configuration

Opened HLK Studio as Administrator

Clicked Connect

Controller and datastore detected correctly

Navigated to Configuration → Machine Pools

  1. Observed:

Client machine appears under Default Pool

  • Status was NotReady.

Heartbeat is visible and updating

Created a new machine pool

Moved client machine into the new pool

  1. Set client state from NotReady to Ready.

Issue

When creating a project and selecting the machine pool:

No targets are visible under:

Systems

  Device Manager
  
     Devices and Printers
     
        Software devices
        
        The UI displays:
        
        ```sql
        There are no selected targets in the project

Selected machine pool does not contain any targets of this type ```


Expected Behavior

The client machine and its devices should appear as selectable targets in the project.


Actual Behavior

No targets are detected in any view despite:

Client being visible

Machine being in Ready state

Heartbeat working correctly


Request for Assistance

Could you please help identify:

Why the HLK client machine is not exposing any targets?

Whether there is any missing configuration or step not covered in the documentation?

If additional components (filters, drivers, provisioning steps) are required before targets appear?


Additional Notes

Installation was performed strictly as per Microsoft documentation

No errors were shown during installation

Environment is clean and minimal


Any guidance or troubleshooting steps would be greatly appreciated.

Windows development | Windows Driver Kit (WDK)

2 answers

Sort by: Most helpful
  1. Danny Nguyen (WICLOUD CORPORATION) 6,615 Reputation points Microsoft External Staff Moderator
    2026-03-30T09:06:34.27+00:00

    Hi @Nitin Pardeshi .

    This behavior typically indicates the client is connecting (heartbeat/Ready) but its device inventory (“targets”) isn’t being published to the controller, so the selected pool has no targets to add to the project.

    Can you try these few quick checks:

    1. Domain vs. workgroup authentication
    • If the environment is workgroup-based, using matching local accounts can sometimes allow the client to appear while other operations (like inventory/target publication) fail. If available, please try a domain-joined setup and run HLK using a domain account with admin rights on both machines.
    1. Firewall / required connectivity
    • Since the controller firewall was disabled, please also confirm the client firewall (and any network filtering) isn’t blocking HLK traffic. As a diagnostic step, temporarily disable the client firewall, toggle the client NotReady → Ready, and check whether targets populate.
    1. Client-side logs during “Ready” transition
    • On the client, please review Event Viewer (Application/System and any HLK/WTT/DTM/HLKsvc logs) for errors at the time the machine is set to Ready. Any RPC/WMI/permission/connectivity errors there are usually the key clue.
    1. Re-run client setup to force re-enumeration
    • On the client, re-run ...\Controller\WTTInstall\Client\Setup.cmd as Administrator, reboot, then set the machine to Ready again and re-check targets.
    1. Version alignment
    • Please confirm the HLK release matches the client OS (e.g., Windows 10 HLK 22H2 with a Windows 10 22H2 client; for Windows 11 clients, use the Windows 11 HLK).

    As a final note, could you confirm whether the controller and client are domain-joined or in a workgroup, and share any relevant client Event Viewer errors from around the time the machine is set to Ready?

    Hope to hear from you soon.

    If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback. Thank you.


  2. Q&A Assist
    2026-03-30T07:13:17.5533333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The behavior matches a known HLK condition where the client is connected and sending heartbeats, but no usable targets appear in a project because the gatherer data on the controller is missing or stale.

    Two specific HLK client issues from the documentation map to this:

    1. Client entry recreated but no targets in pool
      If the controller’s database entry for the client was deleted or became inconsistent, the client will reconnect (heartbeat works, shows as Ready in a pool), but no targets are listed when selecting that pool in a project. The documented symptom is:

    After the client entry appears, the client is visible in the Configuration screen in Windows HLK Studio; however, when you select the machine pool on the Selection tab, no targets are listed for the system.

    The documented resolution is to force the gatherer to return fresh data:

    1. On the HLK client machine, perform one of the following to trigger new gatherer data:
      • Install or update a driver or hardware device, or
      • Restart the client system.
    2. Wait for the client to reconnect and for HLK to rescan the system.
    3. In HLK Studio, re-open the project and reselect the machine pool; targets should now appear.
    4. Inaccurate or missing client information in Studio
      HLK can show incomplete or missing targets/tests if gatherer data is not current. The documented workaround is more thorough and often resolves “no targets in project” when the client is otherwise healthy:
    5. Restart the Windows HLK Client computer.
    6. (Optional) Delete the existing project in Windows HLK Studio.
    7. (Optional) In Windows HLK Manager Job Monitor, reset the status of the client computer.
    8. Close all instances of Windows HLK Studio and Windows HLK Manager.
    9. Restart Windows HLK Studio.
    10. Create a new project and add the HLK client computer to a machine pool, then select that pool for the project.

    If the client was installed incorrectly, another documented symptom is the LLU error “Skipped as Public key is null for the machine.” In that case, the fix is to uninstall and reinstall the HLK Client. Since the question states that the client appears, is Ready, and heartbeats are visible, the primary suspect is stale/missing gatherer data rather than a completely failed client install.

    In summary, to expose targets in the project with the current setup:

    1. Restart the HLK client machine (or cause a hardware/driver change) to force new gatherer data.
    2. Close Studio/Manager, then reopen Studio.
    3. Create a new project, add the client to a pool, and select that pool.
    4. If targets still do not appear, reset the client status in Job Monitor and repeat, and only then consider uninstalling/reinstalling the HLK Client.

    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.