How to Fix the Discord Error 3002 (Error: 3002)

If you’ve ever jumped into a voice channel and been greeted by a red banner reading “It looks like Discord is not detecting any input from your mic. Let’s fix that! (Error: 3002)”, you’re in the right place. Discord Error 3002 is one of the more frustrating mic-related issues the app throws at you — your headset is plugged in, Windows says the mic is working, and yet Discord refuses to pick up a single syllable. This guide walks through every proven fix, in order of how likely each one is to actually solve the problem.

What Is Discord Error 3002?

Discord Error 3002 is a microphone input detection failure. The app has found a recording device connected to your system, but it can’t capture any audio signal from it. Discord surfaces this as a warning rather than a hard crash, which means the app itself is running fine — something at the system or permission level is blocking the audio handoff.

Worth clarifying what this error isn’t: Error 3002 has nothing to do with your Discord account, server access, or internet connectivity in most cases. It’s specifically an audio input problem. It can appear in the desktop app or inside Discord’s browser version, and it affects Windows, macOS, and occasionally mobile.

Common Causes of Discord Error 3002

Understanding what triggers the error makes it much easier to zero in on the right fix instead of guessing randomly:

• OS-level microphone permissions blocked — Windows or macOS may be denying Discord access to the microphone, especially after a system update that resets privacy settings silently.
• Wrong input device selected in Discord — Discord may be set to listen on a different mic than the one you’re actually using, including a ghost device like a disconnected Bluetooth headset.
• Microphone muted inside Discord — The app has its own independent mute control that overrides system audio settings entirely.
• Outdated or corrupted audio drivers — A faulty driver can prevent applications from registering audio input even when the hardware is physically present and working.
• Third-party audio software conflicts — Tools like VoiceMeeter, Realtek Audio Manager, or Discord’s own noise suppression filter can intercept and drop the mic signal before it reaches the voice system.
• Corrupted Discord cache — Stale or corrupted cached data can cause Discord to misidentify or ignore the microphone entirely.
• Firewall or antivirus interference — Security software sometimes blocks Discord’s microphone access as a false-positive threat, or restricts the background processes Discord needs for real-time audio.
• VPN or proxy restrictions — Certain VPN configurations interfere with Discord’s WebRTC-based voice traffic, which can surface as audio input failures.

How to Fix Discord Error 3002 — Step by Step

Work through these fixes in order. The first few take under a minute each and resolve the problem for most users.

Fix 1: Check Microphone Permissions in Windows or macOS

This is the single most common cause of Error 3002, especially on machines that have recently had a Windows feature update. Privacy settings get silently toggled, and Discord loses permission to access the mic without any notification.

On Windows 10/11:

1. Press Windows + I to open Settings, then navigate to Privacy & Security → Microphone.
2. Confirm that Microphone access is toggled On at the top.
3. Scroll down and verify that Discord is listed and enabled under “Let apps access your microphone.”
4. If you’re using the browser version of Discord, also enable microphone access for your browser (Chrome, Firefox, Edge) in that same list.
5. Restart Discord and test your mic.

On macOS:

1. Open System Settings → Privacy & Security → Microphone.
2. Make sure the toggle next to Discord is switched on.
3. Quit and relaunch Discord after making the change.

Fix 2: Set the Correct Input Device in Discord

Discord stores the last-used input device, and if you’ve swapped headsets, added a USB mic, or unplugged a Bluetooth device, the app might be configured to listen to hardware that’s no longer connected.

1. Open Discord and click the gear icon (⚙️) near your username in the bottom-left corner.
2. Go to Voice & Video in the left sidebar.
3. Under Input Device, click the dropdown and select your active microphone explicitly — don’t leave it on “Default.”
4. Drag the Input Volume slider to a healthy level (around 75–100%).
5. Use the Let’s Check button to test if Discord is now picking up audio.

Selecting the microphone explicitly instead of relying on “Default” removes a layer of ambiguity where Discord and Windows disagree on which device is actually default at that moment.

Fix 3: Unmute Your Microphone Inside Discord

Discord has its own mute system that operates completely independently from your operating system’s mute controls. Many users accidentally trigger it and don’t realize it. If the mic icon near your username in Discord shows a line through it, you’re muted at the app level and no audio will transmit regardless of system settings.

Click the microphone icon next to your username in the bottom bar to toggle it off mute, then navigate to Settings → Voice & Video and confirm the input volume slider isn’t zeroed out or that Push to Talk isn’t accidentally activated without you pressing the assigned key.

Fix 4: Update or Reinstall Your Audio Driver

An outdated or corrupted audio driver is a surprisingly common cause of Error 3002, especially on systems that skipped driver updates or installed a Windows update that introduced an incompatible audio stack change.

1. Right-click the Start button and open Device Manager.
2. Expand Audio inputs and outputs and locate your microphone device.
3. Right-click it and choose Update driver → Search automatically for drivers. Let Windows attempt an automatic update first.
4. If that doesn’t help, visit your hardware manufacturer’s website directly — Realtek, Conexant, or your headset brand — and download the latest driver package for your Windows version.
5. Install it, restart your PC, and test Discord again.

If you suspect the driver itself is corrupted rather than outdated, uninstall the device from Device Manager entirely (check “Delete the driver software for this device” if offered), restart your machine, and let Windows reinstall it fresh on boot.

Fix 5: Disable Noise Suppression and Third-Party Audio Software

Discord’s built-in noise suppression — powered by Krisp — and third-party audio tools like VoiceMeeter or Realtek Audio Manager can intercept the microphone signal before Discord’s voice engine receives it, which manifests as Error 3002 even though the mic is technically active.

1. In Discord, go to Settings → Voice & Video and scroll to Noise Suppression.
2. Set it to None to disable it entirely.
3. If you’re running VoiceMeeter, exit it completely from the system tray.
4. Temporarily disable any audio enhancement software from your sound card control panel.
5. Test your mic in Discord.

If disabling noise suppression fixes the problem, you can try re-enabling it later to see if the issue was a temporary conflict or a persistent one. According to Driver Easy’s troubleshooting guide, this fix resolves the issue for a notable number of users who rely on audio enhancement tools.

Fix 6: Clear the Discord Cache

Discord stores cached application data locally, and when this cache becomes corrupted or stale, it can cause unusual behavior including microphone detection failures. Clearing it forces Discord to rebuild everything from scratch on the next launch.

On Windows:

1. Fully close Discord — right-click the system tray icon and choose Quit Discord.
2. Press Windows + R, type %appdata%\Discord, and hit Enter.
3. Delete the Cache, Code Cache, and GPUCache folders inside that directory.
4. Relaunch Discord and check if the mic is now detected.

On macOS:

1. Quit Discord completely.
2. Open Finder, press Cmd + Shift + G, and navigate to ~/Library/Application Support/discord.
3. Delete the Cache folder.
4. Restart Discord.

Fix 7: Check Firewall and Antivirus Settings

Windows Defender, third-party antivirus tools, and software firewalls can flag Discord’s background audio processes as suspicious and silently block them. This is particularly common after a Discord update when the app’s executable hash changes and the security software treats it as an unknown application.

1. Temporarily disable your antivirus or firewall, then test Discord’s microphone. If it works, the security software was the culprit.
2. Re-enable your security software and add Discord as an exception or trusted application instead of leaving it disabled.
3. In Windows Defender Firewall, go to Allow an app through firewall and confirm both Discord and Discord Update have access on Private and Public networks.

If you manage custom firewall rule configurations on your machine, verify no rules are blocking outbound connections on the UDP ports Discord uses for voice (50000–65535).

Fix 8: Disable VPN or Proxy

VPNs and proxies route your traffic through an intermediary server, and some configurations interfere with Discord’s WebRTC-based voice system. School and corporate networks are especially prone to this, as their firewalls may block the UDP traffic Discord relies on for real-time audio.

Disconnect your VPN entirely and test Discord with a direct connection. If that resolves Error 3002, the issue is with how your VPN handles real-time media traffic — you may need to adjust its VPN split tunnel settings to exclude Discord’s traffic from the tunnel, or switch to a VPN provider that doesn’t aggressively filter UDP.

Fix 9: Run the Windows Audio Troubleshooter

Windows includes a built-in recording device troubleshooter that can automatically detect and fix common audio input issues — driver conflicts, default device mismatches, and permission problems that aren’t immediately obvious from the surface. It’s a quick step worth taking before moving to a full reinstall.

1. Press Windows + I and navigate to System → Troubleshoot → Other troubleshooters.
2. Find Recording Audio and click Run.
3. Follow the on-screen steps, selecting your microphone when prompted.
4. Apply any fixes it recommends, restart Discord, and test.

The troubleshooter is particularly effective at catching issues introduced by Windows updates that quietly change audio service states or default recording device assignments. According to Appuals’ guide on Error 3002, combining the troubleshooter with a cache clear resolves the issue in most cases.

Fix 10: Reinstall Discord

If you’ve worked through every fix above and Error 3002 persists, a clean reinstall is the correct next step. The goal here is removing all residual Discord files, not just the app itself — leftover AppData folders from a standard uninstall often carry the same corrupted configuration right back into the fresh installation.

1. Uninstall Discord via Settings → Apps (Windows) or by dragging to Trash (macOS).
2. On Windows, navigate to %appdata% and delete the Discord folder entirely.
3. Also check %localappdata% and delete the Discord folder there.
4. Restart your computer.
5. Download the latest Discord installer from the official Discord download page.
6. Right-click the installer and choose Run as administrator to avoid permission-related install failures.
7. Launch Discord, configure your mic in Voice & Video settings, and test.

Discord Error 3002 During Installation or Update

Some users encounter Error 3002 not in voice channels but during the Discord installation or update process itself, where the installer fails partway through. In this context, the error usually indicates one of three things: a remnant from an incomplete previous installation is blocking the new one, an antivirus tool is blocking the installer’s write operations, or the network connection dropped mid-download.

The fix sequence for the installation variant is slightly different:

1. Close any running Discord processes via Task Manager before attempting to reinstall.
2. Delete the %localappdata%\Discord and %appdata%\Discord folders to remove all residual files.
3. Temporarily disable antivirus software during the reinstall, then re-enable it after Discord launches successfully.
4. Run the installer as administrator.
5. If the error persists, reset your network configuration by opening Command Prompt as administrator and running netsh winsock reset followed by netsh int ip reset, then restart and try again.

If you regularly experience network connection timeouts on your machine, verify your connection is stable before attempting a Discord reinstall, as a dropped connection mid-update is a reliable way to produce a corrupted installation state.

Quick Reference: Discord Error 3002 Fix Summary

When to Contact Discord Support

If all ten fixes have failed to resolve Discord Error 3002, there are two remaining possibilities worth checking before contacting support. First, check Discord’s official status page — if there’s a platform-level voice infrastructure issue, no amount of local troubleshooting will fix it, and it will resolve on its own. Second, test your microphone in a completely different application (Zoom, OBS, Windows Voice Recorder) to confirm the hardware itself is functioning correctly. If the mic doesn’t work there either, the problem isn’t Discord at all — it’s a hardware or driver issue that exists at the OS level.

For persistent problems that don’t fit any of the above patterns, Discord’s support team can review your specific setup at Discord’s official support portal.

Final Thoughts

Discord Error 3002 almost always comes down to one of three things: the operating system blocking mic access, a configuration mismatch inside Discord’s own voice settings, or a software conflict from a third-party audio tool or security application. Working through the fixes in order — starting with permissions and input device selection before moving on to driver updates and cache clearing — resolves the issue for most users without needing a full reinstall. Keep the Windows Audio Troubleshooter and a clean reinstall in your back pocket as a last resort, and you’ll have your mic back in Discord voice channels within minutes.