Featured image of post Fixing Voicemeeter Banana's AUX Input Showing \

Fixing Voicemeeter Banana's AUX Input Showing "no driver present" and Producing No Sound

What this is Link to this heading

This is a note on how I fixed an issue with Voicemeeter Banana where its virtual audio I/O, Voicemeeter AUX Input, suddenly started showing “no driver present” in red and stopped producing any sound.

Voicemeeter AUX Input showing “no driver present” in red

Environment Link to this heading

  • OS: Windows 11 Pro 25H2
  • Voicemeeter Banana: I don’t remember the exact version

Symptoms Link to this heading

  • As shown in the screenshot above, “no driver present” appeared in red under Voicemeeter AUX Input.
  • No sound came through Voicemeeter AUX Input, regardless of what I routed to it.
  • The Voicemeeter application itself remained responsive and could be operated normally.
  • Voicemeeter Input, the other Virtual Input, continued to work normally and produced audio without any issues.
  • The HARDWARE INPUT section also worked normally and received audio as expected.
  • I could run Restart Audio Engine, but it did not resolve the issue.

Cause Link to this heading

The issue appears to have been caused by an incomplete Voicemeeter Banana update, which left the old VAIO drivers installed alongside the current Voicemeeter configuration.

In other words, the application and its virtual audio drivers were no longer in a consistent state.

What I checked Link to this heading

I opened the Sound control panel by pressing Windows + R and running mmsys.cpl1, then checked the Playback tab to see whether both “VoiceMeeter Input” and “VoiceMeeter Aux Input” were present.

At this point, only “VoiceMeeter Input” was listed. “VoiceMeeter Aux Input” was completely missing.

The Playback tab in the Sound control panel. VoiceMeeter Aux Input is missing.

I also confirmed that the device was not simply hidden because it was disabled or disconnected.

Both “Show Disabled Devices” and “Show Disconnected Devices” are enabled.

This indicated that Windows was not recognizing the virtual audio device for Voicemeeter AUX Input at all, which suggested that the problem was caused by an inconsistency in the virtual audio drivers.

Research Link to this heading

After looking into the issue, I found that Voicemeeter changed the architecture of its VAIO drivers in 2024.

Previously, VAIO, AUX, and VAIO3 were handled as separate drivers. With the newer architecture, a single VAIO driver can provide up to eight Virtual I/O devices.

I suspect this change was related to the problem. The Voicemeeter application itself had been updated, but some of the old VAIO/AUX drivers remained installed, leaving the application and drivers in an inconsistent state.

Fix Link to this heading

Since the application and drivers appeared to be out of sync, I removed both and performed a clean reinstall.

These are the steps I followed:

  1. Save your Voicemeeter settings first if you want to keep them.
  2. Download the latest Voicemeeter Setup from the official website.
  3. Run the downloaded Voicemeeter Setup as administrator, select REMOVE, and uninstall Voicemeeter.
  4. Restart the PC.
  5. Open Device Manager and select View → Show hidden devices.
  6. Check the following categories in Device Manager for any old VB-Audio Voicemeeter devices. If any remain, uninstall them.
    • Sound, video and game controllers
    • Audio inputs and outputs
  7. Run Voicemeeter Setup as administrator and install Voicemeeter again.
  8. Restart the PC.

After completing these steps, the “no driver present” message disappeared, and Voicemeeter AUX Input started working normally again.


  1. You can also open it from Settings → System → Sound → More sound settings. ↩︎

Licensed under CC BY-NC-SA 4.0
Last updated on Sep 26, 2026