How to uninstall Voicemeeter Banana on Windows
Voicemeeter Banana is a virtual audio mixer with its own virtual audio devices, so removing it changes your sound setup: apps that used Voicemeeter's inputs or outputs fall back to another device after the restart the uninstaller asks for. Save your mixer configuration first with Menu › Save Settings if you might reinstall. This guide covers Voicemeeter Banana installed machine-wide from the VB-Audio.Voicemeeter.Banana winget package.
Quit Voicemeeter first
Switch the default playback and recording devices in Settings › System › Sound back to your real speakers and microphone, then close Voicemeeter from its window or tray icon. Check Task Manager (Ctrl+Shift+Esc) that no voicemeeterpro.exe is still listed before you uninstall.
Remove the app with its own uninstaller
Go to Settings › Apps › Installed apps, find Voicemeeter Banana, and choose Uninstall, or run:
winget uninstall --id VB-Audio.Voicemeeter.Banana
The uninstaller is VB-Audio's own setup program: it asks for administrator access, shows its window, and needs you to click Remove. It then asks you to restart Windows to finish removing the virtual audio devices. Restart before you check the result.
Where the data lives
| Location | What it holds | What to do |
|---|---|---|
Program Files (x86)\VB\Voicemeeter |
Program files | The uninstaller removes most of it; in this test the setup program voicemeeterprosetup.exe stayed there, so check the folder after the restart |
%APPDATA%\VoiceMeeterDefault.xml |
The mixer configuration Voicemeeter saves on exit | Keep it if you plan to reinstall; otherwise remove it |
Start Menu folder VB Audio |
Shortcuts | The uninstaller removes it |
Check the result
Run these read-only commands after the restart:
Get-Process voicemeeter* -ErrorAction SilentlyContinue
winget list --id VB-Audio.Voicemeeter.Banana
Test-Path "${env:ProgramFiles(x86)}\VB\Voicemeeter"
Test-Path "$env:APPDATA\VoiceMeeterDefault.xml"
Get-PnpDevice -FriendlyName "*VB-Audio*" -ErrorAction SilentlyContinue
- No output from
Get-Processonly means this query observed no matching process; a suppressed error leaves the running state unknown. - A completed
winget listquery with no match means the package record is gone; a matching row means the uninstall did not finish. Test-Pathon the program folder returningTruemeans files remain there; look inside and remove the folder yourself once the uninstall is finished.Test-Path "$env:APPDATA\VoiceMeeterDefault.xml"returningTruemeans your saved configuration is still there, which is expected unless you removed it yourself.- Devices listed by
Get-PnpDevicemean VB-Audio's virtual devices are still installed; if you did not restart yet, restart and check again. VB-Audio's other products, such as VB-Cable, use the same name, so check which device it is.
What Mole lists
For the measured Voicemeeter registration, Mole runs VB-Audio's uninstaller, whose window you finish yourself, and recognizes its own VB\Voicemeeter setup folder. %APPDATA%\VoiceMeeterDefault.xml is listed but not selected. VB-Cable, other VB-Audio products and driver packages are not removed by these file rules; finish the vendor's restart and check the devices separately.
What this test covered
Tested on 2026-09-27 with Voicemeeter Banana installed through winget, machine-wide. Remove was clicked in the uninstaller's window, which then asked for a restart; the test machine was not restarted, so the state after a restart was not verified. Not verified either: routing audio through Voicemeeter, or VB-Audio's other products installed alongside.
On 2026-10-04, the added residue rules were checked with controlled files in the Windows VM using the current source: exact ownership, another installed copy and source-path absence after recycling. This did not repeat the vendor uninstall or verify a released package.