Help

For more information on how to access troubleshooting options from the Unity Hub, go to the Profile page.

Frequently Asked Questions

Where can I find the Unity Hub logs?

To find Hub logs, do one of the following:

  • Go to Account > Troubleshooting > Open log folder.

  • On the Hub Tray Menu, go to Troubleshooting > Open Log Folder.

  • Alternatively:

    • Windows: %UserProfile%\AppData\Roaming\UnityHub\logs

    • Mac: ~/Library/Application\ Support/UnityHub/logs

    • Linux: ~/.config/UnityHub/logs

What should I do if Beta presents a critical bug for me?

If you encounter a bug that prevents you from proceeding in Unity, reinstall the Unity Editor. To reinstall the Editor, do the following:

  1. Under Preferences, select Advanced.

  2. Choose the Production channel.

  3. Restart the Unity Hub.

  4. Reinstall your preferred Editor version.

How do I report a bug?

To report a bug to Unity, do one of the following:

  • Go to Account > Troubleshooting > Report a bug.

  • On the Hub Tray menu, go to Troubleshooting > Report a bug

How do I change back to Light Mode?

Light Mode will be available in a future version of the Hub.

The option to add a module to one of the Editor installs isn't there. What do I do?

You can't add modules to Editor installations that weren't installed with the Hub. To add modules, do the following:

  1. Remove the installation.

  2. Use the Hub to download and install the Editor.

Why can’t I install a missing Editor for a project directly?

This feature is currently in development and will be available in a future version of the Hub.

I am on Mac Catalina. What do I do if the Hub asks for permission to access different folders and services on my machine?

As part of the Unity Editor's parent process, the Hub asks for the Editor's required permissions. The Editor can require permissions for reminders, camera, and keyboard.

I tried to use the manual installer to add Unity version(s), but the install path was modified. What does that mean?

If you use the installer to manually install Editors after you have installed Editors through the Hub, the default installation path might be set to the last path used from the Hub because the Hub also uses the installer. For example, the installation path might be set to an Editor version's folder path. Change the install path when you manually install the Editor, so you don't overwrite the last version of the Editor that was installed from the Hub.

I removed the Hub and now I can't reinstall it. What do I do?

On Windows, if you deleted the Hub without using the Hub uninstaller tool, you might need to clean the Registry to reinstall the Hub.

I am on Windows 10 and can't install the Hub. What do I do?

You will need to add a system override for Mandatory ASLR because the Unity installer won't work with this setting enabled. To override this setting, do the following:

  1. Go to Windows Security > App & browser control > Exploit protection settings > Program settings.

  2. To add a program to customize, do one of the following:

    • Select Add by program name to add a program with the executable file name. For example, file names can include UnityDownloadAssistant-2019.2.12f1.exe or UnitySetup64.exe.

    • Select Choose exact file path to navigate to the executable file of the program you want to add.

  3. In the Program Settings window, go to the Force randomization for images (Mandatory ASLR) section.

  4. Select Override system settings.

  5. Enable Override System Settings.

  6. Select Apply.

  7. Repeat this process for all versions of the Unity installer.

I selected a network drive relative path as a download or installation path, but it won't complete the download or installation. What do I do?

Hub doesn't support network drive relative paths or symbolic links. You need to specify the exact path for download and installation.

Linux Frequently Asked Questions

Why do I only see the beta version of Hub when I try to install with apt-get install unityhub?

Only the beta version displays if you have both STABLE and UNSTABLE repositories configured. By default, the apt command lists the latest version of the package. To install the stable version of the Unity Hub, you can do the following:

Install the stable version of the Unity Hub in Debian

  1. Disable the beta repository.

    $ sudo mv /etc/apt/sources.list.d/unityhub-beta.list /etc/apt/sources.list.d/unityhub-beta.list.bak
$ sudo apt update
$ sudo apt-get install unityhub

  2. Query the specific version of the Hub.

    $ sudo apt-get install unityhub=3.x.x

Install the stable version of the Unity Hub in Rel/CentOS

  1. Disable the beta repository.

    $ sudo mv /etc/yum.repos.d/unityhub_beta.repo /etc/yum.repos.d/unityhub_beta.repo.bak
$ sudo yum check-updates
$ sudo yum install unityhub

  2. Query the specific version of the Hub.

    $ sudo yum list unityhub
$ sudo yum install unityhub-<version info>

When I install the Debian package, I receive the following error message: /etc/apt/sources.list.d/unityhub.list: No such file or directory. What do I do?

This can happen when sources.list.d doesn't exist or you don't have access to create the file. To fix this error, manually create the folder and an empty unityhub.list file with the following commands:

$ sudo mkdir /etc/apt/sources.list.d
$ sudo touch /etc/apt/sources.list.d/unityhub.list

When I remove, add, or update the Unity Hub in the command line, I receive an error message that states that the lockfile is in use. What do I do?

If you receive a lock file error, an associated process number should also display. In this example, the process number is 4076.

$ E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 4076

If this error displays, use the following command to stop the process. In the command, replace 4076 with the process number that your device displays.

$ sudo kill -9 4076

If you remove the Unity Hub after you perform this command and this error shows up, follow the instructions in the command line to fix it.

$ sudo apt-get remove unityhub
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. 
ubuntity@ubuntu:~$ sudo dpkg --configure -a