The Client’s Challenge
A long-term client, a talented composer, was in the final stages of a critical studio upgrade. We had successfully migrated her entire workflow from a trusted, older music PC running Cubase 7.5 to a powerful new machine with the latest Cubase 15. Everything, from her audio interface to her beloved Native Instruments Kontakt libraries, had transitioned with surprising grace.
Then, we hit a wall. When loading her existing projects, one of the cornerstones of her orchestral template, the Vienna Symphonic Library (VSL), fell silent. The plugins loaded, but the instruments were empty, the presets gone. The prospect of manually rebuilding every single VSL instance across her entire back catalogue was, to put it mildly, a daunting and creatively crippling scenario.
The Investigation: A Tale of Two Plugin Formats
My initial suspicion was a simple library path issue. Often, when moving computers, you just need to tell the software where its sound files now live. We had copied the 120GB library across, but the new Vienna Assistant software refused to recognise it, forcing a complete re-download. This was frustrating, but it revealed the first clue: the new software used a completely different content format than the old one.
This led me to the root cause, a classic architectural conflict between old and new standards.
Contextual Conflict: VST2 vs. VST3
Think of plugin formats like different types of video files—an old VHS tape versus a modern Blu-ray. They both store a film, but you need the right player for each.
- The Old Project: Used the legacy
Vienna Instrumentplugin, a VST2 file. This is the ‘VHS player’. - The New Installation: Installed the modern
Vienna Instrument Pro, a VST3 file. This is the ‘Blu-ray player’.
Unlike Kontakt, which cleverly managed to automatically upgrade its VST2 instances in the project to the new VST3 version, VSL did not. Cubase opened the project, looked for the old ‘VHS player’, couldn’t find it, and so the instrument slot remained empty.
The solution seemed simple: install the old VST2 plugin. However, this revealed a second, more subtle hurdle. To encourage developers and users to adopt the more modern and efficient VST3 format, Steinberg made a design choice in Cubase 15: by default, it hides all VST2 plugins from view. The ‘VHS player’ was in the building, but Cubase had tucked it away in a back room, pretending it wasn’t there.
The Fix: Enabling Legacy Access
The primary goal was to make Cubase 15 acknowledge and load the older VST2 plugin, ensuring backward compatibility for the client’s projects. Here is the procedure we followed:
Source the Legacy Plugin
We navigated to the Vienna Symphonic Library website. Buried within the user support area, we found the ‘Legacy Downloads’ section and retrieved the installer for the original VST2 Vienna Instrument plugin. We then installed this on the new PC.
Access the Plugin Manager
Inside Cubase 15, we went to Studio > VST Plug-in Manager. At first glance, there is no obvious way to manage VST2 visibility.
Reveal the VST2 Path Settings
This is the crucial, easily missed step. In the bottom-left of the Plug-in Manager window, there is a small gear icon for settings. Clicking this opens the settings panel. Within this panel, we located the list of VST2 Plug-in Paths.
Re-Activate and Rescan
We ensured the default VST2 path was active and triggered a full rescan of all plugins. After a moment, the legacy Vienna Instrument (VST2) appeared in the plugin list, and more importantly, it was now available to the Cubase project, successfully loading into the instrument slots where it had previously been missing.
Additional Reflections
A Lingering Mystery: The Missing Content
While we successfully made Cubase ‘see’ the old plugin, a new problem emerged. The plugin now loaded, but it still couldn’t find its sound library content, displaying an empty preset browser. I used VSL’s dedicated ‘Directory Manager’ tool to point the plugin to the correct location on the SSD, but to no avail. The connection between the legacy plugin and its library data remains broken.
This is not uncommon in these situations. My next step will be to perform a methodical, clean re-installation of only the legacy components. By isolating the installation process, we can often resolve these stubborn pathing and permission conflicts. The investigation continues.
A Note for Composers on Upgrading
This case is a potent reminder for any composer or producer planning a similar upgrade. The industry-wide transition from VST2 to VST3 is a positive step, but it can create these legacy hurdles. If you rely on older plugins, be prepared to investigate how your DAW handles VST2 visibility. It’s often a hidden setting, not a bug, and knowing where to look can be the difference between a smooth transition and days of frustrating downtime.
If you are seeking professional help with Cubase VST2 plugins not showing after a system migration or update, one-on-one remote support services are available from Audio Support.
Not sure it’s the same problem? Ask a question first
