When I launch Unity hub, does nothing, leaves no log
I tried these:
- Reinstalling
- Checking environment variables: ComSpec correctly set to Windows\System32\cmd, Path env variable checks out, no user variables overriding system variables, PATHEXT variable looking normal
- Running the original exe file as administrator
- Trying on different compability options
- No proxy
I only have C drive. C:\Users<NAME>\AppData\Roaming\UnityHub\logs\ folder is empty, so there are no logs for crashing, which is the most confusing part.
Anything I can do to resolve this issue?
I’m hoping you solved this by now but I just had a similar problem and eventually found a solution for mine which might be related.
TLDR: check for out-dated symlinks, they ‘look’ ok (folder icon with a short-cut style arrow on it) but they don’t work properly and Unity fails silently.
I have a boot SSD and a 14GB Unity asset library which is constantly growing, so I moved the c:\users<name>\appdata\roaming\unity assets to another drive and created a sym-link so Unity would not throw a fit… The target drive started to fail recently, and after copying 1.7TB of files onto a new drive (including my unity installs and unity projects) I wanted to fire everything up and make sure it works.
The hub worked fine (this is where my problem is different to yours) but Unity failed silently on all projects. I reinstalled Unity and it failed again. I ran an uninstall of all versions of Unity (I have 3) and the Hub, and reinstalled everything, it failed again… Then I remembered the symlink. It all works since I recreated it.
Failing that, check for other sources of missing files too (changing a drive volume letter, relocating system folders, you might think of other things that have the same effect). Chances are that Unity is trying to log something (I certainly hope so!) but in these cases it might be very hard to find out where it went.