I used the UnityDownloadAssistant-5.1.0b6 to download the beta 6 installation files into a custom folder instead of to a temp folder. The first installation went OK.
Then I had to do a re-installation because I accidentally deleted the compiler. I started the UnitySetup64.exe that was saved before, but this time the installation got stuck at the verification phase, 30%. It would keep the drive busy, making the PC unresponsive. Killing the process nor shutting down didn’t work, I had to pull the plug.
The second time I tried UnitySetup64.exe it got stuck at 30% again. I thought the drive was dying and started to make a back-up in panic. However a full partition image would take 14 hours so I went looking for a different approach. (Scheduled incremental back-ups would have been a good idea for example (but it was my Temp / Steam / Downloads junk drive (but whenever a drive goes to valhalla it still feels like part of me dies)))
After restarting I tried UnityDownloadAssistant-5.1.0b6 again and this time the installation went perfect.
Although it’s still possible the drive is spotty and the installation files were downloaded to a safer place, I think it’s more plausible the installation files cannot be launched separately but have to go through the UnityDownloadAssistant. If so, is it possible to improve the installers so that:
- Launching UnitySetup64 separately does not keep the drive busy
- Making it possible to use UnitySetup64 downloaded through the Assistant to re-install Unity
- If neither is possible, at least show a warning and cancel the installation before panic ensues
