A specialized system file rather than a standalone audio plugin, WaveShell1-vst3 13.0-x64.vst3
The most frequent headache producers face is when a DAW fails to "see" the individual plugins, only showing the generic "WaveShell" name in the menu. 1. The "Generic Name" or Missing Plugin Bug An error appears when adding the Waves plugin to the insert vst plugin waveshell1-vst3 13.0-x64 -vst3-
Waveshell1-vst3 13.0-x64 -vst3- is a legitimate, digitally signed container plugin from Waves Audio. It is not malware or a conventional VST3 effect. Its purpose is to efficiently host multiple Waves processors under a single VST3 entry point. A specialized system file rather than a standalone
This indicates the specific shell instance. "1" usually refers to the primary or legacy shell. Depending on your Waves version and bundle, you might also see waveshell2, waveshell3, etc. This separation allows Waves to manage different plugin families or compatibility layers without crashing your DAW. If you have the Horizon bundle and the Mercury bundle, they might load via different shell numbers. Open Waves Central → Install Products
File/Component Identified: Waveshell1-vst3 13.0-x64 -vst3-
Product Family: Waves Audio (Waves Complete / Mercury / Bundles)
Version: 13.0
Architecture: x86-64 (64-bit)
Plugin Format: VST3 (Virtual Studio Technology 3)
Primary Function: Hosting/Container shell for multiple individual audio effect plugins.
The file in question: waveshell1-vst3 13.0-x64.vst3 is the 64-bit VST3 container for Wave Version 13. The “1” (e.g., WaveShell1, WaveShell2) historically allows Waves to bypass the 4GB DLL limit on Windows, though this is less relevant with VST3.