I had Cubase Pro 15 installed and working on my Windows laptop, but after a serious system crash Cubase now shows “no license found” when I try to launch it, even though my project files are intact.
I have already redeemed my Cubase Pro 15 activation code in my Steinberg account and in the download/activation tools, and the code is accepted as successful, but Cubase still asks me to verify the license every time and will not start.
oops. didnt mean to include that! I have logged this as a ticket. I’m hoping Steinberg will re-authorise me. I have done everything possible - inserted my Access Code multiple times into the Assistant. rebooted multiple times. Sill being asked for a license even though it was running fine before my computer crash.
I’m having a serious issue with Activation Manager and hoping you can help or point me in the right direction.
The problem: Activation Manager sends me into an infinite loop — I never reach the point where I can input my Access Code. I’ve collected a string of diagnostic logs but haven’t been able to get past this.
I’ve already raised a support ticket (#767174), but since logging it I’ve noticed the issue has spread — Dorico is now also inaccessible. Entering my Access Code directly into Download Manager hasn’t resolved things either, so Cubase Pro 15 remains unactivated.
This is particularly frustrating as everything was working correctly until recently.
If whoever picks up ticket #767174 could address both the Cubase and Dorico activation issues together, that would be much appreciated.
What’s probably happening is that you are logged out from the S.A.M, so you have to log in.
As displayed in my profile here, I am not a Steinberg employee, so please keep that in mind.
There’s no info in your posts that tells us what steps you have taken. The issue is probably fixable, but you should make sure you understand what the activation manager does, which is: it displays the licenses which are also shown in your steinberg.net account.
In any case you have not said anything about what actually happens when you try to use the Steinberg Activation Manager.