Here is your screenshot, it has happened to me all week!!! (LOL).
This is the task manager version that I am experiencing.
This goes on endlessly, hours, and never resolves.
On initial start-up, the CPU % gets as high as about 5% for me and everything appears to be rolling fine. Then when it gets to the VST3 initializing part, it freezes, so it seems.
I really hope that someone will be able to actually help…
I have tried reinstalling Windows, I have all of my drivers up to date, and all of the typical things that I seem to have to do after updates have been attempted.
Thank you GlennO for the question. And the answer, Because I do not know what I am talking about and shouldn’t be expected to have to even investigate this on my own. LOL… Man, what a frustration this is as well.
I just want to live my life and make music, but Cubase 13 Pro won’t allow me to!!!
This is what I see in the Task Manager.
I have tried to delete the files in the CB appData folders as other posts have suggested. No success there.
I have also reboooted, reinstalled CB, reinstalled Win11, all of the typical things that the tech support will have you do, no success there eighter.
Things seem to load fine through the VST 2 scan but then hard stops at the VST 3 scan.
I have left the computer on for hours, multiple times and have returned to find CB stuck on the VST 3 scan part.
The task manager CPU % gets as high as 4-5% when CB starts but drops to 0% when the VST 3 scan starts.
If you happen to have any suggestions or questions, please offer them. I am ready to try something new.
The problem is that I update and upgrade to purchase out of problems, not to purchase into them.
Well then, please offer a question or a suggestion. Please go away if you are not going to do either of those.
I am already frustrated because CB was working and then suddenly stopped.
I see in the task manager “checking licenses”
I also explained the VST 3 hard stops.
I also explained what I have tried.
Again person, I would prefer that you go away if you aren’t here to assist. I came to the forum for assistance. Most people only read posts when they have nothing of value to offer. Don’t waste peoples time person.
Maybe you missed it, but I already explained the cause of your problem in a post above. It’s a bit of a mystery why you are posting in a thread about licensing.
When I opened CB in “safe mode,” the task manager does not say “checking licenses;” it now says Cubase Pro Hub.
Maybe I misunderstood the nature of the post from Haavard.
I read “The newest Cubase brings an old, annoying bug back: It is “checking licenses” continously.”
But again, please do not address anything that I post if you are going to try to frustrate me more. I am sure there are others that are more patient with a Cubase computer forensics novice such as myself.
Take care.
@Haavard
I don’t want to question your experiences with the computer performance in Cubase, but I have some doubts about the share of the Steinberg License Engine (the originator of the Checking Licenses message) in the overall load. I’ve observed that its share of CPU time is very small compared to the main Cubase process, typically less than 1 per thousand:
This already low load also falls almost entirely in the startup phase of Cubase, after which the process remains mostly inactive and does not use any significant CPU resources. This leads to the conclusion that the high load you mentioned and the associated impairment of performance has other causes than the suspected Steinberg License Engine.
@KingHuru
Also in your case, the Steinberg License Engine is not the culprit. It only checks the licensing of the components of the Steinberg content and has nothing to do with scanning the VST plugins, which is the responsibility of the vstscannermaster process (with the vst2xscanner and vstscanner subprocesses).
Both processes are loaded at the same time when Cubase is started, which can give the impression that one process is delaying execution when in fact another process is the culprit. However, the screenshot you posted clearly shows that the delay is caused by the VST3 plugin scanning. A possible solution in this case would be to gradually exclude the existing plugins in order to identify the faulty one.
I don’t know why you are trying to piss off others.
You entered a thread, and other people tried to explain to you that your problem has nothing to do with the original thread.
If your problem is gone in “safe mode” it is most likely a VST plugin that misbehaves.
Find that plugin.
Thank you… I appreciate you taking the time to reply. I did email Cubase and was asked to reach out during business hours, and they would help virtually.
The problem is that I have not loaded any new VST’s in a very long time. And I have not updated any either. Take care sir.
To those who offered the suggestion that it could have been a VST, this was correct.
I saw a video on YouTube where the guy suggested taking 1/2 of the VST’s and putting them in another folder. If it loaded, then that 1/2 was good. I kept adding them but the other 1/2 loaded as well.
So, in all, all of my VST’s actually worked but for some reason, Cubase was stuck until after I did this.
It is still using a high number of resources still.
I had a similar issue today. Yesterday it was running fine, but today it was stuck on the infinite “Scanning VST 3 Plug-ins” pop up.
I think I figured it out though. My iLok wasn’t properly loaded because it was on a hub and I forgot to restart the power on the hub. Rather than warn me, Cubase 14 just hangs and doesn’t show any pop ups for this issue so it seems like a Cubase issue. All my other DAWs show pop ups that they can’t authorize.
Upon disconnecting and restarting Cubase 14 it loaded immediately. Steinberg, if you read this the issue appears to be that it doesn’t show what VST3s are being loaded and also it doesn’t throw pop ups for any errors or licensing issues when loading the VST3s so users aren’t aware why this is occurring. For users, replug in that iLook and double check any other authorization methods like Waves keys to be sure things are plugged in because otherwise C14 appears to infinitely hang instead.
Mine just did this with this new update, I think it’s .30… I can’t seem to recall the steps that I took to fix it in the past. It is currently taking me 30-45 minutes to start CB…which is draining my creative motivation…
Steinberg should clearly identify any issue that occurs during the loading process with a pop-up… and give a suggestion of what to do, such as removing or reinstalling a problematic VST that it identifies… this would not be a difficult function to program in Cubase. Also, when Cubase is stuck, it should have some pop-up with an option to skip/ignore the problem VST… OR SOMETHING…
Don’t just let it sit for 45 minutes without Cubase telling us the reason…
