Blacklisted Plugins - What's up?

i have also problems with iLok protected plugins, softube, eventide, psp (2425, but stompdelay not…), but not all, octavox and quadrovox didn’t get blacklisted.
i have 2 systems, one of them blacklist vst2.4 versions of arturia… the difference? one is win 10 home and a laptop (i7-9750h, 16gb, nvidia 1050) other is win 10 pro (i7-6700k, 32gb, 1060 6gb).
i have 2 iLok dongles (yes…) for both. i can’t really say when the problem started. the laptop is a month old, and the “workstation”, i installed win 10 pro (clean install).

not all iLok stuff gets blacklisted, but most of them. reactivation works, and no problems…

I reverted back to iLok 5.0.2

Well, waddayaknow, without changing or installing anything, the studio system, running C9.5, suddenly blacklistet Eventide (prev versions), all SoundToys and some PSP (both latest v) plugins.This obviously invalidates my previous test which pointed towards C10, and def. indicates that the culprit IS iLok.

So, where can I find the iLok betas?

j,

Steinberg?

i noticed that to, when i had win 7 pro and cubase 9.5 + 10, that cubase 9.5 suddenly blacklisted plugins. i didn’t install 9.5 on my fresh installation of win 10 pro. it seems an iLok thing. pretty annoying. but they are VST2, eventide for example, if you remove the whitelist file for vst2, it does not wait when starting up cubase, scanning vst2 plugins, because the vst2 plugins are in another xml file, and cubase does not see them as reactivated.
strangely enough this does not work for vst3 plugins…

Is there a way to bulk reactivate? When a whole suite gets blacklisted, takes a while to reactivate one by one.

Hi all, Vito from the Soundtoys Support team here. I did some testing to try to figure out an easy workaround for this problem. I can’t pinpoint an exact cause of the issue, but it does appear to be primarily dependent on the version of PACE / iLok you have installed.

It seems as though plugins that use iLok will get blacklisted when scanned in Cubase 10 if you have the latest iLok version 5.1.0 installed. They did not appear to get blacklisted when scanned while the previous iLok version 5.0.3 was installed.

As others have mentioned here, PACE is aware of this problem and has announced that this will be fixed in the next iLok update for version 5.1.1 which they’re trying to get out as soon as possible.

The Soundtoys installers ship with an iLok installer, and it’s usually not the latest version (since PACE issues updates more frequently). This is actually pretty helpful to us now, so here’s the new workaround I suggest:

\

  1. Reset Cubase 10’s blacklist so that it rescans all plugins again. This can be done by navigating to "C:\Users<username>\AppData\Roaming\Steinberg\Cubase 10_64" and then deleting the “Vst2xPlugin Blacklist Cubase.xml” file.
  • You can skip this step if you prefer to reactivate the plugins one-by-one in the VST Plug-In Manager.
  1. Uninstall PACE / iLok. Open the start menu and search for “Add or remove programs” and open up that application. Then search for “PACE License Support” and remove it.

  2. Reinstall the latest Soundtoys package, and choose to install PACE / iLok at the end.


    Now, you should have the latest version of Soundtoys and the previous version of PACE (version 5.0.3) installed, and the plugins should be successfully scanned when you open up Cubase. If you chose not to delete the blacklist file, then you should be able to reactivate them manually in the VST Plug-In Manager. This should also apply to other non-Soundtoys plugins with the same issue. Just make sure you do NOT update the iLok version until 5.1.1 is released.

I hope this information helps! Please let us know if you have any problems with this workaround.

I didn’t find one but sure would’ve appreciated that after the Soundtoys update.

FYI there is an update to the ilok software which should fix the blacklisting problem - fixes some other issues I was having too

Anybody tested this? I got my systems back to normal with info from SoundToys:

  • Uninstall iLok 5.1
  • Delete the Cubase blacklist xml
  • Install latest SoundToys bundle – and say yes to installing the iLok drivers, as these are the previous version (5.0x)

j,

I’ve tested it and it fixed the problem I was having (a subtle crash on exit in ucrtbase.dll)

it’s specifically listed a fix for the blacklisted plugs problem in the release notes - other fixes listed too

Confirmed. My Blacklist is now empty :slight_smile:

j,

For those of you who have re-activated some plugins… please remember to delete the Whitelist also before installing the newest iLok manager… or else you can’t know if the fix is working.

good point :slight_smile:

fixed
Fixed a Windows only problem where some DAWs could randomly blacklist protected VST plugins
fixed
Fixed a possible Windows only silent crash on quit that results in an unexpected exception in the event log

from iLok manager… it seems it causes the silent crash, mentioned in another thread, perhaps, or multiple instances of cubase.exe… do not know for sure, but it can be the case.

yes - fixes ucrtbase.dll error on quit - wavelab had this problem too :slight_smile:

Cheers, I just updated iLok License Manager from 5.0.3.2569 to that new version 5.1.1.2937 not had anything blacklisted by Cubase 10.0.50 (but I didn’t before either). All plugins working OK, including SoundToys.

iLok stuff now work. only on 2 systems it blacklist the vst2.4 versions of my arturia stuff. not a problem, cubase shows only the vst3 version, as before, and i use the vst3 versions. and it blacklist maschine 2/maschine 2 FX. strange. those i must use, because only vst2.4 64 bit. when reactived no problems.

but the iLok problems are gone, yeah!

I had Ilok 4, changed it to the latest Ilok 5 version.
The plugins that where blacklisted are still blacklisten (tested again).
No problem with the Ilok version.
The blacklisted plugins (maybe 7 pieces) i know they do not work.

The latest iLok software still causes problems for me. Back on iLok 5.0.2 for the 2nd time now.