Share via

HLK Client Service Not Running on Windows Server 2025 (Controller, Studio, and Client on Same Machine)

Akhil G Nair 20 Reputation points
2026-01-08T02:42:15.5066667+00:00

For testing NVMe Persistent Reservation, we have installed Windows Hardware Lab Kit (HLK) Controller, Studio, and Client on the same system running Windows Server 2025. The installation completed successfully.

However, when attempting to connect the local system as a client using HLK Studio, the connection fails because the HLK Client service is not running on the system.

Upon verification:

  • HLK Controller and Studio services are installed

HLK Studio is unable to detect or connect to the local HLK Client

The HLK Client service is either missing or not starting

Environment:

OS: Windows Server 2025

HLK Components: Controller, Studio, Client (same machine)

Test Scenario: NVMe Persistent Reservation testing

Request: We would like guidance on:

Whether installing HLK Controller, Studio, and Client on the same Windows Server 2025 system is a supported configuration

Required prerequisites or configuration steps to ensure the HLK Client service is installed and running

Any known limitations or additional requirements (disk space, services, permissions) specific to Windows Server 2025

Please advise on the correct setup and troubleshooting steps to resolve this issue.For testing NVMe Persistent Reservation, we have installed Windows Hardware Lab Kit (HLK) Controller, Studio, and Client on the same system running Windows Server 2025. The installation completed successfully.

However, when attempting to connect the local system as a client using HLK Studio, the connection fails because the HLK Client service is not running on the system.

Upon verification:

HLK Controller and Studio services are installed

HLK Studio is unable to detect or connect to the local HLK Client

The HLK Client service is either missing or not starting

Environment:

OS: Windows Server 2025

HLK Components: Controller, Studio, Client (same machine)

Test Scenario: NVMe Persistent Reservation testing

Request:
We would like guidance on:

Whether installing HLK Controller, Studio, and Client on the same Windows Server 2025 system is a supported configuration

Required prerequisites or configuration steps to ensure the HLK Client service is installed and running

Any known limitations or additional requirements (disk space, services, permissions) specific to Windows Server 2025

Please advise on the correct setup and troubleshooting steps to resolve this issue.

Windows for business | Windows Server | User experience | Other
0 comments

Answer accepted by question author

  1. Harry Phan 19,735 Reputation points Independent Advisor
    2026-01-08T12:15:48.4766667+00:00

    Hi Akhil,

    Running HLK Controller, Studio, and Client on the same Windows Server 2025 system is technically possible but not the recommended configuration for certification scenarios. Microsoft’s HLK documentation specifies that Controller and Studio can coexist, but the Client role is expected to be installed on a separate test machine. When all three are installed together, the HLK Client service often fails to register or start, which is why Studio cannot connect to the local system.

    The HLK Client service (HLKClientService) should appear in services.msc after installation. If it is missing, it means the Client role was not properly provisioned. Re‑running the HLK setup and explicitly selecting the Client role is required. On Server 2025, you must also ensure you are using the latest HLK build aligned with that OS release, as earlier HLK builds do not fully support Server 2025 and will not install the Client service correctly.

    Beyond installation, the HLK Client requires local administrator rights, WinRM enabled, and open TCP ports 17750–17751 for communication with Studio. Disk space should be at least 40 GB free, and prerequisites such as .NET Framework 4.8 and Visual C++ Redistributables must be present. If the service is installed but fails to start, check the Event Viewer for service startup errors and confirm that no conflicting HLK roles are blocking it.

    For NVMe Persistent Reservation testing, the supported and stable approach is to run Controller and Studio on one system and dedicate a separate machine for the Client role. This avoids service conflicts and ensures the tests can execute correctly. If you must run all roles on one server, reinstall HLK with the Client role explicitly selected, confirm the HLK Client service is present and running, and validate WinRM connectivity.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    Harry.

    Was this answer helpful?

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-01-08T02:42:29.35+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Installing the HLK Controller, Studio, and Client on the same system is generally supported, but there are specific prerequisites and configurations needed to ensure that the HLK Client service runs correctly. Here are some steps and considerations:

    1. Check Installation: Ensure that the HLK Client is properly installed. If the service is missing, you may need to reinstall the HLK Client.
    2. Service Status: Verify that the HLK Client service is set to start automatically. You can check this by:
      • Opening the Services management console (services.msc).
      • Locating the HLK Client service and ensuring its Startup Type is set to Automatic.
      • If the service is not running, try starting it manually and check for any error messages.
    3. Firewall and Network Settings: Ensure that any firewall settings allow communication between the HLK Controller and Client. This includes verifying that the necessary ports are open (e.g., port 1771 for the WLK Client).
    4. Permissions: Make sure that the user account running the HLK services has the necessary permissions to start and manage the services.
    5. Known Limitations: While specific limitations for Windows Server 2025 are not detailed in the provided context, it is advisable to ensure that the system meets any general requirements for disk space and system resources, as running multiple HLK components on a single machine can be resource-intensive.

    If you continue to experience issues, consider checking the event logs for any specific error messages related to the HLK Client service that might provide more insight into the problem.

    References:

    Was this answer helpful?

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.