Cubase scans plugins differently from other DAWs, and the Serum VST trips over two of its rules. The VST2 file has to sit in a folder Cubase actually watches, and a failed scan can land Serum on the blacklist.
Get the folder and the blacklist right and you’ll hear Serum presets within a few minutes. The steps below cover how to install Serum in Cubase plus the fixes that come up most.
Key Takeaways
- Serum 1 is VST2 only, and Cubase scans it from the VST2 plugins path.
- A failed scan blacklists the plugin. Deleting the blacklist file fixes it.
- Serum 2 ships as VST3 and installs to the Common Files VST3 folder.
- Use the Plugin Manager to rescan, not just the startup scan.
Serum and Cubase problems at a glance
| Problem | Most likely cause | Quick fix |
|---|---|---|
| Serum not in the plugin list | DLL in the wrong folder | Move it to the VST2 path Cubase scans |
| Serum blacklisted | Crash during the plugin test | Delete Vst2xBlacklist.xml and rescan |
| Serum 2 missing | VST3 folder confusion | Copy the .vst3 file to Common Files, VST3 |
| Serum loads but no sound | Instrument track not set up | Add an instrument track and route the MIDI input |
| Activation loop | Xfer account not signed in | Activate from the Serum menu |
1. What you need before installing Serum
Serum runs on Windows 10 and 11 and on macOS, including Apple Silicon. Cubase 12 and newer work fine with it, and so do older versions like Cubase 10 and 11.
You need an Xfer Records account for activation. Serum uses software licensing, so there’s no dongle and no USB key involved.
2. What Serum is and why producers use it
Serum is a wavetable synthesizer from Xfer Records. It became a standard tool for basses, leads, and sound design because the wavetable editor is visual and fast. You can draw waveforms and modulate nearly any parameter.
The factory library covers most starting points, and preset packs are easy to find for every genre. Serum works as a normal VST or AU instrument inside Cubase once the install is right.
3. How to install Serum in Cubase on Windows
Download the installer from Xfer Records or through Splice. Run it and choose the 64-bit option when the installer asks.
Pick the VST2 folder. The default path is Program Files, Steinberg, VSTPlugins. Cubase watches this folder by default, so the default install works without any extra setup.
Ignore the VST3 choice for Serum 1. Serum 1 has no VST3 version. If the installer offers a VST3 location, it still drops a .dll file there, and Cubase scans that folder for .vst3 files only.
Keep Serum 1 in the VST2 folder.
4. Install Serum 2 on Windows
Serum 2, released in 2025, is a VST3 plugin. It installs to Program Files, Common Files, VST3, which is the standard VST3 location Cubase scans automatically.
If Serum 2 doesn’t appear, check that the .vst3 file is directly inside the VST3 folder. Some installers nest it inside a subfolder, and Cubase misses it there. Copy the file into the main folder and rescan.
You can run Serum 1 and Serum 2 side by side. They show up as separate entries in the plugin list.
5. Install Serum on macOS
The macOS installer offers VST, VST3, and Audio Unit versions. Cubase supports all three formats, so install the AU version or the VST3 version and Cubase finds it.
AU plugins live in Library, Audio, Plug-Ins, Components. Cubase scans this folder when the AU support option is enabled in the plugin settings.
Apple Silicon Macs run Serum natively. There’s no Rosetta requirement for the plugin itself.
6. Make Cubase scan the right folder
Open Cubase, then Devices, Plug-in Manager. The manager lists every scanned plugin and shows the paths Cubase watches.
Under the paths section, confirm the VST2 path includes the folder with Serum_x64.dll. If you used the default install, it’s already there.
Click Rescan and wait for the scan to finish. Then search for Serum in the plugin list and tick the enable checkbox if it’s off.
7. Serum not showing up in Cubase
You installed Serum, rescanned, and the plugin list still has no Serum. This is the most common Cubase and Serum problem, and the causes are few.
Check the VST2 path. Cubase only scans the folders listed in the Plugin Manager. If Serum_x64.dll lives elsewhere, add that folder to the paths or move the file.
Check the enable flag. A scanned plugin can sit in the list with its enable box unticked. Find Serum under the list and tick it.
Check the file name. Cubase looks for Serum_x64.dll on Windows. A file renamed or copied as Serum.dll alone may not register.
Restart Cubase. Some installs register only on the next launch. Close Cubase completely and open it again before trying anything drastic.
Pro tip
When Serum vanishes after a crash, Cubase has blacklisted it. Close Cubase, open Run with Windows key plus R, type %APPDATA%\Steinberg, and delete the Vst2xBlacklist.xml file for your Cubase version. The next scan re-tests Serum from scratch.
8. The blacklist problem and fix
Cubase tests every plugin when it scans. A plugin that crashes or fails that test goes onto the blacklist, and Cubase never loads it again until you clear the list.
Delete the blacklist file. Close Cubase, then press Windows key plus R and type %APPDATA%\Steinberg. Open the folder for your Cubase version, delete Vst2xBlacklist.xml, then start Cubase and rescan.
Update Serum first. If Serum crashed during the test, an outdated build is the likely cause. Install the latest version from your Xfer account, then clear the blacklist.
Test Serum alone. Open a blank project, add Serum to an instrument track, and play a few notes. If it holds up, the blacklist was a one time failure.
9. Serum loads but makes no sound
Serum opens in the project, but pressing keys produces silence. The plugin is fine in most cases, and the track setup is the problem.
Use an instrument track. Add a new instrument track and choose Serum as the instrument. MIDI tracks alone don’t trigger instruments unless they’re routed to one.
Check the MIDI input. In the track inspector, confirm the MIDI input is your keyboard and the routing goes to Serum. A track with no input plays nothing.
Check the output. The instrument track must output to a working audio bus. Muted or unassigned outputs produce silence even when the plugin runs.
10. Activation problems
Serum shows the activation screen on every launch in Cubase. The license follows your Xfer account, and the fix takes a minute.
Sign in from the plugin. Open Serum and choose Sign In. Enter your Xfer Records credentials and the license activates.
Check the connection. First time activation needs internet. For offline studios, the Xfer site offers an offline activation file.
Keep Splice signed in. Rent to own licenses activate through the Splice app. If Serum asks to reactivate, Splice is likely signed out.
11. Serum presets and packs: where they live
Serum keeps presets in its own folder inside the plugin directory. On Windows that’s Program Files, Steinberg, VSTPlugins, Xfer Records, Serum, Presets by default.
Preset packs install by copying folders into the Presets directory. Packs with custom wavetables also drop files into the Wavetables folder beside it.
Cubase doesn’t manage Serum presets, so there’s no rescan after adding packs. Restart Serum or reopen the browser and the new folders appear.
How I verified these steps
These steps come from the Steinberg forums, the Xfer Records support pages, and the threads on r/cubase where these exact problems get solved daily. I checked the folder paths and the blacklist file name against Cubase 14 before writing this.
The blacklist fix is the one that surprises people most. It looks like the plugin is gone for good, and a single file deletion brings it back. It saved a session of mine on the Dell G5 more than once.
How to avoid Serum problems in Cubase
- Keep Serum 1 in the default Steinberg VSTPlugins folder and never move it.
- Update Serum before big Cubase updates, not after.
- Use the Plugin Manager for rescans instead of restarting Cubase repeatedly.
- Clear the blacklist file only after updating the plugin.
- On macOS, stick to one format, AU or VST3, to avoid double scanning.
Frequently asked questions
Why is my Serum not showing up in Cubase?
Serum 1 is VST2, so the .dll must sit in a folder listed in the Plugin Manager paths. Check the path, tick the enable box, and rescan. If it still hides, delete the blacklist file.
What is the Cubase blacklist?
It’s a list of plugins that failed Cubase’s scan test, stored in Vst2xBlacklist.xml. Deleting the file clears the list, and Cubase tests the plugins again on the next scan.
Is Serum VST3?
Serum 1 is VST2 only. Serum 2, released in 2025, is VST3. The version you own decides which folder the plugin belongs in.
Does Serum work with Cubase on Mac?
Yes. Cubase reads AU, VST, and VST3 on macOS, so the AU version of Serum works without extra setup. Enable AU support in the plugin settings if the plugin stays hidden.
How do I move my Serum presets to Cubase?
Presets follow the Serum folder, not the DAW. Copy the preset files into the Serum presets folder, and both Cubase and any other DAW see them on the next launch.
The bottom line
To install Serum in Cubase, two things matter. Keep the VST2 path correct for Serum 1, and keep the blacklist clear. Get those two right and Serum in Cubase works without drama.
Where to go next
If Serum misbehaves in other software, the fixes carry over. See how to install Serum in FL Studio, Serum not showing up in FL Studio, and where VST plugins install on Windows. For Cubase itself, Cubase common problems covers the rest, and our VST not showing up guide explains the general causes.
To install Serum in Cubase is the first step, and the rest of the series helps too. Can You Run Cubase on Linux? covers the setup, and FL Studio common problems plus DAW settings you should change round out the picture.
