Uninstall Voicemeeter A Complete Removal Guide

Why Voicemeeter Won't Just Leave

Voicemeeter is one of those programs that installs itself deep into Windows audio architecture. When you run the normal uninstaller, it removes the main application folder and a handful of registry keys. What stays behind includes a virtual audio driver, configuration files scattered across AppData, startup entries, and sometimes a service that refuses to shut down. I've watched people go through the standard uninstall three times and still have Voicemeeter appearing in their sound mixer, routing audio through channels that don't exist anymore. Here's the actual procedure. First, close Voicemeeter if it's running. Right-click the tray icon and exit. Then open Task Manager and check for any remaining processes like Virtual AE USB ASIO Service or Voicemeeter — kill them all. This matters because the uninstaller sometimes fails silently when the process is still holding onto driver files. Next, go to Settings > Apps > Installed Apps, find Voicemeeter, and run the uninstall. You'll be prompted by the VB-Audio uninstaller. Let it run. Once it finishes, don't restart yet. Open Device Manager, expand Sound, video and game controllers, right-click any entry with Voicemeeter or Virtual Audio in the name, and choose Uninstall device. Check the box that says attempt to remove the driver if one is available. Same thing for the Unknown device entries that sometimes appear under System devices after a failed uninstall — those are usually orphaned Voicemeeter services.

Now for the parts most guides skip. Open File Explorer and navigate to these locations, deleting anything Voicemeeter-related: C:Program Files\VB\\ C:Program Files (x86)\VB\\

C:Users\[YOUR_USERNAME]\AppData\Roaming\VB\\ C:Users\[YOUR_USERNAME]\AppData\Local\VB\\ C:Users\[YOUR_USERNAME]\AppData\Local\VB\\

The AppData folders are where the real stubbornness lives. Voicemeeter stores your audio routing configuration, input/output mappings, and personal settings there. Even after a clean uninstall, that data persists and can cause conflicts if you ever reinstall. I once spent forty minutes troubleshooting a phantom audio loop on a client's system before realizing it was a config file from a Voicemeeter installation they'd removed six months earlier. Deleted the AppData folder and it vanished. Then open regedit and navigate to these paths. Delete any keys containing VB or Voicemeeter: HKEY_LOCAL_MACHINE\SOFTWARE\VB\\

HKEY_CURRENT_USER\SOFTWARE\VB\\ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vb•audio\\

Be careful in the Services key. If you see VB•Audio Virtual ASIO or Virtual AE USB ASIO Service lingering after you've already uninstalled the driver, delete those service keys entirely. They won't come back on their own. That said, if you're not comfortable editing the registry, skip this step — a normal uninstall handles most of it. Open msconfig or check Task Manager's Startup tab and remove any VB•Audio or Voicemeeter entries. Then reboot. After the reboot, open Device Manager again and verify nothing shows up as a VB audio device. Run dxdiag and check the Sound tab — if Voicemeeter isn't listed, you're clean. One edge case worth knowing: sometimes Windows Update reinstalls a generic High Definition Audio driver that shadows the Voicemeeter removal. If your system still shows a second audio device after everything above, open Optional Updates in Windows Settings and hide any Microsoft KB updates related to audio drivers. I ran into this on a Windows 11 machine where a pending optional update kept pulling the driver back after I'd cleaned it. Disabled the update, wiped the device again, and it stayed gone.

This whole process usually takes about fifteen to twenty minutes if you follow it in order. The part that goes wrong is skipping the registry and AppData cleanup — people uninstall, reboot, and assume they're done because the Start Menu entry is gone. It isn't. The driver and its services are what cause the lingering problems, not the program folder itself. There's no official cleanup tool from VB-Audio, which is frustrating because the company knows this happens. Their only suggestion is the standard uninstaller, which is why the manual steps matter. If you want to reinstall Voicemeeter later, you can delete just the AppData config folders and keep the registry keys — it'll do a fresh install without old routing conflicts carrying over.