You ran the Serum 2 installer, opened your DAW, and the plugin list is pretending nothing happened. No Xfer folder anywhere. No Serum 2. At Monosounds we get this exact email weekly, and the subject line is always a variation on “serum 2 not showing up”.
Here’s the truth of it: the install almost always worked. Your DAW is simply searching the wrong folder, scanning the wrong format, or leaning on a stale plugin cache.
Let’s sort it out. Two checks that apply everywhere come first, then step-by-step fixes for Ableton, FL Studio, Logic, Studio One, and Bitwig.
Serum 2 Not Showing Up: Run These Two Checks First
Check 1: is the file actually on disk? Serum 2 installs as its own plugin, a file named Serum2.vst3. It does not overwrite your old Serum. Windows users should look in C:Program FilesCommon FilesVST3. Mac users, check /Library/Audio/Plug-Ins/VST3 and /Library/Audio/Plug-Ins/Components. No file there? Run the installer again and tick every format box this time around.
Check 2: can your DAW even read that format? Serum 2 only ships as VST3, AU, and AAX. A VST2 build does not exist. That single fact accounts for roughly half the missing-plugin emails I answer. An older DAW setup scanning only VST2 folders will happily show Serum 1 forever and never find Serum 2.
Logic takes AU only. Pro Tools takes AAX only. Ableton, FL Studio, Studio One, and Bitwig all want the VST3 (Ableton and Studio One on Mac can also grab the AU). Curious what else changed between versions? My Serum 1 vs Serum 2 comparison has the details, but the compressed answer is: new plugin, new file, new scan required.
Where Serum 2 Actually Installs
Before hitting any rescan button, verify the file lives in one of these folders. They’re the defaults the Xfer installer writes to, and every major DAW scans them out of the box.
| 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 |
A warning earned the hard way: never relocate Serum2.vst3 into some custom plugin folder. VST3 is built around the system location. If you dragged it elsewhere to “organize” things, return it to the default path and run a rescan.
Ableton Live: Enable VST3 Folders, Then Deep Rescan
Ableton produces more serum 2 not showing up reports than anything else I see, and the cause is nearly always the same pair of switches.
- Open Settings (called Preferences in older versions) and head to the Plug-Ins tab.
- Switch on Use VST3 Plug-In System Folders. Mac users who also want the AU build should enable Use Audio Units.
- Hold Alt (Windows) or Option (Mac) while clicking Rescan. The modifier forces a genuine deep rescan rather than the quick pass, and the quick pass has a habit of skipping anything that failed a scan once.
Version check: Live gained VST3 support in 10.1. Anyone on Live 10.0 or older can rescan all day and get nowhere, because there’s no VST2 Serum 2 to fall back on. Updating Live comes first.
FL Studio: Plugin Manager Scan
- Open Options > Manage plugins.
- Check that
C:Program FilesCommon FilesVST3shows up in the search paths. If it doesn’t, add it via the folder button. - Turn on Verify plugins and hit Find installed plugins.
- Once the scan completes, locate Serum 2 under Installed > Generators > VST3 and click the star icon so it appears in your Add menu and plugin picker.
If the scanner finds the file but marks it failed, restart FL Studio and run one more scan with Verify plugins still enabled. First-run verification can time out on big plugins, and Serum 2 loading its factory content for the first time is genuinely heavy work.
Logic Pro: Reset the AU Cache
Logic plays stricter than the rest, because macOS insists on validating every Audio Unit before it touches a session. When serum 2 is not showing up in Logic, blame a stale validation result first.
- Go to Logic Pro > Settings > Plug-in Manager.
- Type “Serum” into the search box. If Serum 2 appears as failed or disabled, select it and press Reset & Rescan Selection, keeping an eye on the validation result at the bottom.
- If Serum 2 isn’t listed at all, quit Logic and check that
Serum2.componentsits in/Library/Audio/Plug-Ins/Components. Missing? Re-run the Xfer installer with the AU box ticked and relaunch Logic; it picks up new components at startup.
Still nothing? Reboot the Mac. macOS keeps AU validation cached at the system level, and a restart flushes more of it than you’d think. Sounds like superstition, and yet it has saved at least a dozen setups I’ve personally helped fix.
Studio One and Bitwig
Studio One: open Studio One > Options (Preferences on Mac), then Locations > VST Plug-Ins, and click Reset Blocklist. Studio One silently blocklists any plugin that misbehaved during scanning and never mentions it to you. Confirm “Scan at startup” is on, restart Studio One, and let it scan.
Bitwig: head to Dashboard > Settings > Locations and make sure your plugin locations cover the standard VST3 folder. Then trigger a rescan under Settings > Plug-ins. Bitwig sandboxes plugins by default, so a scan crash won’t bring the DAW down, but it can quietly flag a plugin as bad. Rescanning clears the flag.
Apple Silicon and Rosetta
Serum 2 ships as a universal binary and runs natively on M-series Macs. The trap is your DAW’s mode, not the plugin itself.
A DAW launched under Rosetta builds its plugin list from Intel-compatible plugins only. Flip the DAW between native and Rosetta and that list gets rebuilt, which explains why a plugin can seemingly “disappear” after you toggle that checkbox in Finder’s Get Info window.
My recommendation: run the DAW natively. Serum 2 is perfectly happy there, and native mode gives you real CPU headroom, which starts to matter once granular and spectral patches begin stacking up. If projects choke after the plugin finally appears, that’s a different fight, and I documented my Serum 2 CPU optimization settings for exactly that scenario.
License and Activation Basics
People confuse two separate problems: a plugin that never appears, and one that appears but isn’t activated.
If Serum 2 loads and asks for a serial, sign into your Xfer Records account, grab the serial, and paste it in. Serum 2 came as a free upgrade for Serum 1 owners, so your existing Serum serial already covers it. On the Splice rent-to-own plan, the Splice desktop app owns installation and activation, so open Splice, find your plugins, and reinstall from there. Anything stranger than that, and Xfer’s support page is genuinely quick to respond.
After it loads and activates, put the install through a real workout. Our free pack of 250+ Serum 2 presets spans basses, leads, keys, plucks, and 808s; if every one of those loads cleanly, your install is in good shape. Then read my guide on how to install Serum 2 presets so the pack lands in the correct folder on the first attempt.
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” got left off in Settings > Plug-Ins. Enable it, then hold Alt or Option while clicking Rescan to force the deep version. And verify you’re running Live 10.1 or newer, because earlier versions can’t load VST3 at all.
Does Serum 2 have a VST2 version?
No. VST3, AU, and AAX are the only formats Serum 2 ships in. A workflow that depends on VST2 needs a DAW update, not a Serum fix. Every current release of the major DAWs handles VST3 without complaint.
Why does Serum 1 show up but Serum 2 doesn’t?
Because they’re separate plugins with separate files. Serum 1 may be a VST2 living in a folder your DAW does scan, while Serum2.vst3 sits in the system VST3 folder your DAW skips. Turn on VST3 scanning, aim your DAW at the default VST3 path, and rescan.
Serum 2 shows up but crashes the scan. Now what?
Clear the DAW’s blocklist first and scan again, since a single bad scan can blacklist a plugin permanently. If failures continue, download the newest installer (2.1.x as of this writing) from your Xfer account and reinstall. On Windows, GPU driver problems occasionally break the UI mid-validation; a graphics driver update has resolved that for several producers I’ve worked with.
Get It Loaded, Then Get to Work
Nearly every serum 2 not showing up case boils down to the same three suspects: wrong folder, wrong format, stale scan. Confirm the file exists, confirm your DAW reads VST3 or AU, force a deep rescan. That sequence sorts it for almost everyone, usually inside five minutes.
Once you’re in, skip the init patch. Take our free 250+ Serum 2 presets, no strings attached, and dissect them to learn how they’re put together. For a broader map of what exists out there, my Serum 2 preset guide for electronic producers is the long-form 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 →
