● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows 11 sound control panel open on recording tab showing stereo mix device being disabled on a dark desktop setup
Fix It Yourself · Troubleshooting

mic picking up desktop audio

Updated 6 November 202615 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Your friends on Discord can hear your game, or your recording has music under your voice. A mic picking up desktop audio can be a sound setting sending your PC's audio into the mic, the mic physically hearing speakers or headphones, or electrical crosstalk in the analogue audio path. A quick test narrows the cause, and the checks below tell routing, acoustic bleed and electrical crosstalk apart. The settings come first because they're the easiest to check.

What Causes Mic Picking Up Desktop Audio?

When people on a call hear your game, music or video, the sound is getting into what your app sends in one of three ways. The app may be recording a device that carries your PC's sound (routing), the mic may be physically hearing speakers or headphones (acoustic bleed), or the analogue mic path may be picking up playback electrically (crosstalk). The fixes are different, so the first job is working out which.

The wrong input in your app. Discord, Zoom, Teams, OBS and games each pick their own input. If one is set to Stereo Mix, a virtual device or a loopback, it records everything your PC plays.

Stereo Mix as the default. Some sound drivers, Realtek among them, include a recording device called Stereo Mix (or What U Hear on some cards) that captures the PC's own output. If it's set as a Windows default input, an app left on that default can end up recording it.

Monitoring loops. Listen to this device in Windows and Monitor and Output in OBS send your mic to a playback or monitoring device. If a loopback or virtual input captures that playback, it can mix the mic with desktop audio. Headset sidetone often stays inside the headset, so it only matters if its software sends the mic to a playback device that a loopback or virtual input is recording.

Virtual audio software. Voicemeeter, VB-Audio Cable, headset suites such as SteelSeries Sonar, and NVIDIA Broadcast create their own devices and routes. A route set the wrong way sends playback into the virtual mic your apps use.

The wrong physical mic. If your headset mic isn't selected, an app may be using the webcam or laptop's built-in mic instead, and those sit close to the speakers and hear everything in the room.

Acoustic bleed. Speakers, or open-back headphones turned up loud, can be heard by a sensitive mic. That isn't a setting at all.

Electrical crosstalk. Some onboard audio, front-panel ports and combined headset jacks (one plug for headphones and mic) pick up a little of the playback signal electrically, often louder as you turn the volume up.

Quick routeStart here

Mic Picking Up Desktop Audio: Quick Fix

Start with the app and Windows' recording settings. Nothing here changes drivers.

1

Check Your App Input and Disable Listen to This Device Easy

  1. Choose the mic by name in your app.
    In Discord, Zoom, Teams or OBS, open the voice or audio settings and set the input to the device you intend to use by name rather than Default. That can be your physical microphone, or a virtual mic output if you deliberately use one.
  2. Check Windows' own choice.
    Go to Settings > System > Sound and, under Input, make sure your microphone is the one selected. Apps set to Default use a Windows default device, but calling apps can use the separate default communications device too. Step 4 sets both.
  3. Turn off Listen to this device.
    Press Win + R, type mmsys.cpl and press Enter. On the Recording tab, double-click your mic, open the Listen tab and untick Listen to this device. Click OK.
  4. Disable Stereo Mix.
    Still on the Recording tab, right-click an empty space and tick Show Disabled Devices. If Stereo Mix or What U Hear is enabled and you don't use it, right-click it and choose Disable. Then right-click the input you want apps on Default to use (your real mic, or a virtual mic if you deliberately use one) and choose Set as Default Device, then Set as Default Communication Device.
  5. Test.
    Play some music without speaking and watch the green bar next to your mic on the Recording tab. Then make a test call or recording to check the app is using the same device.
If the bar only moves when you speak, desktop audio is no longer reaching that Windows input.
mmsys.cpl opens the classic Sound control panel directly. In Windows 11 you can also reach it from Settings > System > Sound > More sound settings.
Intermediate routeKeep going if needed

More Mic Picking Up Desktop Audio Solutions

The next test is for a bar that still moves with music playing. It shows whether the sound is getting in through the mic or around it, and the fixes after it cover levels, effects and each app's own settings.

2

Tell Routing From Bleed Easy

  1. Mute the mic at the hardware.
    Play music, then use a hardware mute that leaves the mic connected and watch the bar for that same input. Don't unplug it for this test, because Windows can remove the device or change the default input.
  2. Read the result.
    If the bar keeps moving with the mic muted, playback is reaching the selected input without going through the mic capsule. Look for a loopback or virtual route (fixes 1 and 5), then electrical crosstalk (fix 9). If the bar stops, the physical mic or analogue input is involved, so carry on with fix 3.
  3. Record yourself.
    Open the Sound Recorder app, play some music quietly, and record a few seconds of silence and a few of talking. Playing it back shows what the Windows input records. It doesn't include a call app's own input choice or processing, so make a test call too if the app still sounds wrong.
  4. Try headphones at a lower volume.
    If the bleed drops a lot with speakers off and headphones on, that points to acoustic bleed. Turn the volume down, move the mic away from the speakers, or use closed-back headphones.
3

Fix Microphone Levels and Disable Enhancements Easy

  1. Turn down Microphone Boost.
    In mmsys.cpl, double-click your mic and open Levels. If Microphone Boost is there and turned up, lower it, then set the main level only high enough for clear speech. Both controls affect the whole mic signal, so move the mic closer if you need more voice level without more room sound.
  2. Try with effects off.
    In Windows 11, go to Settings > System > Sound, select your mic and, if Audio enhancements appears, set it to Off. On older versions, look for an Enhancements or Advanced tab in the mic's properties. Test, and turn them back on if it makes no difference.
  3. Use your app's noise and echo controls.
    Discord and Zoom have noise and echo controls in their audio settings. Teams provides Noise suppression and automatically cancels echo in calls. With speakers rather than headphones, echo cancellation is what stops the other person hearing themselves.
4

Set Up Each App's Audio Easy

  1. Discord.
    Open User Settings > Voice & Video. Set Input Device to your mic by name, and leave Echo Cancellation and Noise Suppression on if you use speakers. The mic test on the same page lets you hear what others hear.
  2. Zoom.
    Open Settings > Audio and pick your mic. For normal calls, choose Noise removal rather than Original sound for musicians, and leave echo cancellation enabled if you use speakers.
  3. Teams.
    Open Settings and more > Settings > Devices. Under Audio settings, choose your microphone. Under Noise suppression, choose Background noise only, or Voice isolation if it's available.
  4. OBS.
    In Settings > Audio, set Desktop Audio to your speakers or headphones and Mic/Auxiliary Audio to your mic. If Mic/Auxiliary Audio is set to Stereo Mix, OBS records desktop audio through its mic source. If you use a virtual device for either setting, check its routing before changing it.
  5. Games with voice chat.
    Many games have their own voice input setting, separate from Windows. Set it to your mic by name too.
5

Audit Your Recording Devices Fully Easy

  1. Show everything.
    On the Recording tab, right-click an empty space and tick Show Disabled Devices and Show Disconnected Devices.
  2. Look for loopback and virtual devices.
    Stereo Mix, What U Hear, Wave Out Mix, VB-Audio, Voicemeeter, headset-suite devices, or anything with Loopback in its name can carry PC sound. NVIDIA Broadcast devices are virtual too, but its microphone normally carries the mic selected in NVIDIA Broadcast, not desktop playback. Note which one your apps use.
  3. Set both defaults to the input you mean Windows to use.
    That's the same input you chose in fix 1. Right-click it and choose Set as Default Device, then Set as Default Communication Device, as calling apps can use the second one.
  4. Disable what you don't use.
    Disable a virtual device only if you don't need it. If you do use it, fix its routing instead (fix 7).
Advanced routeChange one thing at a time

Advanced Mic Picking Up Desktop Audio Fixes

If the bar kept moving in the mute test, the cause is likely to be one of these, from a monitoring loop or virtual audio routing to the sound driver or crosstalk on the analogue side.

6

Find Monitoring Loops in OBS and Headset Apps Medium

  1. OBS.
    Open Edit > Advanced Audio Properties. If your mic is set to Monitor and Output and its monitoring device is also captured as Desktop Audio, your voice can be recorded twice. Set the mic to Monitor Off, or monitor it through a device Desktop Audio doesn't capture.
  2. Headset apps.
    In your headset's software, look for sidetone or mic monitoring and turn it off or down while you test.
  3. Game and stream capture.
    If the problem only shows in a recording, not on calls, check whether the recording app is deliberately capturing both desktop audio and the mic on one track. If it is, music under your voice is expected and doesn't mean the mic is picking it up. If it isn't, remove or mute the unwanted desktop-audio source.
7

Check Virtual Audio Routing Medium

  1. Find what's in the chain.
    If you use Voicemeeter, VB-Audio Cable, SteelSeries Sonar or NVIDIA Broadcast, your apps' mic is probably one of their virtual outputs, not the physical mic.
  2. Follow the route.
    In that program, check that only the physical mic feeds the virtual output your apps use, and that desktop or game audio is routed only to your headphones. Each program shows this differently, so use its own guide.
  3. Test without it.
    Set your call app to the physical mic directly. If the bleed stops, the routing in the virtual audio program is the cause.
8

Disable Loopback in Your Audio Driver Panel Medium

Create a restore point before changing drivers: search Start for Create a restore point, select your system drive and check that Protection is On. If it is Off, click Configure, select Turn on system protection, click Apply, then click Create. If you can't create a restore point, back up important files before changing drivers.
  1. Open the sound panel.
    Search Start for your sound driver's app, such as Realtek Audio Console. Look for loopback, Stereo Mix, sidetone or mic monitoring options and turn off anything that sends playback to the mic.
  2. Update the sound driver.
    Get the current audio driver from your PC or motherboard maker's support page and install it, then restart.
  3. Roll back if it started after an update.
    In Device Manager, expand Sound, video and game controllers, right-click the audio device and choose Properties > Driver > Roll Back Driver, if it's available.
9

Rule Out Electrical Crosstalk Medium

  1. Try another port.
    On a desktop, plug the headset into the rear audio ports instead of the front panel.
  2. Check the plug type.
    A headset with one four-contact plug needs a combined headset jack. If you're using a splitter on separate mic and headphone sockets, make sure it's the right kind for your headset.
  3. Try the headset somewhere else.
    Plug it into another PC or a phone and make a test recording. If the bleed follows the headset, the headset itself is picking up its own speakers, which happens with some cheaper or damaged ones.
  4. Try USB audio.
    Try the same analogue headset through a small USB sound adapter. This bypasses the onboard analogue audio path. If the bleed stops, the onboard audio or front-panel wiring may be contributing. A USB headset can still be useful, but it changes the headset too, so it doesn't prove where the fault is.
When to stop. When the input bar moves only for your voice, the Windows input you're watching is no longer receiving desktop audio. If people still hear your game, check the input named in the call app and make a test call. If the app is using that mic and your speakers are on, it may be acoustic bleed, which headphones fix. And if the bleed only stops with the same headset through a USB sound adapter, keep using the adapter rather than chasing the onboard sound further.

Preventing Mic Picking Up Desktop Audio

A few habits stop it coming back.

  • Pick devices by name. In every call and recording app, choose your mic and headphones by name rather than Default.
  • Recheck after updates. After a sound driver or app update, check your app's input and the Recording tab in mmsys.cpl.
  • Give devices clear names. In mmsys.cpl, double-click a device and type a new name on the General tab, such as Headset mic, so it's obvious which one to pick in each app.
  • Use headphones on calls. They stop the mic hearing your speakers, which no setting can.
  • Keep Microphone Boost modest. Move the mic closer to your mouth before you turn the boost up.
  • Know your routing. If you use OBS monitoring, sidetone or virtual audio software, note how it's set up when it works, so you can put it back.

Mic Picking Up Desktop Audio: Summary

When your mic picks up desktop audio, set the input you intend to use by name in your app, turn off Listen to this device and disable Stereo Mix if you don't use it. Then mute the mic at the hardware, leaving it plugged in, and play music. If the bar keeps moving, the sound is getting in around the mic, through a loopback or virtual route or electrical crosstalk. If it stops, the physical mic or analogue path is involved.

For routing, look at OBS monitoring, virtual audio software and the sound driver's own panel. Headset sidetone only needs a look if its software feeds a playback device that a loopback or virtual input records. For acoustic bleed, use headphones, lower the volume and turn down Microphone Boost. For electrical crosstalk, try another port or the same headset through a USB sound adapter.

Frequently Asked Questions

Your app may be recording a device that carries your PC's sound, such as Stereo Mix or a virtual audio device, your mic may be hearing your speakers, or the analogue mic path may be picking up playback electrically. Set the input you intend to use by name in your app, turn off Listen to this device, and disable Stereo Mix if you don't use it. If it still happens, mute the mic at the hardware, leave it connected and play music. A bar that still moves means the sound is reaching the input without going through the mic. If it stops, the physical mic or analogue input is involved.

Press Win + R, type mmsys.cpl and press Enter. On the Recording tab, right-click an empty space and tick Show Disabled Devices. Right-click Stereo Mix (or What U Hear) and choose Disable, then right-click the input you want apps on Default to use and set it as the default device.

In the classic Sound control panel: press Win + R, type mmsys.cpl, open the Recording tab, double-click your microphone and open the Listen tab. Untick Listen to this device and click OK.

Look for other routes, such as mic monitoring, Monitor and Output on the mic in OBS, or virtual audio software such as Voicemeeter. Headset sidetone counts only if its software feeds a playback device that a loopback or virtual input records. If the input bar stops when the mic is muted, the physical mic or analogue input is involved. Use headphones or turn the volume down for acoustic bleed, then try another port or USB audio if needed.

Check OBS's own setup. In Settings > Audio, Desktop Audio should normally be your speakers or headphones, while Mic/Auxiliary Audio should be your physical mic or the virtual mic you intend to use. If Mic/Auxiliary Audio is Stereo Mix, OBS records desktop audio through its mic source. In Edit > Advanced Audio Properties, set the mic's monitoring to Monitor Off unless you monitor to a device Desktop Audio doesn't capture, or your voice is recorded twice.

A USB headset can bypass the onboard analogue audio path, and closed headphones stop the mic hearing your speakers. It won't fix a routing setting, so check your app's input, Stereo Mix and Listen to this device first. To test the onboard path with the same headset, use a small USB sound adapter.

It can make it worse. Lower Microphone Boost if it's higher than you need. Both the boost and main level affect the whole mic signal, so move the mic closer rather than raising either control if you need more voice without more speaker sound.