Search Issue Tracker
Fixed
Fixed in 6000.0.0b1, 6000.2.0a1, 6000.3.0a1, 6000.4.0a1, 6000.5.0a1
Votes
3
Found in
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-103996
Regression
No
Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
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: {{{}Failed to launch licensing client: licensing client path is not found:{}}}, {{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
----
The next release of Hub 3.15 contains a fix to mitigate this error, once the 3.15 GA is released publicly, we will monitor user reports to evaluate the efficiency of the fix.
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
- Resize to Fit option for Import Activity window's Columns does nothing
Resolution Note:
This issue has been fixed in Unity Hub's versions newer than 3.14.3. Upgrading to the latest Unity Hub version resolves the issue.
Resolution Note (fix version 6000.5.0a1):
This issue has been fixed in Unity Hub's versions newer than 3.14.3. Upgrading to the latest Unity Hub version resolves the issue.
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