Licensing: System ID Changed

Cubase
, ,
1

Hello. I’m having an issue with my Cubase 13 license.
This started happening after a Windows 11 update that my system performed 2 weeks ago. Ever since, whenever I launch a new Cubase session, I get the following message

System ID Changed
Your system ID has changed, likely due to a hardware or software update. Would you like yo update your license for this new machine?

I always click on “OK”, but the message just shows up again the next time I launch Cubase. Anyone knows a solution for how to update my license permanently? Thank in advance for any help!

System Information:
OS: Windows 11 Pro
Version: 24H2
CPU: AMD Ryzen 9 5950X
RAM: 64 GB

2

Same is happening to me in cubase 14

I ended up doing a complete reinstall of windows but it still came back.

3

Hi, this message doesn’t look familiar to me. I would assume that this is from another vendor’s plug-in?

4

Nope!

5

Does that mean that you don’t have any non-Steinberg plug-ins installed?

6

Does the message look like this?

1 Like
7

Fixed! Checking the e-licence control app showed the soft e-licence was corrupt and was unable to be restored, did another reinstall of Windows 11, reinstalled Q14 and now all is fixed. It must’ve corrupted. In the original install.

8

Also fixed on my end. It turned out to be a 3rd-party license. It seems like Korneff Audio’s licensing system was affected by the last Windows update. Since I have their limiter plugin as part of my production templates, the licensing system fooled me into believing it was Cubase who was complaining about the license (since there was no application title on the licensing window). I only stumbled onto it because I recently had to work in Ableton Live, and the same licensing window came up when I dragged an instace of the limiter into a track. That clued me into what was going on. After re-authorizing the plugin in Ableton, the window stopped showing up in Cubase.
My only question is why Ableton was able to successfully register the new license for the plugin, whereas Cubase couldn’t. Anyway… issue resolved, and now I know what to look for in the future.