If you're seeing errors when loading a Cubase project that certain plugins (like Virtual Mix Rack, Virtual Tape Machines, or Repeater) "could not be found," there's a good chance the issue relates to the difference between VST2 and VST3 plugin formats.
This issue can affect both Mac and Windows users but is especially common for Mac users on Apple Silicon systems due to additional factors like Rosetta compatibility and native plugin architecture.
✨ Common Symptoms
- Plugin errors on project load, even though plugins are installed
- Some instances of a plugin load fine while others show as missing
- Manually reloading the same plugin works, but it doesn’t recall saved settings
📂 What's Causing This?
1. VST2 vs. VST3 Format Mismatch
Cubase treats VST2 and VST3 versions of a plugin as entirely separate. If your original session used the VST2 version of a plugin and that format is no longer available, Cubase cannot auto-substitute the VST3 version.
This situation often occurs when:
- You updated Cubase to a newer version
- You reinstalled plugins but skipped the VST2 format
- You moved to a new computer and only installed VST3 versions
2. Apple Silicon (Mac) Specific Behavior
- Cubase running natively on Apple Silicon does not support VST2 plugins at all.
- VST2 plugins will only load if Cubase is launched in Rosetta (Intel) mode.
Also note:
VST2 plugins are not enabled by default in Cubase versions 12 and up. You may need to manually enable support: https://helpcenter.steinberg.de/hc/en-us/articles/22554401894162-Using-VST-2-Plug-ins-in-Cubase-14-Nuendo-14
3. Windows Users: VST2 May Be Missing or Disabled
Even on Windows, users can run into this issue if:
- The VST2 version wasn’t installed (either deselected during installation or removed later)
- VST2 plugin paths were not added in Cubase preferences
- Cubase's plugin manager is set to only scan for VST3 plugins
✅ How to Fix It
If You're on a Mac:
-
Try launching Cubase in Rosetta mode to enable VST2 compatibility
- Open the session again
- If plugins load, manually replace VST2 instances with VST3 versions
Keep in mind: plugin settings will not automatically carry over between VST2 and VST3 formats. You'll need to either manually copy settings or load a saved preset if available.
- Save the session
- You can now return to running Cubase natively with VST3-only plugins
Note: Intel Mac users do not need to use Rosetta mode. VST2 support should remain functional as long as the plugins are installed correctly and enabled in Cubase.
If You're on Windows:
- Reinstall the plugin and ensure both VST2 and VST3 versions are selected
- Open Cubase and check Plugin Manager > VST Plug-in Paths to verify the VST2 folder is being scanned
- Reopen your session and check if the missing plugins now appear
- Just like on Mac, you may need to manually replace the VST2 instances with VST3 versions and resave the session, being careful to copy any plugin settings over manually.
Again, plugin settings will not carry over automatically — manually copy them or use saved presets
🔍 How to Tell Which Version Was Used
Unfortunately, Cubase does not display whether an insert was using a VST2 or VST3 version once it's missing. Your best clues are:
- Whether the plugin shows up under "VST2" or "VST3" in Plugin Manager
- Whether it's available when manually re-inserting
- Session/project age: older sessions often used VST2 by default
🔧 Best Practices to Avoid This in the Future
- Always install both VST2 and VST3 versions when available
- When updating Cubase or reinstalling your system, double-check that legacy formats are supported and enabled
- Consider updating old sessions by manually converting all VST2 instances to VST3 before future-proofing the project
❓ Still having issues?
If you're still running into plugin errors after trying the steps above, 👉contact our support team. Please include:
- A screenshot (macOS/Windows) of the error message
- Your Cubase version
- Your OS and system type (Apple Silicon or Intel, Mac or Windows)
- A list of plugins not loading
We're happy to help!
Comments
Please sign in to leave a comment.