Same issue on Mac Sonoma 14.2, Unity Hub 3.7.0

I had the same issue with the inability to get Personal license in Unity Hub 3.6.1, but remembered that I had changed my Unity Hub password as I was installing it. Signing out of hub and signing back in with new password fixed the issue. I hope this helps.

Same issue on Unity Hub 3.6.1 running as Admin on Windows 11.

Had the same problem with unity 3.5.0 on windows 11

Here's how I got it to work for me: close/exit Unity Hub and start it as administrator

Same problem with a personal license on Unity Hub 3.4.1.

Can confirm that the issue is still present in Unity Hub 3.3.0.

I think Unity should strongly reconsider the architecture of Unity Hub. It slows down the workflow so much that people have made their own multiple lite versions of Unity Hub using Rust or C++ and what not. They don't let you install an editor, but they do come with a full-fledged project management window.

And if people have to figure out how to install older versions *just* so they can actually install an editor, it means something is seriously wrong.

Having this issue with unity Hub 3.2.0 on Windows 10 after being kicked out of Unity Hub this morning
Same account signed into Hub and online, can see Personal License online
- "Get personal license" within Unity Hub 3.2.0 does nothing, even when Running as Administrator
- License file does not work, even with “<Binding Key="4" Value="" />” without outer quotes within <MachineBindings> section

Found Wayback Machine archive link of Unity Hub 2.3.2
- "Get Personal License" link works
- On subsequent Upgrade/License Failure of 3.2.0, 2.3.2 STILL sees my Personal License

I am having this issue with Hub 3.1.1 on Windows 11. It cannot activate a license automatically or manually. The issue appears to be not having permissions to write to the folder where it wants to save the license folder (probably because my user is not an administrator user). When I try to open Hub as administrator from my user it doesn't work at all (just blank window with no UI).

The workaround appears to be to make my user and Administrator, then run Unity Hub as administrator, and then it will work. However I believe the correct way for Unity Hub to handle this would be to prompt for administrator access only when required (i.e. when saving the license file). This would allow an admin user to authorise just that operation rather than requiring the user to be running as admin the entire time. It would also clarify what is going on by making it clear that the issue is that you need admin rights to activate the license.

Even better would be to not require admin rights to activate the license.

I did a FRESH Windows 11 Install and off the bat Hub, 3.0 would not activate. It works with 2.4.5, but as soon as I upgrade to 3.0, it doesn't recognize the license.

So now have to uninstall and reinstall 2.4.5 again. Source of this content is exerror.com

I have macOS 10.12.6 and have same problem.
Please fix it or provide access to old version (2.4.5) of Unity Hub.