You are wearing a headset. The other side hears a room. Your voice is arriving through the laptop's built-in microphone, two feet further away, with the fan in it.
Nothing broke. Windows made a choice, correctly by its own rules, and did not tell you.
Why the device changes without you touching it
A new device arriving resets the default. Connect a dock, plug in an HDMI or DisplayPort monitor, pair a Bluetooth headset or plug in a USB microphone, and Windows evaluates whether the new arrival should become the default. Often it should. Twenty seconds before a call, usually it should not.
Monitors advertise audio. Almost every HDMI and DisplayPort monitor presents itself as a playback device whether or not it has speakers. This is the classic docked-laptop failure: sound goes to a monitor with no speakers, the call is silent for you, and you sound fine to everyone else.
Bluetooth headsets are two devices. A Bluetooth headset exposes a high-quality stereo playback profile and a low-quality bidirectional hands-free profile. Using its microphone forces the whole connection into hands-free mode and audio quality drops audibly. Windows switches between them automatically when an application opens the microphone, which is why music sounds fine until the call starts.
Applications keep their own selection, by device identity. Teams, Zoom, Meet and Webex each store which device you chose. When that device is absent they fall back to something else, and when it returns they do not always return to it. Your Windows default and your Teams default are two settings that agree only by coincidence.
The two defaults
Windows has two default audio devices, not one.
- Default Device is used by general applications: media players, browsers, games.
- Default Communication Device is used by applications that identify themselves as communication software, which is most meeting clients.
They can point at different hardware and frequently do. Setting your headset as Default Device while the Default Communication Device stays on the laptop microphone produces exactly the symptom in the first paragraph: everything sounds right to you, and the call uses the wrong microphone.
To see both, open the Sound Control Panel: run mmsys.cpl, or Settings → System → Sound → More sound settings. The Playback and Recording tabs each let you set both defaults by right-clicking a device. The green tick is the default device; the telephone icon is the default communication device.
Set both, on both tabs. This is the single change that fixes the most cases.
Making a selection stick
- Disable the devices you never want. In the Sound Control Panel, right-click a device you will never use — a monitor's phantom speakers, a webcam microphone — and choose Disable. A disabled device is not a fallback candidate, so Windows cannot switch to it. This works better than setting defaults, because it removes the alternatives rather than ranking them.
- Assign devices per application. Settings → System → Sound → Volume mixer sets the input and output device for each running application, and that assignment survives changes to the system default. Set it while the application is actually running or it will not appear in the list.
- Set the device inside the meeting app as well. Teams: Settings → Devices. Zoom: Settings → Audio. Meet: the settings menu inside the call. Windows-level defaults do not override an app's own stored choice.
- Turn off exclusive mode if a device keeps being seized. Device Properties → Advanced, uncheck Allow applications to take exclusive control of this device.
- Turn off audio enhancements on a microphone that sounds wrong. Device Properties → Advanced. Some drivers apply noise suppression and automatic gain that fight the meeting app's own processing, producing a voice that pumps or cuts out at the other end.
The docked-laptop checklist
If you dock and undock every day, this takes fifteen seconds and prevents most of it.
- 1. Dock, then connect the headset, then check. The last device to arrive is the one most likely to have changed the default.
- 2. Confirm the recording device shows a moving level bar when you speak. A device selected but receiving no signal looks identical to a working one until the call starts.
- 3. Confirm playback is the headset, not the monitor.
- 4. Confirm the meeting app's own picker matches.
Steps 2 and 3 are the ones people skip, and they are the ones that catch a mute switch on the headset cable, a dock port that has stopped passing USB audio, and a Bluetooth headset that connected for media but not for calls.
What a pre-call check is for
The problem is not difficulty. It is that the check has to happen after the last device change and before the call, and there is no natural moment for it. Nobody opens the Sound Control Panel between meetings.
CallReady makes it one click from the system tray. It confirms the microphone is actually receiving signal rather than merely being selected, flags input that is too quiet or clipping, checks that an output device is available, and reports the active devices. It also remembers the devices from your last successful check and warns you when Windows has switched to a different camera, microphone or speaker, which is the failure this article is about and the one nobody notices unaided.
It covers camera and framing, lighting on your face, and network latency, jitter and throughput in the same pass, and gives one plain verdict in about ten seconds. It checks the Windows setup; each meeting app still controls its own device picker, so confirm that too.
Quick reference
| Symptom | Cause | Fix |
|---|---|---|
| They hear the room, not your headset | Default Communication Device is the laptop mic | Set both defaults on the Recording tab |
| No sound for you when docked | Monitor claimed playback | Set the headset as default, disable the monitor's audio device |
| Headset sounds narrow on calls only | Bluetooth switched to hands-free | Expected; use a USB or wired headset if quality matters |
| Right device selected, still silent | Mute switch, dead dock port, or no signal | Watch the level bar while speaking |
| Windows is right, Teams is wrong | The app keeps its own selection | Set it in the app's device settings too |
| It changes back every morning | A device arrives at boot and resets the default | Disable unused devices |