Hi.
I’ve installed Cubase 13 on a shared Mac Pro. Other users have installed plugins with an iLok authorisation to use with other DAWs. The authorisation is on their physical iLok dongles, to which I don’t have access.
Now, when loading Cubase, I get several authorisation/activation screens for the various plugins that I don’t have authorisation for. Is there a way to prevent these screen from appearing every time I load Cubase without uninstalling the plugins?
Thanks,
Tom. 
Try to remove them from the current collection as a first step.
Brilliant thank you st10ss.
By current collection, do you mean the plugins installed on the computer? It’s a shared computer where we all use the same user account, so there will be other users who use other DAWS with an iLok for the plugins in question. I can’t really uninstall, but as the other DAWs are Pro Tools and Logic, I guess nobody needs the VST version so could uninstall that. Not sure if that’s possible…?
Sorry, is that what you meant?
Thanks,
T
This is your problem. Set up different accounts - if possible.
No. The collection is the list that is active in Cubase.
Ah cool! Thanks. Do you know how to remove them from the collection?
You would have to create a new collection without the plugs and make that active instead of the default.
I’m not convinced it will make any difference though. Pretty sure the startup scan is all plugs on system not only the active collection.
The startup scan happens only if something changed related to plugins.
How can Cubase know if something has changed related to plugins if not by scanning??
Well OP can let us know how it goes…my money’s on it won’t help but I’m happy to be proved wrong if it helps them with their issue.
Timestamps from the folders.
I made a collection with just one plug active, re-opened Cubase to check it was still the active collection (all good) and then re-opened with ilok unplugged.
As I thought…Cubase scans all plugins and causes a barrage of ilok authentication errors.
Brilliant. OK thanks for the answers guys. I will give it a go and see what happens! If not that, maybe another solution will present itself in the process. Thanks for the knowledge!
I would give it a go anyway as you’re on Mac and it’s possibly different, but on my PC it didn’t solve the issue so I wouldn’t get your hopes up.