Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
Issue ID
1277752
Regression
Yes
[Installer] Standalone Windows editor installer does not clean up completely
When removing a Unity editor installed without the hub, the following files are left over, requiring manual removal:
MIOpen.dll
OpenImageDenoise.dll
optix.6.0.0.dll
optix_denoiser.6.0.0.dll
RadeonImageFilters.dll
RadeonML-DirectML.dll
RadeonML-MIOpen.dll
Repro:
1) Install a version of the editor without the hub (via UnitySetup64.exe)
2) Run Uninstall.exe to remove the editor.
Result:
Leftover files.
Expected:
All files and the editor folder should be removed.
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
- Variable is set to a different value from the selected enum value in the Editor dropdown
- TreeView Child display toggle styling becomes reversed when clicking and dragging it
- Null is returned when using FocusOutEvent.relatedTarget
- Unity_BaseInstanceID is always zero when rendering multiple meshes and instancing with the same buffer
- UI Document button's text does not resize relatively when size in percentage (%) is used
kiecom1998
Sep 15, 2020 17:04
1. Open Unity Hub and go to the Installs tab
2. Click ADD and select any Unity version available there
3. Click NEXT and then DONE
4. Disconnect from the internet while the Editor is still downloading
5. Download and install the same Unity Editor versions as in step 2 from the Unity download archive
6. In the Installs tab click ADD and locate the Editor installed in step 5
Expected results: the Editor is added to the list of Unity installations
Actual results: Installation failed message is displayed and attempting to remove the Editor results in "Could not Delete Files" error
Reproducible with: 2.4.0
Not reproducible with: 2.3.2
Notes:
-An already existing installation can be used in the 5th step to reproduce the issue
-Restarting Unity Hub doesn't fix the issue and the "failed" installations remain. To fix the issue, deleting the Hub cache seems to be required
-Editors.json file points to the correct Editor location after reproducing the bug
-After reproducing the issue a "no folder path defined for {Unity version}" message is logger to the "info-log.json" file
Workaround (the file name changes depending on the version that's stuck in the "failed" state):
Windows: delete the "C:\Users\USERNAME\AppData\Roaming\UnityHub\downloadProgress%3A2018.4.27f1.json" file
Mac: delete the "~/Library/Application Support/UnityHub/downloadProgress%3A2018.4.27f1.json" file
Linux: delete the "~/.config/UnityHub/downloadProgress%3A2018.4.27f1.json" file
kiecom1998
Sep 15, 2020 16:54
Support
How can we assist you today?
Learn more about Analytics here. Please feel free to also submit requests and feedback on the Unity Analytics forum and make sure to check out our FAQ.
Your Name
Your Email
Subject
subject is required