Question "There was a problem activating a new personal license. Make sure you are logged in, and have intern

Ok so got it working, made a .alf file in CMD, then make sure to open license.unity3d.com/manual inside the unity hub and then you can get an activation file.

 

Same issue with Unity Hub version 3.0 as others in this thread. I can't activate my license or work.

Like dragnagel, in Terminal, I manually generated a .alf and got a .ulf file. But unfortunately, activation still fails!

1) In terminal, I did:
/Applications/Unity/Hub/Editor/2019.4.32f1/Unity.app/Contents/MacOS/Unity -batchmode -createManualActivationFile -logfile

This generated the .alf which was called Unity_v2019.4.32f1.alf.

2) In hub I went to step2 license.unity3d.com/manual And uploaded My .alf. This did successfully download a .ulf.

3) However, as shown below, on then uploading the .ulf is says Unable to save license.


Still stuck. Frustrating! A puzzle that just hits more dead ends.

 

Thank you! The manual activation guide worked for me when nothing else here did. I didn't need to uninstall Hub - I had already used it to download 2021.2, so I used the 2021.2 copy of Unity.exe to activate per the Manual Activation Guide. Manual activation through the Hub menu does not work for me - only using the command line process through the 2021.2 install worked. No need to force quit processes or run anything as admin here.

Possibly useful information if anyone at Unity finds this: When I try to use the manual activation option in Hub, the license file returned by the server is labelled "Unity_v2017.x.ulf" even though the file I upload from Hub is named "Unity_lic.alf". Maybe it's just returning the wrong format, or mixing up the request with an older one on my account? This is a newly reimaged system that previously had older Unity versions installed, but currently has nothing but Hub and 2021.2 installed.

 

Take another look at the directions. There is another command needed to apply the license file - do not use Unity Hub to apply the file.

 

Good catch(!), but unfortunately it still did not work from Terminal. I closed Hub and activated my file via Terminal:

/Applications/Unity/Hub/Editor/2019.4.32f1/Unity.app/Contents/MacOS/Unity -batchmode -manualLicenseFile /MYPATHWAY/Unity_v2019.x.ulf -logfile

Terminal did not report any errors, but going back into Hub its the same issue.

 

Worked for me https://stackoverflow.com/a/70720005

 

Had the same issue. I ran the Unity Hub executable (/Application/Unity Hub/Contents/MacOS/Unity Hub) with sudo. Performed the normal process to add the license. It worked fine. Closed Unity and then ran Unity hub again without sudo by clicking on the Unity icon in the launchpad and everything worked fine.

 

Please can someone help me?
Since this 3.0 version is broken. Create download link for old app.

English is poor, I apologize to everyone.My

 

Something similar to this worked for me when absolutely nothing else did. And I am running OS 10.12.5 which is not exactly current! haha.

To elaborate on this (and it might help out SunqqS too), all I needed is any pre-Hub Editor version installed and licensed. I had one from 2018 (instead of the 2017 one recommended in the Stack link). Then I uninstalled Unity Hub and all more recent Hub-dependent versions of the Editor. Finally, I re-installed my most up-to-date Unity Editor.

At this point, if this solution works for you, you don't even need Unity Hub to get back to work on your project. Simply open the Editor (licensed) and point to your project folder. I am back in business! At this point, I am not going to even bother with Hub until I check these threads and receive support on my ticket. Hub only created issues and it's not necessary at the moment. Just thanking this community and those on the link so that I have a good-enough solution to get back to work.

 

Hello, same problem, nothing works.

I am a paying customer that can't use Unity to work on my game anymore costing days of work ... someone from Unity please help / do something!

Support Ticket opened (#1162677)

 

if this https://docs.unity3d.com/Manual/ManualActivationGuide.html didn't work, try opening the scene that you want to edit directly.
just go to the location of your project then assets then scenes and right click you scene and open with the unity editor.
worked for me !

 

Got license after upgrading to 3.0.0-beta.7 in Linux.

 

¿Alguien sabe como solucionarlo?

 

Saw this in another post and it worked for me;

1. Unistall Unity Hub 3.0
2. Install a previous version with this link:
https://web.archive.org/web/2020081....cloud.unity3d.com/hub/prod/UnityHubSetup.exe
3. Activate license
4. Update to 3.0

Hope it can help other people!

 

This worked for me.

I got the error after I updated from Windows 10 to 11 and also updated Hub to 3.0 (not sure if perhaps only one of these was the cause). The symptom was the 'unable to save license' message.

 

wtf with this freaking dumb bug bothering us for so long,
solved with this method, thanks a lot

 

This was the only solution that worked for me.
Well, except that I haven't updated back to 3.0 cause I fear its gonna break again.

 

-----------------------------------------------------------------------------------------------------------------------------------
Hi am also having the same problem, since 1 week I tried almost everything to fix it but no luck,
finally, I dig in a little bit and find one solution by myself, and I got the personal license, and it's working fine now.

steps:
1. download the license request and generate the license file.
2. sign out with your current account and close the unity hub.
3. go to the C:\ProgramData\Unity ( ProgramData this folder may be hidden, if so first unhide it then follow 3rd step ).
4. in the ProgramData\Unity folder you will see Unity_lic.ulf file, cut this file and paste it somewhere, you can also delete it.
5. grab the generated license (step 1) and paste it here.
6. open the unity hub and sign in.
7. go to license and get the personal license
8. if step 7 fails try 2 - 3 times.

Note: This works for me and I am able to create a project now, hope this will work for you as well, Thanks.

 

I received this link from Unity:
https://issuetracker.unity3d.com/is...n-license-when-activating-it-in-the-unity-hub

So I guess its a known issue.

I did a fresh upgrade to Windows 11 and installed Hub 3.0 and could not get personal license.

Downloaded 1.6.1 from another thread and that activated.
Downloaded 2.4.5 from wayback https://web.archive.org/web/2021080....cloud.unity3d.com/hub/prod/UnityHubSetup.exe

License works to 2.4.5 - but if I then "Upgrade" Hub to 3.0, I get the same problem. So if you may need to stay on 2.4.5.

 

Unreal is the real choice?

 

For mac
https://web.archive.org/web/2020081....cloud.unity3d.com/hub/prod/UnityHubSetup.dmg
helped me.
Updating to 3.0 is succeeded.

 

why is such broken piece of update is even allowed to be published? it basically locks everything and it's not a beta but a production release.
speaks volume about their quality.

 

YASS! Running as root worked for me on osx

sudo /Applications/Unity Hub.app/Contents/MacOS/Unity Hub

 

i fixed the link now

 

I am currently facing the same problem

 

hey the link is not working

 

how?

 

This opens calendar view, you should be able to find an old version of your liking
https://web.archive.org/web/2021*/https://public-cdn.cloud.unity3d.com/hub/prod/UnityHubSetup.dmg

 

thx

 

Run this command from terminal

sudo /Applications/Unity Hub.app/Contents/MacOS/Unity Hub

 

command not found

 

same problem

 

Thanks a lot man, I was working out for 24 hours and it was so simple.

 

Only way is to download an older unity hub

 

i found a download link for downgrade Unity hub to 2. 0. 4 version. by downgrading Unity hub I fix the problem.
Here's the link: UnityHubSetup-2.0.4.exe (dropbox.com).
Then you can update it again to 3.0

 

Please, always be mindful what kind of executables you're running on your computers. Especially getting it from random forum users or random dropboxes. You never know who made that executable and what's in there.

 

I found that version of unity here: Old Version Of Unity Hub - Unity Forum

 

DEU CERTO PRA MIM MANO, MUITO OBRIGADO, TAVA QUASE FICANDO DOIDO AQUI HEHE

 

Hi, all. Here is the solution that worked for us:

sudo chmod a+w "/Library/Application Support/Unity/Unity_lic.ulf"

On our Macs (Big Sur), the problem seems to be an access problem with the Unity_lic.ulf file. The terminal command above fixes that. Running the hub with admin privileges from the terminal as others have suggested works (you have write access to the ulf file), but on multi-user systems (like in our lab), this method breaks (you have to do it every time you change user).
As an added bonus, the "chmod" solution also resolves another unrelated problem we had: the nagging "Unity Hub Wants To Make Changes" pop-up goes away.

 

I am having the exact same issue and have tried everything with no success

 

For some reason, my mac tried to open it with wine stable (which obviously didn't work because wine doesn't have gigs)

 

Man, everyone keeps saying this, no one says how to do that.

 

Worked great for me on M1 Mac and OSX Monterey.

command I typed was: sudo /Application/Unity Hub/Contents/MacOS/Unity Hub

 

Right click the application in the Windows folder. There you can see run as Administrator.

 

Switching the channels from Production to Beta solved the issue for me.

 

For Mac install the latest beta (https://unity3d.com/beta/2022.1a#downloads) and use the first method in this article (https://www.wikihow.com/Open-Applications-With-Root-Privileges-on-a-Mac) to run sudo
installing the license will work fine

 

You give me the right direction; i'm working on Linux and had same issue; problem in my case was /opt/UnityHub directory was owned by root:root, I just did a :

sudo chown -R myuser:myuser /opt/UnityHub

And launched it again and this error went away.

Problem in my case was installation was made by root user and only root had permissions to run it properly...

Thanks!

 

How?

 

Thanks, this worked for me!

Some things to note though:

1. Simply logging out of my account in Hub then logging back in fixed the problem on my laptop, but not on my desktop.
2. Installing the new beta worked on my desktop, but only after I disabled my VPN.