hi, anyone any experience of synthmaster 3 going to blacklist in cubase 14/15 pro win 10 ?
standalone wont open either
thanks

 

Not had any problems with Synthmaster 3 in C15 on Win11. Might need to re-authorise?

 

Does your system conform to the requirements?
CPU: 2.0 Ghz, Intel SSE3 instruction set
RAM: 2 GB
Windows: Windows 7 and above
MacOSX: MacOSX 10.9 and above
For AAX: ProTools 11 and above

 

hi,i have AMD Phenom II X6 could that be the prob?

 

Hi @funkman, it shouldn't actually be due to your processor.

SynthMaster System Requirements

- CPU: 2.0 Ghz, Intel SSE3 instruction set
- RAM: 2 GB
- Windows: Windows 7 and above
- MacOSX: MacOSX 10.9 and above
- For AAX: ProTools 11 and above

AMD - Phenom II X6
- Six-core processor (Hexa-Core)
- Revision: E0
- L1 cache: 64 + 64 KiB per core (data + instructions), 2-way associative
- L2 cache: 512 KiB per core at processor clock speed, 16-way associative
- L3 cache: 6144 KiB at 2 GHz, shared, 48-way associative
- MMX, Extended 3DNow!, SSE, SSE2, SSE3, SSE4a, AMD64, Cool'n'Quiet 3.0, NX Bit, AMD-V, Turbo Core

1.) Delete / Uninstall:
C:\Program Files\KV331 Audio\SynthMaster

Registry (Regedit):
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\KV331Audio

Restart your PC

2.) Re-setting the Cubase plug-ins cache manually
https://acusticaudio.freshdesk.com/...re-setting-the-cubase-plug-ins-cache-manually

 

thanks i shall try that

 

Perhaps you have a second DAW to test whether SynthMaster works there.

 

dosent show up in fl studio 2025 synthmaster 2 is there but no 3.

 

I suspect you need to delete SynthMaster 2 first for it to show SynthMaster 3. I think that's where the conflict lies.

 

the username part of that path with % at start and end,dont put in % right?

 

1. Manually delete the Vst2xBlacklist Cubase (x86_64).xml file (to delete the blacklist)
2. Manually delete the Vst2xPlugins Cubase (x86_64).xml file (to force a complete plug-in to resca

i dont see these in that folder

only one that was there was Vst2xBlacklist Cubase.xml file

 

Spoiler: Source: Grok KI

You're on the right track, and what you're seeing is completely normal depending on your Cubase version and system.

Starting with **Cubase 12 (and especially Cubase 13/14), Steinberg changed the file names and structure a bit. Here's the current situation as of Cubase 13/14 (2024–2025):

Common locations and current file names
Windows C:\Users\YourName\AppData\Roaming\Steinberg\Cubase 13_64\ (or Cubase 12_64, Cubase 14_64, etc.)

The files you will usually find there now are:

• Vst2xBlacklist Cubase.xml ← this is the new name for the 32-bit blacklist (even on 64-bit systems)
• Vst2xBlacklist Cubase (x86_64).xml ← this one often no longer exists in newer versions
• Vst2xPlugins Cubase (x86_64).xml ← this one is gone/replaced in Cubase 12+

Instead, Cubase now mostly uses just:

• Vst2xBlacklist Cubase.xml ← the only blacklist file that still exists in most fresh installations
• The full plugin cache is now stored in Vst2xPluginInfos Cubase.xml (or` in a binary cache folder (not user-editable)

So what should you delete in 2025 to fully reset the VST2 scan/blacklist?
Just delete this one file (safe to do with Cubase closed):

C:\Users\YourName\AppData\Roaming\Steinberg\Cubase XX_64\Vst2xBlacklist Cubase.xml

That’s it in 95 % of cases nowadays.

If you want to be 100 % sure and force a complete rescan of all VST2 plugins (including forcing Cubase to rebuild everything), also delete or rename the entire folder:

C:\Users\YourName\AppData\Roaming\Steinberg\Cubase XX_64\VST PlugIn Cache\

(Cubase will recreate it on next start.)

macOS (for completeness)
~/Library/Preferences/Cubase 13_64/ → delete Vst2xBlacklist Cubase.xml (same idea)

Summary – what you should do right now

1. Close Cubase completely.
2. Go to C:\Users\YOURNAME\AppData\Roaming\Steinberg\Cubase 13_64 (or 14_64)
3. Delete the file you already found: Vst2xBlacklist Cubase.xml
4. (Optional but recommended for full reset) Delete the whole subfolder VST PlugIn Cache
5. Start Cubase again → it will rescan all VST2 plugins from scratch.

The old (x86_64) files you were looking for simply don’t exist anymore in current Cubase versions, so you’re good — just delete the one blacklist file you see and you’ve done exactly what the old instructions wanted.

 

thanks, where is subfolder vst plugincache? i dont see it inside roaming steinberg cubase14

 

Spoiler: Source: Grok KI

The VST plugin cache files for Cubase 14 (and recent versions) are no longer stored in the old location you’re looking at.

Starting with Cubase 13/14, Steinberg moved the plugin cache (the files like VstPlugInCache*.xml, VST3Cache*.xml, etc.) to a new location:

Windows location for Cubase 14 (64-bit):

C:\Users\YourUsername\AppData\Local\Steinberg\Cubase 14_64\Cache\

Full typical path:

text

C:\Users\[Your Windows Username]\AppData\Local\Steinberg\Cubase 14_64\Cache


Inside that Cache folder you’ll usually see files like:

• VstPlugInCache.xml
• VST3Cache.xml
• ComponentCache.xml
• etc.

Quick way to jump there:

1. Press Win + R
2. Type (or paste):
   text
   
   %localappdata%\Steinberg\Cubase 14_64\Cache
   
   
   
3. Press Enter → it opens the folder directly.

If you still don’t see the folder:

• Make sure hidden files/folders are visible (AppData and Local are hidden by default).
• Confirm you’re running the 64-bit version of Cubase 14 (almost everyone is). There is no separate 32-bit version anymore, but the folder is still named Cubase 14_64.

That’s where the current plugin cache lives. If you ever need to reset/refresh your plugin list, just delete (or rename) the files in that Cache folder and restart Cubase — it will rescan everything from scratch.

 

ok synthmaster 3 reinstalled after i deleted it and synthmaster 2
synthmaster 3 comming up in blocklist

 

Many issues reported with that older processor and the newer soft synth. Like buffering issues, stuttering etc...
Also there have been reports of that synth not running due to the fact it can't find it's license file.

 

Reactivating Plug-ins from the Blocklist

You can reactivate 64-bit plug-ins that are on the blocklist.

Procedure

1. On the Blocklist tab, select the plug-ins that you want to reactivate.
   Note
   You cannot reactivate 32-bit plug-ins because they are not supported.
   
   
2. Click Reactivate.

Result
Cubase rescans the plug-in and removes it from the blocklist.

www.steinberg.help/r/cubase-ai/13.0/en/cubase_nuendo/topics/installing_and_managing_plugins/installing_and_managing_plugins_plug-in_manager_reactivating_from_blacklist_t.html

 

tried that before,comes up as failed to reactivate

 

If you have a purchased version, please contact the manufacturer: www.kv331audio.com/contactus.aspx

 

i have been on to them via facebook group page they havent got a solution yet unfort.