AirPods Mic Not Working on Windows? Hands-Free Profile Is the Culprit

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Audio

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Mic Test

Your AirPods microphone stops working on Windows because the operating system switches Bluetooth to the Hands-Free Profile (HFP), which forces both audio input and output onto a single 8 kHz, narrowband codec that Windows then frequently fails to negotiate correctly. This is not a driver problem and reinstalling Realtek or Intel Bluetooth packages will not fix it. The root issue is that Bluetooth cannot simultaneously run the A2DP high-quality audio profile and the HFP microphone profile at full bandwidth, so Windows picks HFP for everything, then often drops the microphone endpoint entirely due to a timing conflict in the Windows Bluetooth audio stack introduced around the 22H2 build cycle.

Confirm the Mic Is Actually Dead Before You Change Anything

Before touching a single setting, verify the hardware side. Open Mic Test in Chrome or Edge, grant microphone permission, and watch the level meter. If you see zero movement while speaking directly into the left AirPod stem (left stem carries the primary microphone on AirPods Pro gen 1, gen 2, and AirPods 3), the Windows audio endpoint has either not been created or has been muted at the driver level. If you see movement but the level is extremely low and the waveform looks like a 300 Hz telephone call, HFP is active but functioning; your problem is codec quality, not a dead mic, and you skip to the profile-switching section below.

Also check this: go to Settings, then System, then Sound. Under Input, open the dropdown. If you see two AirPods entries, one labeled "Headset" and one labeled "Stereo," the Headset entry is HFP and the Stereo entry is A2DP. A2DP has no microphone. Selecting Stereo gives you good audio out but kills mic input entirely. That is the trade-off Windows forces on you.

The Hands-Free Profile Problem: What Is Actually Happening at the Protocol Level

Bluetooth Classic supports multiple profiles simultaneously, but audio profiles share the same ACL (Asynchronous Connection-Less) link bandwidth. A2DP uses up to 328 kbps for stereo output via SBC, or higher with aptX. HFP uses a Synchronous Connection-Oriented (SCO) or eSCO link running mSBC at 16 kHz in best case, or CVSD at 8 kHz in worst case. Windows 10 and 11 default to CVSD on most Intel and Qualcomm Bluetooth adapters unless the adapter firmware explicitly advertises eSCO T2 link parameters. Most laptops shipped before 2022 do not negotiate eSCO T2 correctly with Apple H1 or H2 chips, so you land on 8 kHz CVSD every time.

The H1 chip (AirPods Pro gen 1, AirPods 3) and H2 chip (AirPods Pro gen 2) both support eSCO but will fall back to SCO CVSD if the host adapter does not initiate the correct link type within the connection window. Apple's own Bluetooth stack on macOS handles this handshake correctly. Windows does not.

Profile Codec Sample Rate Mic Available Audio Quality
A2DP SBC / aptX 44.1 kHz or 48 kHz No High
HFP (CVSD) CVSD 8 kHz Yes Very low (telephone)
HFP (mSBC) mSBC 16 kHz Yes Acceptable for calls
HFP (LC3-SWB) LC3 32 kHz Yes Good (BT 5.2+ only)

Four-Step Fix for AirPods Mic Not Working on Windows

  1. Force the correct default input device. Right-click the speaker icon in the system tray, select Sound Settings, scroll to Input, and set the default device to your AirPods Headset entry. If no Headset entry exists, the HFP service has not started. Disconnect the AirPods, wait 10 seconds, reconnect, and check again. The Headset entry should appear within 5 seconds of reconnection.
  2. Disable audio enhancements on the HFP endpoint. Go to Control Panel, then Sound, then the Recording tab. Double-click the AirPods Hands-Free entry. Go to the Advanced tab. Uncheck "Enable audio enhancements." Windows audio enhancement processing applied on top of an 8 kHz stream introduces enough latency that the endpoint sometimes reports as unavailable to applications.
  3. Set the format to 16 bit, 16000 Hz. On the same Advanced tab, open the Default Format dropdown and select 1 channel, 16 bit, 16000 Hz. Do not select 44100 Hz or 48000 Hz for the HFP device. The driver will accept those values but the hardware link is still 8 kHz or 16 kHz; you get silence or distortion.
  4. Update the Bluetooth adapter firmware, not just the driver. For Intel adapters, open Device Manager, expand Bluetooth, right-click your Intel Wireless adapter, select Update driver, then Search automatically. Then separately go to Intel's support page and download the Intel Wireless Bluetooth package for your specific adapter model (AX200, AX201, AX210, AX211 are the common ones). The firmware file ships inside that package and updates the adapter's internal flash, which changes how it negotiates eSCO parameters with H1 and H2 chips.

After completing all four steps, reopen Mic Test and check the level meter again. You should see consistent input above the noise floor when speaking at a normal distance.

Application-Level Overrides That Break the Fix

Even after the system is configured correctly, individual applications can override your default device. Teams, Zoom, and Discord all have their own audio device selectors that default to "Same as system" but can silently switch to a different endpoint after an update.

If you want to verify your speaker output is also routing correctly after all these changes, use Speaker Test to confirm left and right channels are active on the A2DP profile.

Frequently Asked Questions

Why does my AirPods Pro mic work fine on my iPhone but not on my Windows PC?

iOS and macOS use Apple's proprietary Bluetooth audio stack, which correctly negotiates eSCO T2 links with the H1 and H2 chips and maintains A2DP output alongside a clean HFP microphone channel. Windows uses a generic Bluetooth audio stack that does not replicate this handshake, so you get degraded or absent microphone function depending on your adapter firmware version.

Will a USB Bluetooth dongle fix the airpods microphone not working on PC issue?

Sometimes. A dongle running a newer Bluetooth 5.2 or 5.3 chipset, such as the Cambridge Silicon Radio CSR8675 or Realtek RTL8761B, may negotiate mSBC or even LC3 Super Wideband with AirPods Pro gen 2 where your built-in adapter cannot. It is not guaranteed, but it is worth trying if your laptop has an older Intel 8260 or Qualcomm QCA61x4 adapter that predates eSCO T2 support.

My AirPods mic worked yesterday and stopped today. What changed?

A Windows Update, specifically cumulative updates to the Bluetooth Audio Driver Service (BthA2dp.sys or BthHFEnum.sys), can reset your audio format settings and re-enable audio enhancements. Check Windows Update history for anything installed in the last 24 hours. If an update is listed, redo steps 2 and 3 from the fix section above.

Can I use AirPods as a high-quality mic and keep good audio output at the same time on Windows?

Not over standard Bluetooth Classic. The A2DP and HFP profiles cannot share full bandwidth simultaneously on a single Bluetooth link. Your only option for both high-quality output and microphone on a PC is to use a wired connection via the Lightning or USB-C to 3.5 mm adapter, or to accept HFP's 8 kHz or 16 kHz microphone quality while in HFP mode.

The mic shows up in Device Manager but applications cannot see it. What is wrong?

The Windows Privacy settings are blocking microphone access. Go to Settings, then Privacy and Security, then Microphone. Make sure "Microphone access" is on at the top, then also enable "Let desktop apps access your microphone." Applications installed outside the Microsoft Store require that second toggle specifically.

How do I know if my AirPods are connecting in HFP or A2DP mode?

Open the Sound control panel (not Settings, the old Control Panel applet). On the Playback tab, if you see two AirPods entries, one is A2DP (higher quality, no mic) and one is HFP Headset (lower quality, mic present). The currently active profile is shown as the default device with a green checkmark. Whichever one Windows selected automatically is what you are using.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Mic Test