Microphone Works in Discord but Not in Your Game
Windows keeps two separate default microphones, not one: a default device for ordinary apps and a default communication device for voice-chat apps. Discord asks Windows for the communication device and most games ask for the plain default, so when those two point at different microphones only Discord hears you. Set both to the same microphone in the Sound control panel's Recording tab and the game will pick it up.
Start here
This symptom confuses people because it looks contradictory — the microphone obviously works, something is receiving it, and yet the game is silent. That combination is actually the most useful clue you can get. It rules out a broken microphone, a bad cable, a missing driver, and a muted device all at once, because none of those would let Discord work. What is left is a routing question: which microphone did each application ask Windows for, and did it get the same one you are talking into.
Symptoms
- Discord, Teams, or another voice app picks up your voice normally
- The game's own voice chat shows no input activity at all
- The game's push-to-talk indicator never lights up
- Windows' own microphone test works, but the game still hears nothing
- It started after plugging in a headset, webcam, or new USB microphone
Why this happens
Windows is routing the two apps to different microphones
Windows assigns audio devices a role. Ordinary multimedia applications get the console role; voice and calling applications specifically request the communications role. Discord is a communication app, so it asks for the communication device by name. Most games just ask for the default. If a headset holds one role and a webcam or motherboard input holds the other, both apps are working correctly and listening to different hardware.
Set the same microphone as both default and default communication device
A new device silently took one of the roles
When you connect a headset or webcam, Windows detects what the device is suited for and can assign it the communications role automatically. Microsoft is explicit that the system does the detection but leaves the actual choice to the user — which is why this can change under you without anything appearing to have been configured.
Set the same microphone as both default and default communication device
The game is pointed at the wrong input in its own settings
Many games keep their own audio device list, chosen once and then remembered. If it was set when a different microphone was plugged in, the game keeps asking for hardware that is no longer there, regardless of what Windows considers the default.
The game is a Microsoft Store title with its own permission
Windows treats Store apps and desktop apps differently for privacy. Store apps appear individually in the microphone permission list, while every desktop app shares a single toggle. A Game Pass or Store version of a game can therefore be denied microphone access on its own while Discord, a desktop app, is unaffected.
Check microphone permissions, especially for Store and Game Pass games
Fixes
1.Check which input the game is set to
about 5 minTakes a minute and rules out the simplest explanation before you change anything system-wide. Games remember a device chosen months ago, which may no longer be connected.
Applies to: Windows 10, Windows 11
- Open the game's audio or voice chat settings.
- Find the input, recording, or microphone device list.
- If it says Default, change it explicitly to your microphone by name; if it names a device you no longer use, change it to the right one.
- Look for an input level or test meter in the same screen and speak — if the meter moves, the game can hear you now.
- Check the push-to-talk key too, since a game set to push-to-talk with an unbound or conflicting key looks identical to a dead microphone.
2.Set the same microphone as both default and default communication device
about 5 minThis is the actual cause in most cases. Windows exposes two separate defaults and the two applications are asking for different ones — pointing both at the same hardware makes the distinction irrelevant.
Applies to: Windows 10, Windows 11
- Press Windows+R, type mmsys.cpl and press Enter. This opens the classic Sound control panel, which is the only place both roles are visible at once.
- Open the Recording tab.
- Look at the labels under each device. One may say Default Device and a different one Default Communication Device — that split is the problem.
- Right-click the microphone you actually speak into and choose Set as Default Device.
- Right-click the same microphone again and choose Set as Default Communication Device.
- Confirm both labels now sit on that one device, then click OK.
- Restart the game — most read their audio device once at startup — and test again.
Confirmed by the vendor.
Source: Microsoft
3.Check microphone permissions, especially for Store and Game Pass games
about 5 minWorth checking when the game came from the Microsoft Store, because Store apps carry individual permissions while desktop apps like Discord share one blanket toggle. That asymmetry produces exactly this symptom.
Applies to: Windows 11, Windows 10
- Open Settings → Privacy & security → Microphone.
- Confirm Microphone access is on for the device.
- Under the list of apps, find the game if it came from the Microsoft Store or Game Pass and make sure its switch is on.
- Scroll down and confirm Let desktop apps access your microphone is on — this single toggle covers every non-Store application.
- Restart the game and test again.
Confirmed by the vendor.
Source: Microsoft
4.Confirm the microphone with Windows' own test
about 5 minSeparates a routing problem from a level problem. If Windows records you clearly but the game hears nothing, you have proof the hardware is fine and the fixes above are the right direction.
Applies to: Windows 11, Windows 10
- Open Settings → System → Sound.
- In the Input section, select the microphone you intend to use.
- Open its properties with the arrow next to it.
- Choose Start test and speak normally, then stop the test and check the recorded level.
- If the level is very low, raise Input volume on the same page — some games gate their voice detection at a threshold a quiet microphone never reaches.
Confirmed by the vendor.
Source: Microsoft
If none of this worked
If no application hears you, including Discord, this is not the right page — that is an ordinary microphone or driver problem and the Windows test above is the place to start. If the game hears you but other players do not, the problem is in the game's own voice settings or its server, not in Windows. And if the microphone works everywhere except one specific game, check that game's community for a known bug before changing system settings, since some titles have shipped with broken voice input for months at a time.
Common questions
- Why does Windows have two default microphones at all?
- So that a headset can handle calls while speakers and a better microphone handle everything else. Microsoft added the communications role specifically to let an application tell the difference between a device chosen for phone calls and one used as a general multimedia device. It is genuinely useful — it just produces confusing results when the two roles drift apart without you noticing.
- Why does my game audio drop in volume when a voice call starts?
- That is the same system, working as designed. When a communication stream opens, Windows raises a ducking event and by default lowers or mutes non-communication audio. You can change the behaviour on the Communications tab of the same mmsys.cpl window where you set the device roles.
- Do I need the classic Sound control panel, or can I use Settings?
- You need mmsys.cpl. The modern Settings app shows one input device, which hides the very split causing the problem — the Recording tab is where both roles are labelled and where you can assign them.
- Will setting both roles to one device break my headset?
- No. It only tells Windows which microphone to hand out when an app asks. You can move either role back at any time from the same screen, and nothing about the device's drivers or configuration changes.
Did this fix work?
If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected — reports are reviewed before new articles.
Report a problem with this pageRelated problems
Sources
- Using a Communication DeviceOfficial
Microsoft · Documentation · checked Aug 16, 2026
- Windows maintains a separate communication device role (eCommunications) alongside the multimedia console role (eConsole)
- The multimedia control panel Mmsys.cpl provides a Default Communication Device option for both the Playback and Recording tabs
- Windows performs automatic role detection when a device is connected but does not itself choose which device is used for communications — the user must do that
- Communication applications such as VoIP apps request the endpoint by passing eCommunications to IMMDeviceEnumerator::GetDefaultAudioEndpoint, which restricts enumeration to communication devices
- The eCommunications role exists so an application can distinguish a device chosen for handling calls from one used as a multimedia device
- When a communication stream opens, the system generates ducking events and by default mutes or lowers the volume of non-communication streams
Microsoft · Support page · checked Aug 16, 2026
- Microphone access is controlled at Settings > Privacy & security > Microphone on Windows 11
- Microsoft Store apps are listed individually under Choose which apps can access your microphone
- Desktop applications are governed collectively by a single Let desktop apps access your microphone toggle rather than individually
Microsoft · Support page · checked Aug 16, 2026
- Input devices are selected under Settings > System > Sound in the Input section
- Windows provides a built-in microphone test under the device's Properties, using Start test and speak normally
- Input volume for the selected microphone is adjustable from the same properties page