MAPIWhy Is My Bluetooth Headphone Microphone Not Working?
Headphone playback and microphone input are separate paths. Music can work perfectly while the headset microphone is unavailable to a particular app or operating-system input setting.
First confirm that the headset microphone is selected as the input device and that the app has permission to use it. Microsoft specifically recommends checking microphone privacy access, the default recording device, input level, and drivers.
Key takeaways
- Microphone privacy permissions can block input even when Bluetooth playback works.
- The wrong recording device can be selected while the headphones remain the active output.
- Voice calls depend on a call-capable Bluetooth profile and app routing.
- Physical mute controls, fit, firmware, and drivers can affect microphone operation.
What it actually means
A Bluetooth headset microphone problem occurs when the headphone speakers may still play sound but voice input from the headset is missing, too quiet, or unavailable to an app.
The main explanation
Microsoft's microphone guidance begins with privacy permission, connection, default input selection, microphone testing, level, and drivers. Sony's call troubleshooting adds headset-specific checks such as Bluetooth call connection, device settings, fit, software, and reconnecting. The fastest diagnosis is to test the microphone in the operating system first. If the system test works but one app does not, focus on that app's permissions and device selection. If the system itself records nothing, focus on Bluetooth profile, mute, driver, pairing, and the headset.
Main causes and reasons
1. The app does not have microphone permission
Windows privacy settings can prevent desktop or store apps from accessing the microphone.
How to recognize it
- The microphone works in system test but not one app
- Microphone privacy is disabled
- Granting permission restores input
Why it matters: No amount of Bluetooth re-pairing fixes an app that is denied access.
2. The wrong input device is selected
A laptop's built-in microphone may remain selected instead of the Bluetooth headset microphone.
How to recognize it
- Headphones play sound but input meter follows another microphone
- Selecting the headset input fixes it
- The app has its own device menu
Why it matters: Output and input devices can be chosen independently.
3. The headset is muted or the input level is too low
Physical mute buttons, boom position, or low input gain can create apparent failure.
How to recognize it
- A mute indicator is active
- The system detects the mic but records very quietly
- Raising input level helps
Why it matters: Simple controls should be checked before driver repair.
4. The call-capable Bluetooth profile is not active
Voice input requires the headset/call path rather than music-only playback.
How to recognize it
- Music works but no headset mic appears
- A call app cannot select the microphone
- Reconnecting for call mode restores input
Why it matters: A2DP is designed for music, while HFP/HSP handle voice calls.
5. Driver, firmware, or pairing state is faulty
Bluetooth and audio drivers plus headset firmware coordinate the microphone path.
How to recognize it
- The issue began after an update
- A clean re-pair changes behavior
- Another PC or phone can use the microphone normally
Why it matters: Software state becomes more likely when several apps cannot use the microphone.
How to identify your situation
The app's permission or input selection is the likely cause.
Next: Select the headset microphone inside the app and confirm permission.
The call profile, driver, or pairing state may be missing.
Next: Reconnect, re-pair, and update Bluetooth/audio drivers.
Input level, microphone position, or fit is more likely than total hardware failure.
Next: Raise the input level and verify the microphone opening/boom position.
The headset microphone hardware or firmware becomes more likely.
Next: Update firmware and use manufacturer service if it persists.
What you can do
- Check physical mute controls on the headset.
- Enable microphone access in operating-system privacy settings.
- Select the Bluetooth headset as the system input device.
- Select the same microphone inside the call or recording app.
- Run the operating-system microphone test and check input level.
- Reconnect or re-pair the headset if the call profile is missing.
- Update PC audio/Bluetooth drivers and headset firmware.
Common misconceptions
Bluetooth playback and microphone input can use different device paths and profiles.
Permissions and input-device selection are common software causes.
Many voice apps can override the system default with their own input selection.
When it may be a bigger problem
Seek support if the headset microphone fails on multiple source devices after firmware updates, correct permissions, clean pairing, and system-level microphone tests, or if the microphone was physically damaged or exposed to liquid.
Frequently asked questions
Why do my Bluetooth headphones work but the mic does not?
Playback and microphone input are separate. The mic can be blocked by permissions, wrong input selection, call-profile issues, or drivers.
Can Windows privacy settings block a headset microphone?
Yes. Microsoft specifically recommends checking microphone access for apps and desktop apps.
Why does the headset microphone work in one app but not another?
The failing app may have the wrong input device selected or lack microphone permission.
Do Bluetooth calls use a different profile than music?
Yes. Music typically uses A2DP, while voice calls use HFP/HSP or newer LE Audio capabilities.
Sources
- Fix microphone problems — Microsoft SupportOfficial
- While on a phone call, I can’t hear the other person talking, or they can’t hear me — Sony SupportOfficial
- How to use Bluetooth headphones for video calls on a computer — Sony SupportOfficial
Written by Mapiance Editorial Team
The Mapiance Editorial Team researches, writes, reviews, and maintains practical guides and explainers for MAPIANCE.
Reviewed by Mapiance Editorial Team
Published Sep 7, 2026 · Updated Oct 2, 2026 · Verified Sep 4, 2026