Search Issue Tracker

Fixed

Fixed in 6000.0.0b1, 6000.2.0a1, 6000.3.0a1, 6000.4.0a1, 6000.5.0a1

Votes

12

Found in

6000.0.47f1

6000.1.0f1

6000.2.0a9

6000.3.0a1

6000.4.0a1

6000.5.0a1

Issue ID

UUM-103995

Regression

No

Licensing Client fails to launch when opening Unity Hub

Hub

-

Reproduction steps:
1. Open the Unity Hub
2. Observe the Unity Hub

Expected result: Unity Hub opens
Actual result: Unity Hub fails to open

Reproducible with: 1.17.0

Reproducible on: Windows 10 (by the user), Windows 11(24H2) (by the user)

Notes:

-Not reproducible by CQA
-For this exact scenario the following error lines should be present: {{Process exited with code null}}, {{Failed to launch licensing client: Error: Timeout}}, {{Failed to start Unity Hub, reason: LICENSING_CLIENT_CONNECTION_ERROR: Failed to establish a connection with the Licensing Client}}
-A potential workaround involves performing a clean reinstallation of Unity Hub by first backing up the editors-v2.json file. Then, delete all files located in Users/[username]/Library/Application Support/UnityHub (for macOS users) or C:\Users\[username]\AppData\Roaming\UnityHub (for Windows users). Afterward, reinstall Unity Hub and restore the editors-v2.json file to its original location

  1. Resolution Note (fix version 6000.5.0a1):

    The issue has been resolved in Unity Hub 3.15.0

  2. Resolution Note (fix version 6000.4.0a1):

    The issue has been resolved in Unity Hub 3.15.0

  3. Resolution Note (fix version 6000.3.0a1):

    The issue has been resolved in Unity Hub 3.15.0

  4. Resolution Note (fix version 6000.2.0a1):

    The issue has been resolved in Unity Hub 3.15.0

  5. Resolution Note (fix version 6000.0.0b1):

    The issue has been resolved in Unity Hub 3.15.0

Comments (1)

  1. unity_8B16398C0FD0537D9EA7

    Aug 20, 2025 12:34

    This is not working

Add comment

Log in to post comment