Search Issue Tracker
Not Reproducible
Votes
4
Found in
6000.0.37f1
6000.1.0b5
6000.2.0a2
Issue ID
UUM-96843
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.16.2
Reproducible on: Windows 10, Windows 11, macOS 24.0.0 (M1), macOS 24.1.0 (M1), macOS 24.2.0 (M4 Max), macOS 21.6.0 (Intel i5 1,6 GHz), macOS 23.2.0 (Intel i3 3.6 GHz)
Notes:
-Not reproducible by CQA
-All versions listed under "Reproducible on" were reported by users
-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)
-
DragonfiAR
Apr 04, 2025 09:29
The workaround says to do the following:
Uninstall Unity Hub
Open “C:\Users%username%\AppData\Roaming\UnityHub”
Backup “editors-v2.json” file (information about installed Editors is kept here)
Delete all of the files inside
Install Hub again. You can download the latest Hub installer from “https://unity.com/download ”
Open “C:\Users%username%\AppData\Roaming\UnityHub” and paste the saved “editors-v2.json” file here.But there is no editors-v2.json file in the folder. I also can't open any Unity Editors directly either so this is blocking all Unity development for my business.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
This should be fixed with the new start up improvement for the client v1.17