Share via

Issues preparing a new HLK test environment (Client stays Not Ready)

dongdong Hao 20 Reputation points
2025-12-11T04:10:59.5666667+00:00

Hi, I am setting up a new HLK (Hardware Lab Kit) test environment and have run into several issues during the preparation of the Controller, Studio, and Client machines. I would appreciate some guidance on whether I might have missed any configuration steps.

Here is a summary of the situation:

Environment

  • HLK Controller + Studio OS: [Windows Server 2025 Datacenter Version 24H2 OS Build 26100.7462 + HLK version: 10.1.26100.6584]
  • HLK Client OS: [Windows Server 2025 Datacenter Version 24H2 OS Build 26100.7462]

Network mode: Workgroup

  • Connection: Same subnet, no domain, connected directly by a tp-link router
  • HLK Client installed from: \\HLKController\HLKInstall\Client\Setup.cmd ICFAGREE=Yes

Symptoms

  • HLK Studio displays the client under Machines, but the status is always Not Ready.
  • The HLK Client never changes to the “Ready” state in HLK Studio. It appears online, but HLK Studio still reports it as “Not Ready”. The Client installation itself completed without visible errors.
  1. What I have already verified
    • The HLK Server components (Controller/Studio) are installed successfully.
    • SQL Server is installed and working correctly for the HLK database.
    • Required Windows services such as WinRM and Remote Registry are enabled on the Client.
    • The HLK Communication Service is running on the Controller.
    • Firewall settings have been checked to allow required HLK communication.
    • Connectivity
    • ping from Controller → Client: OK
    • WinRM connection to client: OK
    • File share access to \\HLKController\HLKInstall\...: OK
    Services on the client 
        HLKsvc – Running

RemoteRegistry – Running WinRM – Running ```

1. **Installation**

   HLK Client installed successfully with no visible errors.
   
      Correct HLK version matching the Controller.
      
         No antivirus or firewall blocking ports (tested with firewall temporarily disabled).
  1. Language / Region
    • System language is English (en-US).
    • But HLK Studio unexpectedly shows WTT\LanguagePack = Arabic.
    • Not sure if this mismatch affects readiness.
  2. Additional observations
    • Language settings on the Client appear inconsistent in HLK Studio.
    • The HLK installation folder on the Client does not contain some expected tools.
    • Some HLK Client status information does not match the system’s actual configuration.
  3. What I would like to confirm
    • Are there any known issues or extra steps when using Windows Server 2025 as an HLK Client?
    • Are there specific language-pack requirements for HLK Client recognition?
    • Are there additional services or configurations required beyond the standard HLK documentation?
    • Is there a recommended checklist to validate HLK Client readiness?

Any suggestions or guidance would be greatly appreciated. Thanks in advance!

Windows development | Windows Driver Kit (WDK)
0 comments
Answer accepted by question author
  1. Jack Dang (WICLOUD CORPORATION) 5,960 Reputation points Microsoft External Staff Moderator
    2025-12-11T10:32:37.36+00:00

    Hi @dongdong Hao ,

    Thanks for reaching out.

    I see that you’ve already verified services, network connectivity, and firewall settings, which is great - the following points focus on additional factors that can affect HLK Client readiness.

    Based on your description, the HLK Client showing as “Not Ready” despite installing successfully can be caused by a few factors:

    1. Language Pack / Regional Mismatch HLK relies on the WTT language pack to recognize Clients. Even if your OS is English, HLK Studio may report a different language if the corresponding WTT language pack is missing. Ensuring the correct language pack is installed on the Client can resolve readiness issues.
    2. Windows Server 2025 Compatibility The HLK version you are using (10.1.26100.6584) may not fully support Windows Server 2025. Some checks may fail silently if the OS build is newer than expected. Verify the HLK release notes to confirm support for your OS version.
    3. Incomplete HLK Client Tools Missing tools in the HLK Client installation folder can prevent the Client from reaching “Ready.” Consider reinstalling the Client and ensuring all expected tools are present.
    4. Workgroup Configuration HLK environments are typically validated in domain setups. In a workgroup, extra configuration may be needed for authentication and service communication. Double-check credentials and permissions between the Controller and Client.

    Suggested Checklist:

    • Verify the WTT language pack matches your OS language.
    • Ensure all HLK Client tools are installed.
    • Confirm Windows Server 2025 is supported by your HLK version.
    • Restart HLK services and reboot the Client after installation.
    • Review firewall and network settings once more, even if initially tested.

    If the Client still shows “Not Ready” after these steps, consider reinstalling the Client or reviewing the HLK release notes for any OS-specific guidance.

    Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.