Bluetooth Headset Mic shows "Microphone unavailable

Because Windows already records from the headset and permissions are enabled, reproduce the failure in Edge InPrivate while recording edge://webrtc-internals, then use the reported WebRTC error to distinguish device contention, a missing Bluetooth input endpoint, or a WhatsApp-specific failure.

1. Isolate Edge extensions and profile state

1. Fully close applications that can capture audio, including Teams, Zoom, Discord, recording software, and other browser windows.
2. Open an Edge InPrivate window.
3. Open WhatsApp Web, grant microphone access when prompted, and test a call or voice message.

InPrivate provides an isolated test with default profile settings and without the usual extension environment. If it works there:

• Temporarily disable media, privacy, ad-blocking, and security extensions in the normal Edge profile.
• Re-enable them individually until the failure returns.
• Clear only WhatsApp Web’s stored site data and grant microphone permission again.

Microsoft documents extensions and damaged profile state as possible causes of website media-capture failures.^1^

2. Capture the actual WebRTC error

1. Open a normal Edge tab and enter: edge://webrtc-internals/
2. Leave that tab open.
3. In another tab, open WhatsApp Web and reproduce the microphone error.
4. Return to edge://webrtc-internals/.
5. Inspect GetUserMedia Requests and the WhatsApp entry for the failed request and error name.

Interpret the result as follows:^1^

• NotReadableError — the endpoint is locked or otherwise cannot be opened.
  • Exit Edge completely, including background Edge processes shown in Task Manager.
  • Close other capture applications.
  • Reopen Edge and test again.
  • Windows’ “exclusive control” checkbox is not a browser force-release mechanism; there is no supported Edge command that forcibly takes the microphone from another process.
• NotFoundError — Edge cannot detect the requested input endpoint.
  • Continue with the Bluetooth endpoint rebuild below.
• OverconstrainedError — WhatsApp requested capture constraints that the device could not satisfy.
  • Compare with another microphone and another browser. The available Microsoft guidance identifies this error but does not provide a verified WhatsApp-specific local correction.

Also check edge://policy. On a managed PC, inspect AudioCaptureAllowed and AudioCaptureAllowedUrls; organization policy can override the permission selected in Edge.^1^

3. Determine which component owns the failure

Run these comparison tests without changing the Windows defaults again:

1. Test the headset on a different microphone-enabled website in Edge.
2. Test WhatsApp Web in another supported Chromium browser.
3. If available, repeat both tests with a wired or USB microphone.

The results determine the next destination:

• Fails on every microphone-enabled website in Edge but works in another browser: collect the Edge version from edge://version, export/save the edge://webrtc-internals results, capture edge://policy, and contact Microsoft Support for Edge.
• Works on other sites and browsers but fails only on WhatsApp Web: contact official WhatsApp support; the failure is isolated to WhatsApp’s web capture implementation.
• Fails with only the Bluetooth headset across browsers: investigate the headset/dongle HFP driver path and contact the USB Bluetooth adapter or PC manufacturer for a Windows 11 driver or firmware update.
• Fails with every microphone across browsers: this is no longer isolated to WhatsApp; use Windows audio/driver troubleshooting.

4. Rebuild Bluetooth endpoints only for NotFoundError

Do this only if Edge reports NotFoundError or the headset disappears from Settings → System → Sound → Input. Windows 11 normally creates one input endpoint when the Bluetooth device supports HFP, and automatically switches from high-quality A2DP playback to HFP when an application opens the microphone.^2^

Removing devices can affect saved Bluetooth pairings; create a restore point first and remove only entries belonging to the HOCO headset.

1. Remove HOCO ES64 from Settings → Bluetooth & devices → Devices.
2. Open Device Manager → View → Show hidden devices.
3. Under Audio inputs and outputs, Bluetooth, and Sound, video and game controllers, uninstall only entries clearly associated with HOCO ES64.
4. Restart Windows.
5. Pair the headset again.
6. Confirm it reappears under Settings → System → Sound → Input, then retest Edge.

A closely related Windows 11 case restored Bluetooth microphone detection by removing saved Bluetooth audio endpoints and restarting, but that resolution applies most directly when the microphone endpoint is missing—not when Windows continues to expose and record from it.^3^

If the endpoint disappears again, obtain the Windows 11 Bluetooth driver supplied for the specific USB dongle. Treat dongle/HFP incompatibility as a hypothesis until confirmed by its manufacturer; Windows 11 itself supports HFP 1.7.2.^4^

References

1. Camera or microphone doesn't work on websites in Microsoft Edge
2. Bluetooth Classic audio
3. Windows 11 Bluetooth headset microphone not detected - Microsoft Q&A
4. Bluetooth version and profile support in Windows 11