Search Issue Tracker
Third Party Issue
Votes
0
Found in
3.14.0
Issue ID
UUM-135820
Regression
No
"Editor unavailable" message is displayed when navigating to "Get set up" tab in Unity Hub
How to reproduce:
1. Open Unity Hub
2. Navigate to "Get set up" tab
3. Observe the message under “Install the latest Unity Editor” field
Actual result: “Editor unavailable” message is displayed
Expected result: No error message is displayed
Reproducible with: 3.14.0 and later Hub versions
Reproduced on: Windows 11, Windows 10 (by the user), macOS (24.6.0) (by the user)
Not reproduced on: No other environment tested
Note: the issue is not reproducible by staff
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting this issue to Unity.
Based on the information available, the “Editor unavailable” message appears to have been caused by an unstable network connection in the affected environment rather than by a defect in Unity Hub itself.
Because the issue is related to the user’s environment, we are closing this case as a Third Party Issue. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.
Resolution Note:
Thank you for reporting this issue to Unity.
Based on the information available, the “Editor unavailable” message appears to have been caused by an unstable network connection in the affected environment rather than by a defect in Unity Hub itself.
Because the issue is related to the user’s environment, we are closing this case as a Third Party Issue. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation.