Cubase 13 and 14 block list

bill127
bill127 Member Posts: 6 Newcomer

I had a power supply issue with my laptop which is now resolved, but ever since, about 30 Native instruments VSTs have been added to the block list in Cubase 13, and now in Cubase 14 including Kontakt 7. Kontakt 5 and Kontakt still work just fine. I have deleted and reinstalled Cubase and deleted and reinstalled Kontakt 7. No joy. I have also tried downloading Kontakt 8 player. this went straight to the block list as well. Any suggestions? i can't justify buying Komplete 15 when half of Komplete 14 isn't working….

Answers

  • Uwe303
    Uwe303 Moderator Posts: 4,135 mod

    Hello,

    does it block the vst3 versions, can you post some pics of the vst plugin manager?

  • bill127
    bill127 Member Posts: 6 Newcomer

    Thanks for getting back to me! screenshot attached - it is the VST3 versions that are being blocked.

    I have a raft of other plugins (Arturia, EWQL, Roland etc) and they are all ok. about half the NI plug-ins are also fine which is puzzling.

  • PK The DJ
    PK The DJ Member Posts: 2,044 Expert

    Surely for Windows they should all be backslashes i.e. C:\Program Files\Common Files\VST3\

  • bill127
    bill127 Member Posts: 6 Newcomer

    I will try re-pathing one of them, but this is pathing is as was set up when I installed the plug-ins, ie Native access selected the path and I haven't amended it manually.

  • PK The DJ
    PK The DJ Member Posts: 2,044 Expert

    For comparison, my Cubase plugin list. All NI plugins active.

  • Uwe303
    Uwe303 Moderator Posts: 4,135 mod
    edited November 2024

    On my cubase 14 pro all native plugins are also active and working, also on the standard folder for vst3 plugins. Can you try the stuff from the last post here?

  • bill127
    bill127 Member Posts: 6 Newcomer

    No joy, I'm afraid. I renamed the VST3 cache to force Cubase to regenerate it, but all that happened is that I have lost all my VST3 instruments. rescanning inside the plugin manager doesn't find them either. I am quite perplexed. Starting Cubase with the VST cache renamed did force Cubase to create a new folder "Cubase pro VST3 Cache".

  • PK The DJ
    PK The DJ Member Posts: 2,044 Expert

    The cache? If you mean you changed the VST3 directory name, I'm not surprised it didn't work. The path has to be named correctly as it's a system setting/default install path.

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,147 mod
    edited November 2024

    Go to:

    C:\Users\your_user_name\AppData\Roaming\Steinberg\Cubase version_number\Cubase Pro VST3 Cache

    and delete the .xml file named "vst3blacklist"

    Open Cubase and check (maybe it needs a re-scan too)

    Note: in case you have multiple Cubase folders there (at C:\Users\your_user_name\AppData\Roaming\Steinberg\), check them all and delete the above .xml file from all folders.

  • bill127
    bill127 Member Posts: 6 Newcomer

    Thanks for the suggestion Sunborn, and I tried this, deleting all the blocklist xml's back to Cubase 9.5. This did force Cubase to re-index all the VST3 plugins from scratch on launching, however it has jsur added them all back in to a new block list - see below.

  • bill127
    bill127 Member Posts: 6 Newcomer

    I have also tried re-activating a blocked VST3 file. I get a System32 \KERNELBASE.dll unstable error, see below;

  • PK The DJ
    PK The DJ Member Posts: 2,044 Expert

    I mentioned earlier about your use of forward slashes rather than the normal Windows forward slashes - now I notice in that error message it mentions //dssr-gla-do01/redirect$/ and so on.

    That looks non standard also…

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,147 mod

    Some things are weird in your system, that's for sure and the most weird one is what PK The DJ mentioned above…

    "//dssr-gla-do01/redirect$/"

    This indicates some kind of network address which is, to say it simple, a very wrong way to deal with "key" Windows features. It look like that, at least part of your system is on a different computer (or on a network drive)?, i can't explain it better…

    It is also very possible that your kernelbase.dll is faulty, or some older version, so please execute the sfc/scannow command to replace corrupt files.

    …and it's getting weirder… For 64-bit users, the KernelBase.dll is at C:\Windows\SysWOW64 and not at C:\Windows\System 32!! Of course there is also a version of the files there, but it is the 32-bit version.

    Cubase is a 64-bit application and it has drop all support to 32-bit VST plugins. So, i am pretty sure that you have installed one or more 32-bit VST plugins and those are causing the error!

    In any case, we need a lot more info about your system and its structure (however be aware that this is not the purpose of this forum, because extensive system damages require a technician in your place and not speculations on the internet), but anyway, a very good start will be to check and update everything (Windows Update, drivers, etc etc) in your system,

Back To Top