I thought Cubase 12 would do a license check once a month but it happens every time on startup and I’ve had to reboot a few times now because the licenses weren’t found?
2 Likes
I’m seeing the same check at every start, and it’s not exactly quick.
On Mac here the same. But no problem, when I block it. This kind of checking do a lot of apps. But I have none, which stops working when blocked. But you should let it connect from time to time. I just had to authorise BFD again, because it has been offline for more than 30 days.
I’m wondering the same. I had the issue yesterday that for whatever reason no license could be found because of a network connectivity issue and I wasn’t able to use Cubase. How do I prevent that from happen respectively what about that alleged once-a-month license check?
Please read the official Steinberg notes about this in the New Steinberg Licensing FAQ | Steinberg
How often will I need to connect to the internet? Do I need to be connected all the time?
Your computer only needs to be connected to the Internet in order to sign in with your Steinberg ID and to obtain the initial activation. Thereafter your computer can remain disconnected from the internet, and your software will continue its normal operation. Running your Steinberg software does not require a constant internet connection.
Yes that’s clear so far but I’m still wondering why it is doing the lengthy license check on every startup. Is it because I actually do have a permanent internect connection and it therefore checks it every time? Maybe I am missing something but I haven’t found anything specific about that. It’s not a dealbreaker but the initial startup of Cubase 12 appears to take way longer for me than it did before the new licensing system because of that.
There’s no internet connection going on for this.
Probably Cubase is waiting for the Activation Manager components to launch.
1 Like
Ah ok that makes sense. I was assuming it was actually checking the license servers during that part.
Which means my issues yesterday were probably not related to connectivity but rather to the Activation Manager being borked or something like that. (since it worked again after a reboot)
Yes. You can always force quit the Activation Manager or the SteinbergLicensingEngine.exe if it’s stuck, but I say that from doing it on my machine, my personal experience, only.