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
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
Comments (1)
-
unity_8B16398C0FD0537D9EA7
Aug 20, 2025 12:34
This is not working
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 6000.5.0a1):
The issue has been resolved in Unity Hub 3.15.0
Resolution Note (fix version 6000.4.0a1):
The issue has been resolved in Unity Hub 3.15.0
Resolution Note (fix version 6000.3.0a1):
The issue has been resolved in Unity Hub 3.15.0
Resolution Note (fix version 6000.2.0a1):
The issue has been resolved in Unity Hub 3.15.0
Resolution Note (fix version 6000.0.0b1):
The issue has been resolved in Unity Hub 3.15.0