Search Issue Tracker
Not Reproducible
Votes
0
Found in
Issue ID
918667
Regression
Yes
Can't Re-Activate Unity license
Repro steps:
1. Open Unity
2. When greeted by "Unity license is not yet valid" press "Re-Activate"
3. a) Enter your Unity serial number and press next
b) Press Unity "Personal" and press next
Expected result: For Unity to activate the chosen license type
Actual result: Unity doesn't pass the Activation stage/Reverts back to choosing what license type to choose
Reproduced with: 2017.2.0a3, 2017.2.0a2, 2017.2.0a1(Sometimes, look at video)
Regression introduced in: 2017.2.0a1
Did not reproduce on: Everything else
Note:
The sequence in which you launch the editor MATERS for 2017.2.0a1 and 2017.2.0a3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
shubhamswaraj2021
Aug 18, 2020 08:22
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
dionysis
Feb 11, 2019 04:12
I just experienced this issue with Unity Hub 1.4.0 and thought I'd add an observation. I found a non-responsive Unity Hub process running in the background.
As soon as I killed it and deleted the Unity_lic.ulf file that Guif documented, I was able to reactivate my license without further issues.
Guif
Jan 20, 2019 18:15
Removing the C:\ProgramData\Unity\Unity_lic.ulf file worked for me
Guif
Jan 20, 2019 18:15
Removing the C:\ProgramData\Unity\Unity_lic.ulf file worked for me
wsfflyn
Jan 11, 2019 00:48
This issue is reproducible by following the exact steps above. I'm using 2017.4.6f1 on Windows 10. Turning off automatic time update and forwarding time to 4 hours later fixed allows me to by-pass activating the license, but I re-enabling automatic time update caused the same issue. Can we get an update on how to fix this bug or can we open this issuse?
wsfflyn
Jan 11, 2019 00:47
This issue is reproducible by following the exact steps above. I'm using 2017.4.6f1 on Windows 10. Turning off automatic time update and forwarding time to 4 hours later fixed allows me to by-pass activating the license, but I re-enabling automatic time update caused the same issue. Can we get an update on how to fix this bug or can we open this issuse?
phillipvdo
Oct 20, 2018 04:25
SERPENTEAGLE, thank you. After an hour of unsuccessful attempts of activating your method worked.
Going from 12:22 am to 4:22 am by turning ON automatic time worked..
pigravity
Oct 03, 2018 09:06
Same issue here. Frustrating.
DDainys
Sep 12, 2018 15:26
If you are still experiencing this issue in 2017.4, 2018.2 and newest betas, please file a new bug report and add "Issue related to case #918667" with as much info as possible
unity_4xxLqrqapLHfmw
Sep 05, 2018 18:01
This thread was started a year back and I m still facing the issue...