Install the Hub on Windows or macOS
Install Unity Hub on supported Windows or macOS systems and troubleshoot common setup issues.
阅读时间8 分钟最后更新于 3 天前
To install the Unity Hub on Windows or macOS, your operating system must meet the following minimum requirements:
- Windows: 10 (21H1 and later, 64-bit versions, including Enterprise LTSC 2021), 11
- macOS: 13 (Ventura) and later
If your operating system is older, install the last Hub version that supports it from Install a deprecated Hub version.
To install the Unity Hub on a supported Windows or macOS system, do the following:
- Go to the Download Unity page on the Unity website.
- Log in to your Unity account or create a new account.
- Select the Download link for your platform.
- Open the installer file you downloaded.
- Follow the instructions in the Unity Hub setup window.
To use the Hub, sign in with your Unity ID. If you don’t have a Unity account, select Create account.
The Hub might request access to your computer's file system locations or to connect through the firewall when you launch it for the first time. It uses these permissions to access your local project files and Unity Editor installations, and to fetch resources from cloud servers.
Where the Hub installs on Windows
The Hub installs on Windows as an MSIX package. Windows manages it like other packaged apps:
Task | How it works |
|---|---|
| Install location | A folder under |
| Find or uninstall the Hub | Settings > Apps > Installed apps. You can also right-click Unity Hub in the Start menu and select Uninstall. The Hub isn't listed in Control Panel > Programs and Features. |
| Start the Hub from a script or the command line | Run |
| Other Windows accounts | If you installed the Hub with the Unity Hub installer ( |
| Desktop shortcut | Installing the Hub doesn't create a desktop shortcut. To add one, drag Unity Hub from the Start menu to your desktop. |
| Updates | Windows updates the Hub. On Windows 11, it can also update the Hub in the background while the Hub is closed. |
| Hub settings and projects list | Stored in |
| Unity Editors | Installed in |
To find the folder where the Hub is installed, run the following command in PowerShell:
(Get-AppxPackage UnityTechnologies.UnityHub).InstallLocation
Update from Unity Hub 3 on Windows
When Unity Hub 3 updates to Unity Hub 4, the update installs Hub 4 first and checks that it works. Only then does it remove Hub 3. If the update can't install Hub 4, it leaves Hub 3 as it was, and you can keep using it.
The update keeps your settings, projects list, sign-in, and installed Editors. It also moves your existing Unity Hub desktop shortcuts and taskbar pins to Hub 4. If it can't move a shortcut, it removes it. To add one again, drag Unity Hub from the Start menu to your desktop.
Hub 4 is listed in Settings > Apps > Installed apps instead, and the Start menu doesn't offer Open file location. To find the install folder, refer to Where the Hub installs on Windows.
The update installs Hub 4 before it removes Hub 3, so the Hub is usually still installed. To check, run the following command in PowerShell:
Get-AppxPackage UnityTechnologies.UnityHub
- If the command lists UnityTechnologies.UnityHub, the Hub is installed. Open Unity Hub from the Start menu. The update can remove your desktop shortcut. To add it again, drag Unity Hub from the Start menu to your desktop.
- If the command lists nothing, download the Hub from the Download Unity page and install it again. If opening the downloaded file does nothing, refer to Nothing happens when I open the .msix file.
Your settings, projects list, sign-in, and installed Editors are kept either way.
If the update removed Hub 3 without installing Hub 4, report it on Unity Discussions and attach the update log. Refer to Find the update log.
Hub 3 is unchanged and still works. The message you saw names the reason:
- This installer is running as a different Windows account than the one signed in: an administrator account other than yours approved the update. Hub 4 installs for one Windows account at a time, so the update stopped rather than install it for the wrong account. If your own account is an administrator, update the Hub again and approve it with your account. Otherwise, install Hub 4 for your account from the file with PowerShell, which doesn't need administrator rights, as described in Nothing happens when I open the .msix file. Hub 3 stays installed until an administrator removes it, after checking its installation folder as described at the start of this section.
.msix - Its data folder is in use by another program: close any File Explorer window, terminal, or app that is using a folder under , then update the Hub again.
%LOCALAPPDATA%\Packages\UnityTechnologies.UnityHub_... - A newer Unity Hub is already installed: open Unity Hub from the Start menu to use it. To remove Hub 3, first check its installation folder as described at the start of this section.
- A Unity Hub package with this same version is already installed with different contents: wait for the next Hub update, or follow the PowerShell command in the message.
- Unity Hub could not be converted to the MSIX package, sometimes with an error number: the message doesn't name a reason. Report it on Unity Discussions and attach the log file named after Details in the message.
Hub 3 shows a failure message once for each version and reason. If the same failure happens again, the update fails without a message. The update log records the reason every time, so if you missed the message, read the log. Refer to Find the update log. If you can't fix the reason, report it on Unity Discussions with the update log.
The update installed Hub 4 but couldn't remove Hub 3. Hub 4 works normally. The message you saw after the update says what to do:
- If it says Hub 3's folder also holds files that aren't part of the Hub, don't uninstall Hub 3 from Programs and Features, because that deletes the whole folder, including those files. Delete only the Hub's own files from that folder.
- If it says Hub 3's uninstaller couldn't be verified, leave Hub 3 as it is and contact Unity Support with the update log.
- Otherwise, you can uninstall Hub 3 from Programs and Features. This keeps your settings and projects list.
The update installs Hub 4 for the account that updated it right away. Other accounts get the Hub the next time they sign in to Windows. If an account still doesn't have it after signing in again, install the Hub on that account from the Download Unity page.
Find the update log
The update writes a log to a folder named , in the file . Failure messages also show the log's full path. You need administrator rights to open this folder. Attach the log when you report an update problem.
C:\Windows\Temp\UnityHubMsix-<ID>UnityHub-msix-conversion.logWindows and macOS installation troubleshooting
Windows opens files with App Installer. Some Windows editions, such as Windows 10 Enterprise LTSC, don't include App Installer, and some organizations remove it. You can install the Hub with PowerShell instead, which doesn't need App Installer:
.msix-
In File Explorer, hold Shift, right-click thefile you downloaded, and select Copy as path.
.msix -
Open PowerShell. You don't need to run it as administrator.
-
Enter, paste the path after it, and press Enter. For example:
Add-AppxPackage -PathAdd-AppxPackage -Path "C:\Users\<username>\Downloads\UnityHubSetup-<version>-x64.msix" -
Open Unity Hub from the Start menu.
This installs the Hub for your Windows account only.
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.