Search Issue Tracker
Fixed
Votes
1
Found in
2017.3.0f3
Issue ID
1010822
Regression
No
[Unity Hub] Hub searches for Unity in the wrong folder after changing Installation destination while installing a version
How to reproduce:
1. Open Unity Hub
2. Go to the Installs tab, select a version, start installing it
3. While it is still installing, change the installation folder to something else
4. After the installation, attempt to open a project with the installed version. Observe the error
Expected result: The version is installed in the old destination and Unity searches for the version in the old destination.
Actual result: The version is installed in the old destination, however, Unity searches for the version in the new destination.
Notes: Attempting to locate your version with the "Locate a version" button in the Installs tab fails to locate your editor, as Unity Hub believes there's another copy of the same version installed in the new folder. Trying to uninstall the version is impossible, as the "Uninstall" option is not present. There is an easy workaround, which involves simply setting your destination folder back to the old folder that the version was installed in. Going back to the new folder again after doing so no longer reproduces the bug.
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:
Resolved in Hub v0.15.0