Now Available: Unity Hub 3.17.3

Unity Engine
, ,
21

Just updated Hub. It takes unusually long now to open Hub. When it finally does open I see all my projects but clicking on them does nothing and I cannot open any of them. I’m on 3.17.1 (a4c4afe).

I also noticed that it cannot find the branch and is just stuck loading the branch:

image
image761×350 24.4 KB

Could it be that I have too many projects and it is trying to find the branch for each of them delaying the whole application? If that’s the case, this kind of information should only be queried when you expand the project dropdown with the arrow.

EDIT:
What I mentioned above seems to be the issue. After waiting about 20-30min all the “Current branch” fields have loaded and now projects are opening correctly again. I don’t even have that many projects in Hub linked to git repos. It might be more than just the git repos, it could just be querying for a lot of info on all the projects listed in your hub.

tldr; You have to wait a long time for it to finish doing things before you can use the Hub again.

22

Does that only occur on the initial load after the update, or every time you re-open the hub?

23

I will say having unity hub open did lock all the known project folders so i couldnt have a cull.. had to close it to allow this to happen

24

I’ve filed a bug.

From the log, clicking on a project created the following log, which I captured until the boot screen appeared. Briefly before the editor boot screen appeared, a loading/processing bar appeared under the project name.

The logs actually show that it took closer to two minutes, not 30 seconds, in this instance. While waiting I did move focus between the text viewer with the logs and the hub client itself.

{"timestamp":"2026-04-15T21:34:22.387Z","level":"info","moduleName":"AmplitudeExperimentService","pid":12992,"message":"Fetching feature flags"}
{"timestamp":"2026-04-15T21:34:22.399Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:34:22.534Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:34:32.816Z","level":"info","moduleName":"LicensingSdkService","pid":12992,"message":"checkEntitlements: checking entitlements for: com.unity.editor.ui"}
{"timestamp":"2026-04-15T21:34:32.827Z","level":"info","moduleName":"LicensingSdkService","pid":12992,"message":"Successfully checked for entitlements request."}
{"timestamp":"2026-04-15T21:34:43.460Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:34:43.510Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:34:49.598Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:34:49.647Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:35:46.915Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:35:46.918Z","level":"info","moduleName":"AmplitudeExperimentService","pid":12992,"message":"Fetching feature flags"}
{"timestamp":"2026-04-15T21:35:47.014Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:36:09.354Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:36:09.420Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:36:14.030Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:36:14.077Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:36:14.963Z","level":"warn","moduleName":"LocalProject","pid":12992,"message":"project.openInEditorUrl ipc message is supported."}
{"timestamp":"2026-04-15T21:36:31.836Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Fetching banners from hub-globalBanners document for language: en"}
{"timestamp":"2026-04-15T21:36:31.881Z","level":"info","moduleName":"sanityCMS:fetchBanners","pid":12992,"message":"Successfully fetched banners from hub-globalBanners document"}
{"timestamp":"2026-04-15T21:36:32.172Z","level":"warn","moduleName":"LocalProject","pid":12992,"message":"show.package.manager ipc message is supported."}
{"timestamp":"2026-04-15T21:36:32.173Z","level":"info","moduleName":"LocalProjectService","pid":12992,"message":"openProject projectPath: D:\\Development\\Projects\\REDACTED\\midiaudiotesting\\midiaudiotesting_unity, current editor: undefined"}
{"timestamp":"2026-04-15T21:36:32.173Z","level":"info","moduleName":"IPCServer:LocalProject","pid":12992,"message":"Forwarding postal event: project.opened"}
{"timestamp":"2026-04-15T21:36:32.173Z","level":"info","moduleName":"LicensingSdkService","pid":12992,"message":"checkEntitlements: checking entitlements for: com.unity.editor.ui"}
{"timestamp":"2026-04-15T21:36:32.185Z","level":"info","moduleName":"LicensingSdkService","pid":12992,"message":"Successfully checked for entitlements request."}
25

Hi,

  1. Thanks - quite the nasty bug. Seems like not everyone encounters this bug, though. It may be situational. I specifically opened my project first then clicked the update button about 5 seconds later as it was opening. Either way, it shouldn’t be touching project settings at all if it’s just a launcher without explicitly letting us know. I couldn’t repro the bug on my other device when I carefully updated. Other device had Unity closed when I updated.

  2. Renaming the dir back worked fine - it was just the installer that flipped it - it doesn’t seem to actually want to keep it there.

  3. In case it actually was a blocker, you need a link to Hub archives within Hub - don’t hide it. This is about the 5th time I’ve had issues updating Hub in the past year. Everyone has bugs, but so many breaking releases per year feels shocking. If you’re using AI to speed you guys up, wonderful - but please QA it to the max. You’re delivering updates to millions of people. More AI requires more QA.

26

I mean in one of the many posts that you blasted about this they mentioned the hub doesn’t touch the folder at all: Unity Hub update made breaking change to Build Profiles? - #6 by christophera_unity

It was probably something else at a coincidental time.

27

The hub seems to be fine now. Only happened on initial update.

1 Like
28

Unfortunately AUR is still on 3.16.2-1 so no new Hub for us.

29

Hi @Lurking-Ninja

Quick reminder that Unity only supports Ubuntu officially. We provide deb and rpm installers for Linux. The AUR and flatpak versions are unofficial community releases that we have no affiliation with

30

I know. Sorry, didn’t try to imply that you would support any other linux distro. I’ll try to choose my words more carefully in the future.

31

Please speed it up.

You open it, and it takes 10 seconds to even appear as a task, then when it appears you watch a spinning circle for 1 minute, then clicking a project does nothing until 10 seconds later.

Also have high power usage in task manager as mentioned.

32

Agree. On my machine (with an AMD Ryzen 9 5900HX), it takes wholly 13 seconds to be fully available.

33

Hi folks,

Hub v3.17.2 is rolling out now! All the bug reports you made were invaluable in helping find the cause of the performance issue.

Bug fixes & improvements

  • Fixed an issue where users experienced high CPU usage during startup caused by excessive file watching and missing version control configurations.
  • Fixed an issue on Linux where .deb package installation could fail on some setups when AppArmor profile loading could not complete in the kernel.
  • Fixed an issue where the bundled Unity Version Control install or the cm on PATH could become broken, leaving version control in an unusable state.

Thanks for all the help and patience while we resolved the issue here!

2 Likes
Unity Hub 3.14.0 CPU usage crazy high doing what
Now Available: Unity Hub 3.17 beta
Latest Unity Hub 3.17.1 'mini' spiking Mac CPU
34

Please also look into not locking all project folders listed in the hub while the hub is open

2 Likes
35

There’s been little appreciable change in Unity Hub’s CPU usage, for me, since the update. I have 31 projects set up to use version control outside of Unity’s package and I’m guessing that this is tied to the issue. Presumably more projects would compound the problem.

Since the intended fix is related to ‘excessive file watching and missing version control configurations’ is there a means to disable this? Perhaps to minimal or no file watching, and without a need for version control configurations. But, of course, not by removing version control entirely. I want to continue to use what I have already set up, yet the only option I see through Unity Hub is to disconnect projects from their repositories.

Further, the CPU over-usage is constant and consistent for as long as it the Hub remains running, even though the fix states “during startup”.

36

@Satinel, sorry to hear you are still experience the issue. Can you please submit a bug ticket by following the steps here, this will give us more information to debug your case.

In the meantime, you can download a deprecated version of the Hub from our Docs page: Install a deprecated Hub version • Unity Hub • Unity Docs

37

I’m still experiencing the high cpu usage with v3.17.2, it might even be worse now. I had to rollback to UnityHubSetup_3.14.5 because it was the only one I could find an official download

2 Likes
38

@DJ_Link - we are continuing to investigate this issue. Can you please submit a bug ticket to help us find the issue?

39

Can confirm I still have 30-45% CPU usage after the update to 1.17.2. For reference I do have a lot of projects, many on external drives not plugged in, and many using a variety of source controls (GitHub, Plastic, Perforce, etc). At least opening the Hub program seems quicker & clicking on a project now instantly opens it though! I’ll just have to close the Hub program after my projects open for the time being.

1 Like
40

Same here. Enormous CPU usage + most of the times clicking on the project to open it does nothing

1 Like