In-Game Voice Chat: Teammates Cannot Hear You? Microphone Input, Communications Device and In-Game Voice Settings Diagnosis Guide

Key takeaway: If teammates cannot hear you in a game but your microphone works in Windows and in Discord, the microphone is probably not broken. Windows, the game platform, and the game itself each choose an input device, and they can point at different microphones. Compare the three settings, test each layer separately, and change only one setting at a time.
Teammates cannot hear you in a game. The game itself sounds normal: you hear the effects, the music, and your teammates' voices. The microphone is not silent everywhere, because it works in the Windows microphone test and in Discord. That combination — silent in the game, working elsewhere — is the whole problem this guide addresses, and the combination itself is the first piece of evidence.
The instinct in this situation is usually to blame the microphone. A new microphone is bought, a driver is reinstalled, or the game is reinstalled, and the problem stays exactly where it was. That outcome is expected if the microphone was never the fault. A microphone that moves the meter in the Windows test and is heard in Discord has already demonstrated that it can capture sound, that its connection works, and that the system can process its input. The question is not whether the microphone works. The question is whether the game is listening to that microphone at all. Those are two different questions, and they need two different kinds of evidence.
This guide covers only a narrow shape. Four conditions must all be present. First, teammates hear nothing at all from you in the game — not quiet speech, not broken speech, but complete silence. Second, the same microphone works elsewhere: the Windows microphone test moves the meter, or a Discord or browser microphone test hears your voice. Third, the game's own sound is normal: you hear game effects, music, and your teammates. Fourth, the problem is not confined to one game on one server alone: the games and servers tested should be written down. A microphone that does not move the meter anywhere is a microphone, connection, or driver problem, not a game voice-chat problem. A game with no sound at all is a playback problem. A problem that appears in only one game on one server points to that game or server's own settings or permissions, and its diagnostic path is different.
Three places choose a microphone, and they can disagree
A computer does not have one microphone setting. It has three, and RigCheckup states this directly: the operating system's default input device, each application's own remembered input device, and the browser's per-site device choice and permission. Three places pointing at three different devices produce the classic symptom described in the sources: the test sounds clear through the headphones, Discord is listening to the webcam microphone, and the game is waiting for a microphone that was unplugged last week.
That is the central mechanism of this guide. The microphone is not broken. The game is listening to the wrong microphone. The distinction between "the microphone is broken" and "the game is listening to the wrong microphone" should be kept apart from the start, because the first is a hardware layer and the second is a settings layer, and they are fixed in different places.
The game has a voice layer of its own. The platform client, such as Steam, and the game itself each have an input-device choice, a voice-transmission switch, and a sensitivity setting. The platform's voice settings can override, and can also ignore, a change made in Windows, according to UmaTechnology. A Steam microphone test that works does not prove that a particular game is using the same microphone or that voice transmission is switched on in that game, a point RottenWifi states directly. Testing therefore has to be done layer by layer: the Windows test proves the microphone itself works, the platform test proves the platform layer works, and only the in-game test proves the game layer works. No one test stands in for the others.
Windows microphone privacy has two levels
Windows microphone privacy is not one switch. It has two levels, and the two levels should be kept separate in any diagnosis. The first level is the overall microphone access switch together with "Allow apps to access your microphone". The second level is "Allow desktop apps to access your microphone". Programs installed with an ordinary installer — including Discord and most games — are desktop apps, and they belong to the second level. If that second switch is off, a browser test can have sound while every desktop program is silent, a point made by RigCheckup. That split is one explanation for the pattern "the browser works, the game does not". It should not be presented as the most common cause, because the external sources disagree about ranking. VividRepairs describes app-layer permission as the most common cause by a wide margin, while RottenWifi lists a wrong microphone, push-to-talk, and game input device as several different breaking points without ranking them, and UmaTechnology lists a wrong microphone, privacy, and exclusive mode as three different breaking points. This guide reports that the sources disagree, lists each account with its source, and makes no ranking of its own.
Exclusive mode: one program can hold the microphone
Windows exclusive mode allows one program to take complete control of a recording device, which reduces delay. If Discord, streaming software, or another background program has already taken the microphone in exclusive mode, the game queues behind it and receives no sound. The microphone looks active in Windows, but the game cannot use it, a point made by VividRepairs and MimicParty. The characteristic sign of this layer is that the microphone works in one program and not in another, and that whichever program is opened first is the one that gets it. Closing the other programs that use the microphone and trying again is the comparison that tests this layer. It should be done as a single change, not combined with other changes, so that the result can be read.
Push to talk: no key pressed means silence
In push-to-talk mode, nothing is transmitted unless the assigned key is held down. The game's voice key and the platform's voice key are two independent settings, and they can be different, as RottenWifi states. A key that is wrong, a key that conflicts with another program, or a key held by another program can all produce silence that looks exactly like a broken microphone. The decisive comparison is to switch temporarily to open microphone, also called voice activity, and try once. If teammates can hear you after the switch, the fault is in the push-to-talk layer: the key, a key conflict, or the mode itself. The switch is a test, not a permanent recommendation. The original setting can be restored after the test, once the layer has been identified.
Old games read the old sound panel
Some older games, especially those using DirectSound, do not read the modern settings page. They read the old sound control panel, opened with mmsys.cpl, and its default recording device and communications device. If the microphone is not the default in that old panel, such a game may automatically choose the device at the top of the list, which may not be the microphone in use, a point made by VividRepairs. This layer applies only to older games, and it should be stated as applying only to them. It should not be presented as the behaviour of all games. For a modern game, the in-game input-device setting and the Windows modern settings page are the places to check first.
The five suspect layers
| Layer | What it means | Decisive comparison |
|---|---|---|
| In-game input device | The game has chosen the wrong input device, such as a webcam microphone, an old microphone, or a virtual audio cable, or voice transmission is switched off in the game | The input-device setting inside the game, plus a comparison with another game |
| Platform voice | The Steam or platform client has chosen the wrong microphone, the voice mode does not match, or the platform microphone test fails | The Steam "Start Microphone Test" comparison, plus the platform input-device setting |
| Windows input device | The Windows default input device is not the microphone in use, with several microphones present at once, such as a headset, webcam, or monitor microphone | Settings, System, Sound, Input comparison, plus removing extra microphones one at a time |
| Privacy and exclusive mode | The Windows microphone privacy switch is off, especially "Allow desktop apps to access your microphone", or another program holds the microphone in exclusive mode | The two-level privacy comparison, plus closing other programs that use the microphone and trying again |
| Microphone itself and connection | The microphone mute switch, a boom arm raised to mute, a plug in the wrong socket, a loose USB connection, or microphone volume at zero | The Windows microphone test, plus the physical mute switch and plug check |
Each layer has its own comparison, and no single comparison covers all five. The Windows test separates the microphone layer from the application layer. The Discord or browser comparison separates the Windows layer from the game and platform layers. The Steam test separates the platform layer from the game layer. The order in the seven steps below is the order that wastes the least time.
Seven diagnostic steps
Step 1 — Define the shape
Confirm the four shape conditions: teammates hear nothing, the microphone works elsewhere, the game's own sound is normal, and more than one game or server has been tested. Write down the baseline before changing anything: the microphone model and connection type, whether it is USB, 3.5 mm, or Bluetooth, the Windows default input device, the input device chosen inside the game, the voice mode — push to talk or open microphone — and the input device chosen in Steam or the platform client. A diagnosis built on a vague description such as "voice chat does not work" cannot be checked later, because it does not say which microphone, which game, or which layer was tested.
Step 2 — Run the Windows microphone test
Go to Settings, System, Sound, Input, and speak while watching the meter. This is the entry test for the whole guide. If the meter moves, the microphone itself, its connection, and the system's basic processing all work, the problem narrows to the application layer, and the diagnosis continues to Step 3. If the meter does not move, this is not the problem covered by this guide: the fault is in the microphone itself, its connection, or its driver, and a different diagnostic path applies. The result of this test should be written down before anything else is changed, because every later result is read against it.
Step 3 — Compare with other programs
Use the Discord microphone test or a browser microphone test and speak. If other programs hear you and the game does not, the fault points to the game or platform layer, and the diagnosis continues to Step 4. If other programs cannot hear you either, return to Step 2 and check the Windows layer. Do not keep changing settings inside the game while the Windows layer is still unproven. The comparison only works if the same microphone is used in each program; changing the microphone between tests makes the result unreadable.
Step 4 — Run the platform voice test
Use the Steam microphone test, found under Friends and Chat, then the gear icon, then Voice, then "Start Microphone Test", and speak to see whether it registers. The menu path is given as it appears in the current version; RottenWifi notes that older Steam paths no longer match the current version, so the path should be checked against the interface in use rather than treated as fixed. If the Steam test fails, the fault is in the platform layer or the Windows layer: the platform input device or the privacy setting. If the Steam test works and the game still does not hear you, the fault is in the game layer, and the diagnosis continues to Step 5. This step should be stated plainly: a Steam test that works does not prove that the game is using the same microphone.
Step 5 — Compare the in-game input device and voice transmission
Open the game's settings, under audio, voice, or communications, and check three things one at a time: whether the input device is the same microphone, whether voice transmission is switched on, and whether receiving and transmitting are separate switches that are both on. Change one item at a time and test after each change, rather than changing everything at once. This is the most important single step in this guide: Windows, the platform, and the game must all point at the same microphone before the game can hear you. The default communications device is not the only cause: the in-game input device, push to talk, privacy, and exclusive mode are separate layers, so do not stop after checking the default communications device alone. Each game has its own voice settings in its own place, and the Discord or Steam settings should not be treated as applying to every game. Menu paths vary by game and by version, so they should be checked against the interface in use.
Step 6 — Compare push to talk, privacy, and exclusive mode
Work through the three checks in this step one at a time. Change only one variable before each test, and write down the result before moving on to the next check. First, check both levels of the Windows microphone privacy switches — this is a read-only check, not a change — especially "Allow desktop apps to access your microphone", since desktop games belong to that second level. If a switch is off, switching it on is itself one change: test once, and restore it if the test does not explain the fault. Next, if push to talk is in use, switch temporarily to open microphone and try once. If teammates can hear you after the switch, the fault is in the push-to-talk layer: the key is wrong, the key conflicts, or the game and platform keys differ. Restore the original setting after the test. Finally, close every other program that uses the microphone, such as Discord or streaming software, and try again, to exclude exclusive mode. A result produced by changing three things at once proves nothing, because it does not say which change mattered.
Step 7 — Stop if the fault is still undivided
If the fault still cannot be divided after these steps, or if the microphone does not move the meter anywhere, a driver warning appears, or a USB device keeps disconnecting, stop and bring the written record to Room 1209, Dali Plaza, Shek Mun for inspection. The telephone number is 2186 8010 and WhatsApp is 6558 6806. The site's published three-tier fee is HK$400–780, HK$480–1,380, and HK$680–2,800, an overall range of HK$400–2,800, with the actual fee quoted after inspection. Do not delete the screenshots of the original settings; they are comparison material. A screenshot taken after the settings have been changed cannot show what the settings were when the fault occurred.
Boundary cases
A microphone that does not move the meter anywhere, including the Windows test, is a microphone, connection, or driver problem, not a game voice-chat problem. A recording file in which only the microphone is silent while the game sound is normal is a recording-capture problem, not a live game voice-chat input problem. A live stream in which only the microphone is silent is a streaming output problem. A change in ordinary playback sound after a call has ended is an output-device handover problem, in the opposite direction from this guide, which is about input. Teammates hearing you while you cannot hear them is the reverse direction: an output-device or game-output problem, not an input problem. A problem in only one game on one server points to that game or server's own settings or permissions, and it is an isolated case rather than a general diagnosis. Voice in a game that is choppy, intermittent, or distorted is a sound-quality problem, not a complete-silence problem. A microphone that produces echo, where teammates hear their own voices back, is a monitoring or crosstalk problem, not an input-silence problem.
Six common misconceptions
- "Teammates cannot hear me, so the microphone must be broken." Wrong. A microphone that moves the meter in the Windows test and is heard in Discord is not broken. Hardware should not be blamed until the Windows microphone test has been done.
- "The Windows default input device is correct, so the game must be correct." Wrong. The game has its own input-device choice and can point at a different microphone. Windows, the platform, and the game must be checked one at a time; they cannot be assumed to agree.
- "The Steam microphone test works, so the game must hear me." Wrong. A Steam test that works proves only that the Steam layer works. It does not prove that a particular game is using the same microphone or that voice transmission is switched on in that game.
- "Pressing the push-to-talk key must transmit." Wrong. The game's voice key and the platform's voice key are two independent settings and can differ. A key conflict, or a key held by another program, can also stop transmission. Switching temporarily to open microphone is the decisive comparison.
- "The microphone privacy switch is on, so every program can use the microphone." Wrong. Windows privacy has two levels: "Allow apps to access your microphone" and "Allow desktop apps to access your microphone" are two switches. Desktop games belong to the second one, and if that one is off, a browser test can have sound while every desktop program is silent.
- "Reinstalling the game or the driver will fix it." Wrong. Reinstalling before the layers have been divided is blind trial. Reinstalling does not correct a wrong input device, does not switch a privacy setting back on, and does not release exclusive mode. The layer must be identified first, so that the next step is known.
Sources and what they do and do not establish
RigCheckup, in "Mic Works in Browser but Not in Discord, Zoom or Games: Fix the App, Not the Mic", states that a computer has three microphone settings — the system default, each application's own setting, and the browser's per-site choice and permission — that can disagree with each other, that a microphone dead in one place and alive in another points to the application layer, and that Windows privacy has two levels, with desktop apps needing "Allow desktop apps to access your microphone".
RottenWifi, in "Steam Voice Chat Not Working: 5 Ways to Enable It", describes the Steam microphone test under Friends and Chat, then the gear icon, then Voice, then "Start Microphone Test", states that a Steam test that works does not prove a game is using the same microphone, notes that the game's voice key and the Steam voice key are two independent settings, notes that older Steam paths no longer match the current version, and covers the Windows privacy and default communications device layers.
UmaTechnology, in "How to Fix Steam Voice Chat Not Working on Windows?", states that Steam voice settings can override or ignore a change in Windows devices, lists a wrong microphone, privacy, exclusive mode, and drivers as different breaking points, and describes a wrong push-to-talk setting as one of the leading causes.
VividRepairs, in "Microphone Not Working in Game? Fix It Fast", describes the shape "the microphone works in Discord and Windows, but not in the game", and covers app-layer permission, a wrong input device, exclusive mode, and the old sound control panel, mmsys.cpl, noting that older games read the old panel rather than the modern settings page.
MimicParty, in "Troubleshooting Mimic Party voice not detected", describes a microphone that works in Discord and Zoom but not in a game lobby as a problem in how the game client asks the system for audio hardware, and lists exclusive-mode conflict, privacy restriction, and a wrong input device as three layers, noting that a platform update can make the default recording device disappear.
UmaTechnology, in "Fix Discord Audio: Mic, Headphones, and Voice Chat", advises separating the direction first — whether you cannot hear others or others cannot hear you — notes that push to talk transmits only while the key is held, suggests switching temporarily to voice activity as a test, and states that a Discord microphone test moving the meter is what proves input is being received.
No source cited here ranks the causes quantitatively, and the sources disagree about which cause is most common. This guide therefore makes no such ranking and reports the disagreement with its sources. No percentage, case count, success rate, or fee beyond the site's published three-tier fee of HK$400–780, HK$480–1,380, and HK$680–2,800 appears in this guide, because none is supported by the sources used.
FAQ
Does a moving meter in the Windows microphone test mean the microphone is not broken?
Yes. If the meter moves in the Windows microphone test, the microphone itself, its connection, and the system's basic processing all work. The fault narrows to the application layer, so continue with the other-program comparison, the platform test, and the in-game input-device check. Hardware should not be blamed until the Windows microphone test has been done.
Why can teammates not hear me when my microphone works in Discord?
The game is probably listening to a different microphone from the one Discord uses. Windows, the platform client, and the game each choose an input device, and they can point at different devices. Check the input device in the game first, then in the platform client, then in Windows, and make all three point at the same microphone.
Does a working Steam microphone test mean the game will hear me?
No. A Steam test that works proves only that the Steam layer works. It does not prove that a particular game is using the same microphone or that voice transmission is switched on in that game. The game has its own input-device choice and its own voice-transmission switch, and both must be checked inside the game.
I pressed the push-to-talk key and still nothing transmits — how do I test it?
In push-to-talk mode, nothing is transmitted unless the assigned key is held down. In open microphone, also called voice activity, transmission starts when the microphone detects speech. The game's voice key and the platform's voice key are two independent settings and can differ, and a key conflict, or a key held by another program, can also stop transmission. Switch temporarily to open microphone and try once: if teammates can hear you after the switch, the fault is in the push-to-talk layer. Restore the original setting after the test.
Why does my microphone work in a browser test but not in a game?
Windows microphone privacy has two levels. The first is "Allow apps to access your microphone". The second is "Allow desktop apps to access your microphone", and desktop games belong to that second level. If the second switch is off, a browser test can have sound while every desktop program is silent. Check both switches, and check them separately. Exclusive mode can produce the same symptom: if another program has already taken the microphone, the game queues behind it and receives no sound, so close the other programs that use the microphone and try again as a separate, single change.
What should I bring if the fault still cannot be divided after all seven steps?
Bring a written record of the microphone model and connection type, the Windows default input device, the input device chosen in the platform client and in the game, the voice mode, the results of the Windows microphone test, the Discord or browser comparison, and the Steam test, together with screenshots of the original settings. Bring that record to Room 1209, Dali Plaza, Shek Mun for inspection; the telephone number is 2186 8010 and WhatsApp is 6558 6806. The site's published three-tier fee is HK$400–780, HK$480–1,380, and HK$680–2,800, an overall range of HK$400–2,800, with the actual fee quoted after inspection.