This article explains why you might see the message "Your license is already active on two devices" in Unity Hub, even if you’ve only activated it on two machines. The issue stems from a conflict between older serial key activations and the new Named User Licensing system. It provides clear steps to resolve the problem by returning license activations, deleting the license file from your system, and signing back into Unity Hub so your license activates automatically without a serial key. ✨
Cause:
This warning is typically caused by a conflict between the new Named User Licensing (NUL) system and the older serial key activation method. If you're using a Unity Industry, Enterprise, or Pro plan, it primarily relies on the modern NUL system, which automatically activates your license when:
- You sign in to Unity Hub
- You refresh your license through the Licenses tab in Unity Hub
- An automatic token refresh occurs (approximately every two hours) while you're signed into the Hub
Although these licenses support two active devices at the same time, having previously activated a device using a serial key can cause the system to interpret it as two separate activations, essentially counting the same device twice.
Resolution:
To resolve the conflict, go to your Unity ID page and return the activations linked to your license. This support article provides clear steps if you need help with that. Next, follow the steps below:
- Sign out of Unity Hub on all your machines.
- Close the Hub completely using the task manager or similar.
- Delete the current license file. Using your file explorer, navigate to:
- Windows:
C:ProgramData/Unity -
Mac:
Library/Application Support/Unityand delete the.ulffile housed there.Note: Folders might be hidden.
- Windows:
- Then, sign back into Unity Hub on your devices, and your license should activate automatically without needing a serial key.
More information:
Users can still activate using a serial key in specific scenarios, such as automated build environments or situations that require a manual activation.
If you're still getting this error after troubleshooting, contact Customer Experience, including your Hub log file in your ticket, so we can examine your issue more closely.