Voicemod Soundboard Not Working On Discord: Fix Guide

When your Voicemod soundboard doesn’t work on Discord, it is almost always one of seven specific issues — and most of them are five-minute fixes. This guide walks through each, in order from most-likely to least-likely, so you can stop pasting “voicemod discord broken” into Google and actually solve it.

I have seen this break for friends across two Windows updates and three Discord versions in the last year. The pattern is consistent: the audio routing chain between Voicemod’s virtual cable and Discord’s input device picks up a stale reference, and nothing works until you walk through the routing methodically. Below is the order I check.

---

Key Takeaways

• Wrong input device selection in Discord causes 70% of these issues
• Discord noise suppression can mute soundboard triggers
• Voicemod must be running before Discord opens for the virtual mic to register
• Clearing Discord cache fixes stale audio device entries
• Alternative apps like VoxBooster avoid kernel driver issues entirely

---

Issue 1: Wrong Input Device in Discord

This is the most common cause and the fastest fix. Discord needs to be receiving audio from the Voicemod Virtual Audio Device, not your actual microphone.

Fix:

1. Open Discord
2. Click the gear icon next to your username (bottom-left) to open User Settings
3. Click Voice & Video in the left sidebar
4. Under Input Device, click the dropdown
5. Select “Microphone (Voicemod Virtual Audio Device)” — the exact name may vary slightly
6. Click “Let’s Check” to test microphone input
7. Speak into your microphone — the input level bar should move

If you do not see Voicemod in the dropdown, Voicemod was not running when Discord opened. Close Discord completely (right-click the system tray icon > Quit), open Voicemod, wait for it to fully load, then open Discord again.

Issue 2: Voicemod Started After Discord

Discord scans for audio devices on startup. If you launch Discord first and then Voicemod, the Voicemod Virtual Audio Device may not appear in Discord’s dropdown until you restart Discord.

Fix: Always start Voicemod first, wait for the main window to appear, then start Discord. Set Voicemod to launch on Windows startup (Voicemod settings > General > Start with Windows) to make this automatic.

Issue 3: Audio Cable Not Enabled in Voicemod

Voicemod has an internal toggle for the Audio Cable feature. If it is disabled, no audio gets routed to the virtual microphone, and Discord receives silence.

Fix:

1. Open Voicemod
2. Click the gear icon to open Settings
3. Go to the Audio tab
4. Find the “Audio Cable” or “Virtual Microphone” setting
5. Toggle it on
6. Restart Discord

This setting sometimes gets reset by Voicemod updates. If your setup was working last week and broke today, this is the first place to check.

Issue 4: Discord Voice Processing Interference

Discord runs noise suppression and automatic gain control on incoming voice. These features can interpret sudden soundboard triggers as noise and reduce them to near-silence — your voice changer works fine, but soundboard sounds get stripped out.

Fix:

1. Open Discord User Settings > Voice & Video
2. Scroll to Voice Processing
3. Set Noise Suppression to “None” or “Standard” (avoid Krisp for soundboard use)
4. Disable Echo Cancellation if soundboard sounds bounce back through your speakers
5. Disable Automatic Gain Control to prevent volume riding on soundboard triggers
6. Test by triggering a soundboard sound in a voice channel

The downside: your ambient noise will come through more clearly. The upside: soundboard sounds play at full volume.

Issue 5: Discord Cache Corruption

Discord caches audio device information. After Windows updates, driver changes, or Voicemod updates, this cache can hold stale references that prevent the new virtual microphone from showing up correctly.

Fix:

1. Close Discord completely (right-click system tray icon > Quit Discord)
2. Press Win+R to open Run
3. Type %appdata%/discord and press Enter
4. Open the Cache folder and delete all files inside (do not delete the folder itself)
5. Repeat for Code Cache and GPUCache folders
6. Reopen Discord

This forces Discord to rebuild its device list on next startup. Your settings (servers, friends, etc.) are not affected — only the cached technical data.

Issue 6: Multiple Audio Devices Competing

If you have multiple virtual audio cables installed (VB-Cable, VoiceMeeter, plus Voicemod), they can conflict. Windows may route audio through the wrong virtual cable, or Voicemod may output to a different device than Discord is reading from.

Fix:

1. Open Windows Sound Settings (right-click speaker icon in taskbar > Sound settings)
2. Under Input, set your physical microphone as the default
3. Open Voicemod Settings > Audio
4. Set Input to your physical microphone
5. Set Output to your speakers
6. Verify the Voicemod Virtual Audio Device is enabled
7. In Discord, confirm Input Device is the Voicemod Virtual Audio Device

If you do not actively use other virtual cables, consider uninstalling them to eliminate routing confusion.

Issue 7: Voicemod Permissions

Voicemod needs administrator privileges on first install and after major updates. If you ran it without admin rights once, some functionality may have failed to register.

Fix:

1. Close Voicemod completely
2. Right-click the Voicemod desktop icon
3. Choose “Run as administrator”
4. Reconfigure your soundboard sounds if they appear missing
5. Test in Discord

Diagnostic Comparison Table

Symptom	Likely Cause	Fix
No sound at all in Discord	Wrong input device	Set Voicemod Virtual Audio Device as Discord input
Voice works, soundboard does not	Discord noise suppression	Disable Krisp / set Standard
Voicemod not in Discord dropdown	Started Discord first	Restart Discord with Voicemod running
Worked yesterday, broken today	Cache corruption or Voicemod update	Clear Discord cache
Sound only plays locally	Audio Cable disabled in Voicemod	Enable in Voicemod Audio settings
Random distortion	Multiple virtual cables conflict	Disable unused virtual audio drivers
Sound delayed several seconds	Driver-level latency	Check WASAPI buffer settings

When to Switch Soundboards

If you have tried all seven fixes and Voicemod’s soundboard still does not cooperate with Discord reliably, the issue may be deeper than configuration. Voicemod uses a kernel-mode audio driver, which historically has interaction issues with:

• Anti-cheat systems in competitive games (Valorant, EAC-protected titles)
• Newer Windows builds where kernel driver signing changed
• Multiple audio device installs on the same Windows install

Alternative: VoxBooster

VoxBooster handles soundboard, voice changer, and AI voice cloning in one app on Windows 10/11. It uses WASAPI (Windows Audio Session API) instead of a kernel driver, which means:

• No anti-cheat conflicts in games
• No kernel driver signing issues after Windows updates
• Cleaner uninstall (no orphan driver entries in Device Manager)
• Sub-300 ms latency from button press to audio in Discord
• Same virtual microphone routing approach Voicemod uses, but more robust

The setup is identical to Voicemod from Discord’s perspective: install VoxBooster, set its virtual microphone as your Discord input, and the soundboard plus voice changer route through one unified audio stream. See our Discord voice changer setup guide for the broader pipeline.

Verification Steps After Any Fix

Once you have applied a fix, verify with this checklist:

1. Open Discord, go to User Settings > Voice & Video
2. Confirm Input Device shows Voicemod Virtual Audio Device
3. Click “Let’s Check” — input bar should move when you speak
4. Join a voice channel (use a test server or DM voice call)
5. Trigger a soundboard sound — it should be audible to other users
6. Speak normally — your voice should come through with your selected voice effect
7. Have another user confirm what they hear matches what you intended

If steps 3 and 5 both work, the issue is fixed. If only step 3 works (voice but no soundboard), revisit Issues 3 and 4 above.

Preventing Future Breakage

A few habits prevent most recurrence:

• Set Voicemod to launch with Windows so it is always running before Discord opens
• After any Voicemod or Discord update, do a 2-minute test in a private voice channel before relying on the setup in a real conversation
• Keep notes on which Voicemod settings you customized — they sometimes reset on major updates
• Avoid installing competing virtual audio drivers unless you have a specific need
• Disable Krisp noise suppression in Discord if you use soundboards frequently

For broader audio setup guidance, see voice changer for Discord setup and best Discord soundboard sounds.

---

Soft CTA

If Voicemod’s quirks are wearing you down, VoxBooster handles the same workflow with WASAPI-based routing — soundboard, voice changer, and AI voice cloning in one app, fewer driver-level failure modes, and sub-300 ms latency on Windows 10/11.

---

Frequently Asked Questions