If a VST plug-in is missing in Sound Forge Pro 2026, start at Options → Preferences → VST Effects. Confirm the folder that contains the plug-in is listed, confirm the plug-in’s checkbox is enabled, then click Refresh. After the scan, open View → Plug-In Manager and search under All before assuming the install failed.
That is the current Boris FX workflow. Sound Forge’s 2026 help documents Add path, Edit path, Remove path, per-plug-in enable checkboxes, a Generic VST editor fallback and Refresh. It also documents a Plug-In Manager that can filter by vendor, category, VST version and 32/64-bit type. This guide follows those controls rather than Sony-era cache tricks.
Do not reinstall Sound Forge first. A missing effect is usually a format, path, scan, list-filter or hidden-state problem. Work through these seven checks in order and stop when the plug-in appears.
Before you start: identify what is missing
- VST effect: EQ, compressor, reverb, restoration tool or meter. Sound Forge 2026 officially supports third-party VST and DirectX effects.
- VST instrument: synth, sampler or drum instrument that expects MIDI. Sound Forge is a single-file audio editor and effect host, not a MIDI instrument DAW; do not expect a VSTi workflow.
- Standalone application: an installer may provide an app without installing a VST build. A standalone RX-style editor or AAX-only plug-in will not appear in a VST effects list.
Write down the exact product name, version, format and architecture shown by its installer. “The app is installed” does not prove that its 64-bit VST3 effect was installed.
Fix 1: Install a format Sound Forge can host
Rerun the plug-in manufacturer’s installer and select a 64-bit VST3 effect when that option exists. Current Sound Forge runs on 64-bit Windows, so the matching 64-bit plug-in is the least fragile choice. Don’t install only AAX, Audio Unit or a standalone build and expect it to appear in Sound Forge.
The Plug-In Manager’s By Type view separates plug-ins by VST version and 32/64-bit version. Use that view to see what Sound Forge actually scanned; do not infer architecture from a product name. If only an obsolete 32-bit build exists, check vendor support before adding a third-party bridge. A bridge adds another failure layer and is not the first fix for a current host.
If you installed an instrument, render it in a DAW and open the resulting audio in Sound Forge. The current Sound Forge effects help describes VST effects, not a MIDI/VSTi instrument rack.
Fix 2: Find the actual VST file and folder
For a normal 64-bit VST3 install on Windows, check:
C:\Program Files\Common Files\VST3
That is the standard global VST3 location in Steinberg’s VST3 developer specification. Steinberg also defines a per-user location at %LOCALAPPDATA%\Programs\Common\VST3 and a 32-bit global location at C:\Program Files (x86)\Common Files\VST3. Current 64-bit Sound Forge users should normally install the vendor’s 64-bit build rather than point the host at a 32-bit binary. VST3 products commonly appear as a .vst3 bundle, often inside a manufacturer subfolder.
VST2 has no single required location. Common 64-bit paths include:
C:\Program Files\VSTPluginsC:\Program Files\Steinberg\VSTPluginsC:\Program Files\Common Files\VST2
Steinberg’s Windows plug-in guidance recommends using the installer or reinstalling if a plug-in must move. Don’t drag a modern plug-in’s files between folders casually: presets, libraries, licensing components and registry entries may live elsewhere.
Fix 3: Add the path and enable the effect
- Open Options → Preferences → VST Effects.
- Compare VST search folders with the actual folder from Fix 2.
- Choose Add path if it is missing, or Edit path if an old path points somewhere else.
- After the scan, find the effect in Select VST effects to be available as audio plug-ins.
- Enable its checkbox.
A listed path is not enough if the individual effect is unchecked. Conversely, enabling an entry does not help if Sound Forge is scanning the wrong folder. The Sound Forge 2026 VST Effects preference page documents both controls.
Keep search paths narrow. Adding all of C:\Program Files makes Sound Forge inspect unrelated program files and turns every refresh into a slower, less diagnosable scan. Add the VST folder, not the entire drive.
Fix 4: Refresh after installation or update
In the VST Effects tab, click Refresh. Sound Forge’s current help explicitly says Refresh rescans after a new plug-in installation so the new effect appears in the list.
Let the scan finish. Then close Preferences and check View → Plug-In Manager. If the vendor installer was still open, close it first; if the plug-in uses a licence manager, complete activation before scanning again.
If one product still does not appear, verify that its .vst3 or VST2 .dll exists in the scanned folder. If it does not, repair or reinstall the plug-in from the manufacturer. Repeated Refresh clicks cannot discover a format that was never installed.
Fix 5: Search the Plug-In Manager, not only Favorites
Open View → Plug-In Manager. Select All and type part of the effect name in the search field. Also check:
- Third Party for vendor folders;
- By Category if the vendor supplied a category;
- By Type to distinguish VST versions and 32/64-bit builds;
- the options view, where an effect type may have been excluded from display.
The Manager tree mirrors the FX Plug-Ins menu. A plug-in can be installed and usable without appearing in your custom Favorites folder. Double-click an effect to apply it to the current selection or whole file, or drag it onto a data window to add it to that window’s real-time Plug-In Chain. Those actions are documented in the current Plug-In Manager help.
Once the effect works, drag it into FX Favorites if you want faster access. Don’t rebuild an installation merely because a Favorites submenu is empty.
Fix 6: Separate a scan failure from a broken interface
If the plug-in appears but its window is blank, clipped or unusable, return to Options → Preferences → VST Effects and enable Generic VST editor for that effect. This current Sound Forge option replaces the vendor’s graphical interface with generic parameter controls. It is a diagnostic and a practical fallback, not a rescan.
If Refresh freezes on one product, do not kill random background processes or delete the whole cache. Remove the suspect VST2 folder from the search list temporarily, restart Sound Forge and refresh the remaining paths. If the scan completes, update, repair or uninstall that plug-in with the vendor’s installer, then add the path back.
For VST3, avoid manually moving the bundle out of the standard folder. Note the last product shown during the scan, update it from the manufacturer, and send its version plus the Sound Forge build number to Boris FX support if the hang repeats. This leaves a reproducible problem instead of a damaged plug-in installation.
Fix 7: Restore a plug-in that was hidden
Sound Forge’s Plug-In Manager has a real Hide command. A hidden plug-in remains installed but stops appearing in Sound Forge. First run Refresh and check All, By Type and the Manager options. If the effect is still absent and you know it was hidden, the current help gives a version-specific reset:
HKEY_CURRENT_USER\Software\BorisFX\Sound Forge Pro\2026.0\DXCache
This is a last resort because it edits the Windows Registry. The current Sound Forge 2026 Plug-In Manager help documents that exact key for restoring hidden plug-ins. Close Sound Forge, open Registry Editor, export the DXCache key as a backup, then delete only that key and restart Sound Forge so it can rebuild the scan. Don’t delete the parent Sound Forge key. If your installed version is not 2026, use the matching help or ask Boris FX support for the correct path rather than guessing.
Symptoms and the shortest next check
| Symptom | Check next |
|---|---|
| No entry in VST Effects preferences | Format, architecture, actual file and search path |
| Entry exists but is unchecked | Enable it, then reopen Plug-In Manager |
| Checked but absent from Favorites | Search All in Plug-In Manager; Favorites is only an organization layer |
| Visible but blank interface | Enable Generic VST editor |
| Refresh hangs on one product | Isolate the path, update or reinstall that plug-in |
| Previously hidden effect never returns | Back up and reset only the documented 2026 DXCache key |
| Synth or sampler is missing | Use a DAW for the VST instrument and render audio into Sound Forge |
Frequently Asked Questions
Why does Sound Forge Pro not find my newly installed VST plug-in?
The VST build may not be installed, its folder may not be listed under Options → Preferences → VST Effects, the effect may be unchecked, or the scan may not have been refreshed. Verify those four points in that order.
Where is the standard VST3 folder on Windows?
The standard global path for 64-bit VST3 plug-ins is C:\Program Files\Common Files\VST3. Steinberg also defines a per-user path at %LOCALAPPDATA%\Programs\Common\VST3. VST2 has no single required folder, so check the manufacturer’s installer and add the actual VST2 path to Sound Forge.
Does Sound Forge Pro 2026 support VST3 effects?
Yes. The current Plug-In Manager organizes scanned effects by VST version and 32/64-bit type, and Sound Forge’s current help documents third-party VST effects. Install the current 64-bit VST3 build where the vendor offers it.
Why is a checked plug-in missing from FX Favorites?
FX Favorites is an organization layer, not the complete installed list. Search the All folder in View → Plug-In Manager. You can double-click the effect there, drag it to a Plug-In Chain, or add it to Favorites after confirming that it loads.
Why is the plug-in window blank?
Enable Generic VST editor for that effect in Options → Preferences → VST Effects. If the generic controls work, the plug-in was scanned and the problem is its graphical interface, not discovery.
Why does my VST instrument not appear?
Sound Forge hosts audio effects rather than a MIDI instrument workflow. Load the synth or sampler in a DAW, render its output, and edit the audio file in Sound Forge.
How do I restore a plug-in hidden in Plug-In Manager?
After ordinary Refresh and list checks fail, follow the current 2026 help: close Sound Forge, export the exact DXCache registry key as a backup, delete only that key, and restart to rebuild the scan. Use support documentation matching your installed version.
Once the plug-in appears, verify it in the Plug-In Chain workflow. If Sound Forge freezes during the scan instead of finishing with a missing entry, follow the startup-crash isolation steps and change one plug-in at a time.
Last fact-checked: August 2, 2026.