Installer fails, plugin doesn’t show up, DAW rescans for two minutes and finds nothing. If you install free plugins off sites like BPB with any regularity, you’ve eaten this at least once. The plugin is fine. The installer is the problem.
I’ve been through this cycle more times than I care to count, mostly with small freeware releases where the “installer” is a 5 MB exe bundled by a one-person dev who tested it on their own machine and called it done. VST3 is the modern standard, as the writeups on free plugins keep saying, but the VST3 install path on Windows 11 is also where things quietly break. Here are three fixes that actually moved the needle for me, roughly in the order I try them.
First, figure out what the installer is actually doing
Two shapes of download show up constantly. Either a bundled installer exe, or a bare VST3 file stuffed in a ZIP with no installer at all. The BPB download pages are pretty transparent about this now: Shatter Clip offers a 5 MB Windows installer and a 3 MB Windows VST3 with no installer, alongside a 14 MB Mac build. X-Audio’s FAULTLINE is a 6.5 MB download, VST3 on Windows, AU and VST3 on macOS.
That distinction matters for troubleshooting. An installer exe that fails is usually a permissions or path problem. A bare .vst3 file that “fails” is usually you putting it in the wrong folder. Dumping a .vst3 into Program Files\VstPlugins and expecting it to appear is the single most common self-inflicted wound here.
So before you click anything: is this an exe or a file? Look inside the ZIP. If you see a single file ending in .vst3, skip the rest of the installer drama and jump to fix number two.
Fix 1: Run the installer as administrator, then check where it landed
The boring fix that resolves most failed installers. Windows 11’s UAC will happily let a plugin installer launch, unpack halfway, and then fail to write its final files to C:\Program Files\Common Files\VST3 because it never asked for elevation properly. The window closes. You assume it worked. It didn’t.
Right-click the exe, run as administrator. Reboot the DAW fully (not just a project reload: close the whole app). Rescan.
The second half of that fix is confirming the install path. That folder, C:\Program Files\Common Files\VST3, is the default system VST3 location on Windows. A well-behaved installer drops files there and your DAW finds them without you touching a scan path. A badly behaved installer drops them in C:\Program Files\VstPlugins, or worse, somewhere in your user profile under a folder with the developer’s initials in the name. I’ve seen both.
If the plugin installed but isn’t showing up, search the machine for the .vst3 file. Once you know where it actually went, either move it to the system folder or add the folder to your DAW’s VST3 scan list. Nine times out of ten this alone brings the plugin back from the dead.
- Run installer as admin
- Full DAW restart, not just a project reload
- Locate the
.vst3file on disk and confirm the path - Point the DAW at it if it’s in a non-standard folder
Fix 2: Copy the bare VST3 file by hand and skip the installer completely
When a developer offers a “VST3, no installer” download, take it. Every time. This is the version that can’t fail because there’s no installer to fail. It’s also smaller, which tells you something about how much bloat the installer wrapper adds to a plugin that’s a couple of megabytes of DSP.
The process is dumb and reliable:
Unzip. Find the file ending in .vst3. Copy it into C:\Program Files\Common Files\VST3. That’s it. No admin prompt, no registry writes, no uninstaller to regret later.
A quick note on .vst3 files on Windows: even though it looks like a single file, it’s usually a bundle, a folder wearing a file extension. Don’t try to open it, don’t rename it, don’t extract anything from inside it. Just move it whole.
The trade-off: no installer means no Start menu entry and no automatic uninstall. To remove the plugin later, you delete the file. Which, honestly, is how it should work. The people who complain about abandoned plugins becoming liabilities as DAWs and OS versions move on are usually the same people who can’t find where the uninstaller put everything. Manual install keeps you honest about what’s on the machine.
Fix 3: When it’s not the installer at all, it’s the scan or the block
Sometimes the installer runs clean and the file is in the right place and the DAW still ignores it. Three culprits I’ve hit.
The DAW’s VST3 scan got stuck. Most DAWs cache their plugin list and only rescan on demand or when the cache is invalidated. If a previous scan crashed partway through, the plugin can get blacklisted. Every DAW does this differently: in most of them you can clear the plugin cache or force a full rescan in preferences. Do that before assuming the plugin is broken. A stuck scan is a scan problem, not a plugin problem, and blaming a working plugin for it wastes an afternoon.
Windows marked the file as blocked. Files downloaded from the internet get a “mark of the web” flag on Windows 11. Right-click the downloaded .vst3 or the installer, check Properties, and look for an “Unblock” checkbox at the bottom. Tick it, apply. This one’s easy to miss because the installer runs fine; it’s the plugin host that refuses to load the marked file.
The DAW is 32-bit only, or you’re trying to load a VST2 build into a VST3-only host. Less common now, but the format matters. VST3 is the standard; AU is the Mac equivalent; AAX is for Pro Tools. If you grabbed the wrong format out of a ZIP that has all three, it won’t load no matter what you do to the installer. Check the actual file extension against what your DAW wants.
The order I try things
- Is it an exe or a raw
.vst3? If raw, copy by hand into the system folder and restart the DAW. - If exe, run as administrator, then find where the file landed.
- If it’s in the right place and still missing, clear the DAW plugin cache and rescan.
- If it still won’t load, check Properties for the Unblock flag.
- If nothing works, verify you downloaded the right format and, if not, grab the no-installer version.
The pattern across every one of these is that the “installer failure” is almost never the plugin. It’s Windows permissions, a folder nobody agreed on, or a DAW cache holding a grudge. The plugin itself, the actual DSP code, is fine. Treat the install like you treat buffer size and driver setup: unglamorous, worth getting right once, and much easier the second time. Grab the no-installer build whenever a developer offers one, put the file where Windows expects it, and move on to the part that actually makes records.