No option to choose install location - Forcibly installed to C-drive. I have a different drive for work (with all the different Unity versions installed, and so on). Didn't recognize existing Unity ID authorization on this computer, although all the actual Unity editors work just fine. After re-authorizing, does Hub "eat" one of the two allowed installs? Wouldn't detect automatically any of Unity versions I had already installed (~20 of them). When manually adding Unity versions, it mistakenly detected the actual versions. For example, I added Unity 5.6.5f1 and it was detected as 5.6.0b1 when showing up in the Installs-list. Because of this, the Hub won't actually open the projects which need that particular Unity version. I guess this is because I have originally installed 5.6.0b1 and many other 5.6.x versions over it, letting the installer always uninstall the previous one. That way removed versions still tend to show up in the Windows Programs and Features -list, so probably something is always left in the registry of those earlier versions and Hub will end up seeing the original version installed. All of those 5.6.x installs have shared same install folder, so that I can have static shortcuts pinned to start menu which point to "Unity 5.6" or "2017.2" regardless of what are the exact versions. Unity Hub seems quite heavy application for what it is. I tend to be rather picky about what's running in the background, especially if they keep eating more memory than a few MB and/or using CPU. Some findings here: After closing the application, it leaves two processes open (about 120 MB of memory, growing each time opening & closing Hub). Having the processes there didn't seem to make it exceptionally fast to startup, if that is the intention. Opening Hub will open yet another process. One of the two background processes keeps eating CPU a bit all the time, spiking a bit occasionally. Not a lot, but enough to notice. Probably a big reason is that the app seems to be made by embedding chromium/node and whatnot. I wish not so many apps would use that model, especially for cases where the software is kept open all the time. To have a bad & good examples for a reference: compare memory&CPU usage of Slack and Telegram (on Desktop windows). Slack has internally the same chromium/node stuff, and can grow up to huge amounts of memory (over 1GB), and is often quite slow when using it. Telegram Desktop is lightweight, has similar functionality (rich enough), and uses only 50-60 MB of memory. I guess it'd be huge change to fix everything I listed in above points. So, at the very minimum, I request you add an option that Unity Hub will never run in the background once it's closed. So far I have habit of including Unity version in name of the project folder, so that it's rather easy to pick up right Unity shortcut and then select the project. A launcher like Unity Hub would be a replacement for that way of working. But so that one would actually use it, it needs to be lightweight enough so that opening doesn't feel like a chore (or running it doesn't feel like waste of resources, if it's in the background).