Bluetooth Classic (HFP) mic and speaker cannot operate simultaneously on Windows 11 25H2 — persists after September 2026 updates

Question

Bluetooth Classic (HFP) mic and speaker cannot operate simultaneously on Windows 11 25H2 — persists after September 2026 updates

Sam Ah 5

Product: Windows 11 Enterprise, version 25H2 Current build: 26200.9457 (KB5129195, out-of-band) Affected component: Bluetooth Classic Audio — Hands-Free Profile (HFP)

Summary On Windows 11 25H2, a Bluetooth Classic headset can use either playback (A2DP) or the microphone (HFP), but not both simultaneously. Selecting the Bluetooth microphone causes the recording endpoint to fail to open — the recorder stays at 00:00 and the app sometimes crashes — and playback drops at the same time. The internal laptop microphone works normally, and the same headsets work correctly (both directions) on mobile phones, which isolates the issue to the Windows Bluetooth audio stack rather than the accessories.

Environment (primary reproduction device)

OS: Windows 11 Enterprise 25H2, build 26200.9457
Device: Lenovo ThinkPad P16s Gen 3, machine type 21KS001MUS
Bluetooth adapter: Intel Wi-Fi 6E AX211 (Bluetooth 5.3)
Bluetooth driver versions tested: 23.170.0.3 and 24.50.0.4
Management: MDM-managed (Intune) with Configuration Manager co-management; no WSUS/upstream redirection (no WUServer/WUStatusServer configured)
Affected accessories: multiple Bluetooth Classic headsets — Apple AirPods and at least one additional third-party Bluetooth headset

Symptom detail

Output-only (A2DP): works.
Microphone (HFP): selecting the Bluetooth mic fails to open the capture endpoint; recorder remains at 00:00, occasional app crash.
Same failure across multiple third-party conferencing apps (e.g., Zoom, Teams) and the built-in Sound Recorder.
Internal mic + wired audio: unaffected.
Same headsets on a phone: both directions work — accessory ruled out.

Troubleshooting already performed (please do not re-suggest)

Re-paired devices; verified microphone privacy settings and audio services.
Rolled back and reinstalled Bluetooth drivers; tested multiple driver versions (23.170.0.3, 24.50.0.4).
Disabled audio post-processing/enhancements (Dolby).
Applied the HFP offload disable (HfpOffloadDisable) workaround.
Installed the September 2026 out-of-band update (KB5129195 / 26200.9457).
Tested a fresh local user profile on affected hardware to separate per-user audio state from an OS/driver-level cause (results per device in Fleet observation below).

Fleet observation The symptom appears on multiple managed devices, and testing indicates more than one root cause producing the same symptom:

Device 1: Resolved after BIOS/firmware and Bluetooth driver upgrades, with no user-profile change — indicating a firmware/driver-level factor on that unit.
Device 2 (on build 26200.9539): Symptom persisted on the primary user profile, but a fresh local profile on the same device resolved it; reverting to the original profile reproduced the failure — indicating per-user audio-state corruption on that unit, independent of OS build.
Device 3 : Symptom persists after all current updates and driver updates; . Computers

We are treating these as potentially distinct root causes and want confirmation of which are OS/stack-level versus device-local.

Relevant Microsoft context

The September 2026 Patch Tuesday update (KB5124008) has a Microsoft-acknowledged audio regression (documented for USB Audio Class 1.0 devices), partially addressed by out-of-band KB5129195, with microphone-related reports still outstanding. We want to know whether Bluetooth HFP capture is in scope of that regression or its follow-up.
The Release Preview update KB5124010 (build 26200.9539) release notes state it improves microphone compatibility with certain Bluetooth Classic Audio accessories. We want confirmation of whether that fix is intended to cover this exact HFP "speaker or mic, not both" failure.

Questions for Microsoft

Is Bluetooth Classic HFP capture failure ("speaker or mic, but not both") a known issue on 25H2 build 26200.9457, and is there a tracked bug or Known Issue Rollback?
Is the HFP microphone fix referenced in KB5124010 / 26200.9539 intended to resolve this specific failure, and which accessories/chipsets (specifically Intel AX211 and Apple AirPods) are in scope?
Is there a supported way for a managed enterprise device to obtain the fix ahead of general availability, or a confirmed GA date for the build carrying it?
What in-box diagnostics (Bluetooth/audio ETL traces, Feedback Hub category) would you like us to capture to progress this case?

Business impact Multiple users cannot use Bluetooth headsets for voice/conferencing on managed devices, affecting daily meeting workflows.Product: Windows 11 Enterprise, version 25H2

Sam Ah 5 Reputation points

2026-09-23T21:38:23.96+00:00

see the comment
Dominic Rossi 0 Reputation points

2026-09-28T18:32:56.0666667+00:00

Same issues here - 25H2, build 26200.9550, ThinkPad T14S Gen 6. Issue occurred after update. Tried most of the same troubleshooting steps you have with no luck. Happening across multiple headset models and apps.
Mihails Popovs 5 Reputation points

2026-09-28T22:30:15.09+00:00

I have exact same issue too on 25H2. Tried updating and rolling back driver, repairing device. Does not help. Started after an update last week.
Sam Ah 5 Reputation points

2026-09-29T15:09:37.9266667+00:00

@Dominic Rossi confirmed that this issue is happening on Lenovo Thinkpads @Mihails Popovs what model/brand are you working with? For us it is happening on multiple Lenovo thinkpad models
Mihails Popovs 5 Reputation points

2026-09-29T22:33:20.5633333+00:00

@Sam Ah Lenovo Thinkpad P16 Gen 3.
Will Nestor 0 Reputation points

2026-10-02T18:19:26.66+00:00

I am having this exact issue with the same symptoms and test results on several of the computers in my environment:

3 are Lenovo E14 gen 6, and one is a HP Elitebook 660 G11. Bluetooth headsets that work on other Lenovos/HPs simply will not work on these machines.

Has there been any movement from Microsoft on a fix?

1 answer

Your answer

Sam Ah 5 Reputation points

2026-09-23T21:38:23.96+00:00

see the comment
Dominic Rossi 0 Reputation points

2026-09-28T18:32:56.0666667+00:00

Same issues here - 25H2, build 26200.9550, ThinkPad T14S Gen 6. Issue occurred after update. Tried most of the same troubleshooting steps you have with no luck. Happening across multiple headset models and apps.
Mihails Popovs 5 Reputation points

2026-09-28T22:30:15.09+00:00

I have exact same issue too on 25H2. Tried updating and rolling back driver, repairing device. Does not help. Started after an update last week.
Sam Ah 5 Reputation points

2026-09-29T15:09:37.9266667+00:00

@Dominic Rossi confirmed that this issue is happening on Lenovo Thinkpads @Mihails Popovs what model/brand are you working with? For us it is happening on multiple Lenovo thinkpad models
Mihails Popovs 5 Reputation points

2026-09-29T22:33:20.5633333+00:00

@Sam Ah Lenovo Thinkpad P16 Gen 3.
Will Nestor 0 Reputation points

2026-10-02T18:19:26.66+00:00

I am having this exact issue with the same symptoms and test results on several of the computers in my environment:

3 are Lenovo E14 gen 6, and one is a HP Elitebook 660 G11. Bluetooth headsets that work on other Lenovos/HPs simply will not work on these machines.

Has there been any movement from Microsoft on a fix?

Answer 1

Allan Solomon Mejia 10,225

Hello @Sam Ah

Bluetooth Classic HFP supports simultaneous monaural microphone capture and monaural speaker playback. Therefore, the microphone and speaker should operate concurrently in HFP mode.

However, HFP can’t provide high-quality A2DP stereo playback while using the headset microphone:

A2DP provides stereo playback only; it doesn’t support microphone capture.
HFP provides simultaneous microphone and speaker audio, but both use the HFP mono voice channel.
On Windows 11, A2DP and HFP endpoints are unified. Windows automatically switches to HFP when an application opens the Bluetooth microphone.

If the speaker stops completely when the microphone opens, that isn’t expected HFP behavior. Verify that the application uses the same Bluetooth device for both input and output, then update the Bluetooth/audio drivers from the PC manufacturer, remove and re-pair the device, and test with another HFP-capable headset.

If this is a custom Bluetooth device, also confirm that its HFP implementation establishes and maintains the bidirectional SCO/eSCO audio connection. You can’t validate that device-side implementation with the information currently provided.

Reference: Microsoft Bluetooth Classic Audio

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.

Sam Ah 5 Reputation points

2026-09-23T21:38:10.2166667+00:00

To clarify scope: this reproduces across multiple separate PCs, not a single unit. On each affected machine, every Bluetooth headset tested fails identically, while those same headsets work correctly (simultaneous mic + audio) on a mobile phone and on unaffected machines. The failure follows the Windows PC, not the accessory — which rules out a device-side HFP/SCO implementation and points to the host Bluetooth audio stack / HFP-SCO path on 25H2.

Given that, can you confirm:

Is this a known issue on 25H2 (build 26200.9457) — a failure to establish the HFP SCO/eSCO connection when an application opens the Bluetooth microphone — and is there a tracked bug or Known Issue Rollback?

Does the "microphone compatibility with certain Bluetooth Classic Audio accessories" fix in KB5124010 / build 26200.9539 target this SCO/eSCO setup path, and are Intel AX211 + Apple AirPods in scope?

What Bluetooth/audio ETL trace would you like captured during a reproduction so we can show where the HFP/SCO negotiation fails — rather than repeating per-device driver steps that were already completed before this case was opened?
Allan Solomon Mejia 10,225 Reputation points

2026-09-23T23:28:37.1666667+00:00
Thank you for the clarification. Since the failure reproduces with multiple headsets and follows the affected Windows PCs, the evidence points to the Windows host Bluetooth audio path rather than a headset-specific HFP implementation.

Microsoft’s documentation for KB5124010 states that it “improves microphone compatibility with certain Bluetooth Classic audio accessories.” However, the release notes don’t identify:

HFP SCO/eSCO negotiation as the corrected component.

Build 26200.9457 as having a confirmed regression.

Intel AX211 or Apple AirPods as specifically affected.

A Known Issue Rollback for this behavior.

Also, KB5124010 installs OS build 26200.9550 for Windows 11 25H2, not 26200.9539. Build 26100.9539 is the included servicing stack version.

The most useful next test is to install KB5124010 on one affected PC and repeat the same microphone-plus-speaker test. If it resolves the problem, that provides strong evidence that the compatibility fix covers this scenario, although Microsoft’s public notes don’t confirm its internal scope.

For diagnostics, use Windows Performance Recorder with Bluetooth-specific tracing profiles, but it doesn’t publish a support article specifying the exact HFP/SCO trace set required for this particular failure. Therefore, provide the trace profile and supporting logs through Microsoft Support, or reproduce the issue through Feedback Hub so it collects the applicable Bluetooth diagnostic data.

References:

KB5124010 - OS Builds 26200.9550 and 26100.9550

Bluetooth Driver Testing Resources
Allan Solomon Mejia 10,225 Reputation points

2026-09-29T01:53:01.4+00:00

Thanks, @Dominic Rossi and @Mihails Popovs . The additional reports are significant because the failure now reproduces across different PCs, Bluetooth adapters, headset models, and applications, while the common factor is Windows 11 25H2 after an update. That makes a Windows-side regression more plausible than an accessory-specific HFP implementation issue. This remains an inference, not an official Microsoft confirmation.

KB5124010 updates Windows 11 25H2 to build 26200.9550 and states that it improves microphone compatibility with certain Bluetooth Classic Audio accessories. However, Microsoft doesn’t document which accessories, chipsets, or HFP/SCO scenarios are covered. Since the issue persists on build 26200.9550, that published improvement hasn’t resolved this particular failure pattern.

KB5124010 - OS Builds 26200.9550 and 26100.9550

At this point, repeatedly reinstalling headset drivers or pairing additional devices is unlikely to add much diagnostic value. Each affected user should submit a Feedback Hub report while reproducing the microphone activation failure and share the Feedback Hub link here so others can upvote it.

Send feedback to Microsoft with the Feedback Hub app

I still cannot find verified official Microsoft documentation confirming this as a recognized 25H2 known issue, identifying a Known Issue Rollback, or confirming that the KB5124010 Bluetooth fix targets this HFP SCO/eSCO connection failure. We need a Microsoft support case with reproducible traces for authoritative confirmation and escalation to the Windows engineering team.