You installed Serum 2, opened your DAW, and the plugin list acts like nothing happened. No Xfer folder. No Serum 2 anywhere. We get this exact email at Monosounds every week, and the subject line is always some version of “serum 2 not showing up”.
Here’s the honest part: in almost every case the install actually worked. Your DAW is just looking in the wrong folder, scanning the wrong format, or trusting a stale plugin cache.
So let’s fix it. Two universal checks first, then the exact steps for Ableton, FL Studio, Logic, Studio One, and Bitwig.
Serum 2 Not Showing Up: Run These Two Checks First
Check 1: does the file actually exist? Serum 2 installs as a separate plugin called Serum2.vst3. It does not replace your old Serum. On Windows, look in C:Program FilesCommon FilesVST3. On Mac, check /Library/Audio/Plug-Ins/VST3 and /Library/Audio/Plug-Ins/Components. If the file isn’t there, re-run the installer and tick every format box this time.
Check 2: does your DAW read that format? Serum 2 ships as VST3, AU, and AAX only. There is no VST2 build. That one fact explains about half of the missing-plugin emails I get. People run an older DAW setup that only scans VST2 folders, so Serum 1 shows up and Serum 2 never will.
Logic loads AU only. Pro Tools loads AAX only. Ableton, FL Studio, Studio One, and Bitwig all want the VST3 (on Mac, Ableton and Studio One can use the AU too). If you’re wondering what else changed between versions, my Serum 1 vs Serum 2 comparison covers it, but the short answer is: new plugin, new file, new scan needed.
Where Serum 2 Actually Installs
Before you touch any rescan button, confirm the file sits in one of these folders. These are the defaults the Xfer installer uses, and every major DAW scans them automatically.
| Format | Windows | macOS |
|---|---|---|
| VST3 | C:Program FilesCommon FilesVST3Serum2.vst3 |
/Library/Audio/Plug-Ins/VST3/Serum2.vst3 |
| AU | Not available | /Library/Audio/Plug-Ins/Components/Serum2.component |
| AAX | C:Program FilesCommon FilesAvidAudioPlug-Ins |
/Library/Application Support/Avid/Audio/Plug-Ins |
| VST2 | Does not exist | Does not exist |
One warning from experience: don’t move Serum2.vst3 into a custom plugin folder. VST3 is designed to live in the system location. If you dragged it somewhere else to “organize” your plugins, put it back in the default path and rescan.
Ableton Live: Enable VST3 Folders, Then Deep Rescan
Ableton is the most common serum 2 not showing up report I see, and it’s almost always the same two switches.
- Open Settings (Preferences on older versions) and go to the Plug-Ins tab.
- Turn on Use VST3 Plug-In System Folders. On Mac, also enable Use Audio Units if you want the AU version available.
- Hold Alt (Windows) or Option (Mac) and click Rescan. The modifier key forces a full deep rescan instead of the quick one, and the quick one loves to skip plugins that failed once before.
Version check: VST3 support arrived in Live 10.1. If you’re on Live 10.0 or older, no amount of rescanning will help, because there’s no VST2 build of Serum 2 to fall back on. You’d need to update Live first.
FL Studio: Plugin Manager Scan
- Go to Options > Manage plugins.
- Confirm
C:Program FilesCommon FilesVST3appears in the search paths list. If not, add it with the folder button. - Enable Verify plugins, then click Find installed plugins.
- After the scan, find Serum 2 under Installed > Generators > VST3 and click the star icon so it shows up in your Add menu and plugin picker.
If the scan sees the file but flags it as failed, restart FL Studio and scan once more with Verify plugins still on. First-run verification can time out on heavyweight plugins, and Serum 2 initializing its factory content is not a small job.
Logic Pro: Reset the AU Cache
Logic is stricter than the others because macOS validates every Audio Unit before letting it near your session. When serum 2 is not showing up in Logic, a stale validation result is usually the culprit.
- Open Logic Pro > Settings > Plug-in Manager.
- Type “Serum” in the search field. If Serum 2 is listed as failed or disabled, select it and click Reset & Rescan Selection. Watch the validation result at the bottom.
- If Serum 2 isn’t in the list at all, quit Logic and confirm
Serum2.componentexists in/Library/Audio/Plug-Ins/Components. If it’s missing, re-run the Xfer installer with the AU box ticked, then relaunch Logic. It scans new components at startup.
Still stuck? Restart the Mac. macOS caches AU validation at the system level, and a reboot clears more of it than people expect. It feels like superstition, but it has rescued at least a dozen setups I’ve helped with.
Studio One and Bitwig
Studio One: go to Studio One > Options (Preferences on Mac), then Locations > VST Plug-Ins. Click Reset Blocklist. Studio One quietly blocklists any plugin that misbehaved during a scan, and it never asks you about it. Make sure “Scan at startup” is enabled, then restart Studio One and let the scan run.
Bitwig: open Dashboard > Settings > Locations and check that your plugin locations include the standard VST3 folder. Then go to Settings > Plug-ins and trigger a rescan. Bitwig sandboxes plugins by default, so a crash during scanning won’t take the DAW down, but it can silently mark a plugin as bad. The rescan clears that flag.
Apple Silicon and Rosetta
Serum 2 is a universal binary, so it runs natively on M-series Macs. The catch is your DAW’s mode, not the plugin.
If your DAW launches under Rosetta, it builds its plugin list from Intel-compatible plugins. Switch the DAW to native mode (or back) and the list gets rebuilt, which is why a plugin can “disappear” after you change that checkbox in Finder’s Get Info window.
My advice: run your DAW natively. Serum 2 is happy there, and native mode buys you real CPU headroom, which matters once you start stacking granular and spectral patches. If your projects choke after the plugin finally loads, that’s a separate battle, and I wrote up my Serum 2 CPU optimization settings for exactly that.
License and Activation Basics
Two things people mix up: a plugin that doesn’t appear, and a plugin that appears but isn’t activated. Different problems.
If Serum 2 loads but asks for a serial, log into your Xfer Records account, copy the serial, and paste it into the plugin. Serum 2 was a free upgrade for Serum 1 owners, so your existing Serum serial covers it. If you’re on the Splice rent-to-own plan, the Splice desktop app handles installation and activation, so open Splice, head to your plugins, and reinstall from there. For anything weirder, Xfer’s support page is genuinely responsive.
Once it loads and activates, stress-test the install with real patches. Our free pack of 250+ Serum 2 presets covers basses, leads, keys, plucks, and 808s, and if all of those load cleanly, your install is healthy. Then follow my guide on how to install Serum 2 presets so the pack lands in the right folder on the first try.
FAQ: Serum 2 Missing From the Plugin List
Why is Serum 2 not showing up in Ableton after install?
Nine times out of ten, “Use VST3 Plug-In System Folders” is switched off in Settings > Plug-Ins. Turn it on, then hold Alt or Option and click Rescan for a deep rescan. Also confirm you’re on Live 10.1 or newer, since older versions can’t load VST3 at all.
Does Serum 2 have a VST2 version?
No. Serum 2 ships as VST3, AU, and AAX only. If your workflow depends on VST2, that’s a DAW update conversation, not a Serum problem. Every current version of the major DAWs handles VST3 fine.
Why does Serum 1 show up but Serum 2 doesn’t?
They’re separate plugins with separate files. Serum 1 might be a VST2 sitting in a folder your DAW scans, while Serum2.vst3 sits in the system VST3 folder your DAW ignores. Enable VST3 scanning, point your DAW at the default VST3 path, and rescan.
Serum 2 shows up but crashes the scan. Now what?
First, clear your DAW’s blocklist and scan again, since one bad scan can blacklist it permanently. If it keeps failing, re-download the latest installer (2.1.x as of this writing) from your Xfer account and reinstall. On Windows, GPU driver issues occasionally break the UI during validation; updating your graphics driver has fixed that for several producers I’ve worked with.
Get It Loaded, Then Get to Work
Almost every serum 2 not showing up case comes down to the same trio: wrong folder, wrong format, stale scan. Check the file exists, check your DAW reads VST3 or AU, force a deep rescan. That sequence fixes it for nearly everyone, usually in under five minutes.
And once you’re in, don’t start from an init patch. Grab our free 250+ Serum 2 presets, no strings attached, and tear the patches apart to see how they’re built. If you want a wider map of what’s out there, my Serum 2 preset guide for electronic producers is the long version.
I run Monosounds.studio and make the packs myself. Ten-plus years of producing, 97+ releases, 16,000+ downloads. Every Serum 2 preset we ship passes a CPU check on a mid-range laptop and gets used in a real track before release. If it does not survive a mix, it does not go in the pack.
More about Maxim & the studio →
