Bluetooth Audio Codec Settings in Windows Registry

This article explains the specific Windows Registry locations used to configure and control system-wide Bluetooth Advanced Audio Distribution Profile (A2DP) codec negotiations, such as SBC, AAC, and aptX. By modifying these registry entries, administrators and power users can determine codec priorities, disable specific codecs, and manage Bluetooth audio streaming behavior across the operating system.

Primary System-Wide Registry Key

Windows handles system-wide Bluetooth A2DP audio codec negotiation parameters through the Bluetooth A2DP driver service configuration. The primary registry path is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BthA2dp\Parameters

If the Parameters subkey does not exist under BthA2dp, it can be created manually to define global codec behavior.

System-Wide Codec Control Values

Within the BthA2dp\Parameters key, Windows evaluates specific DWORD (32-bit) values during the Bluetooth device handshake to determine which codecs are offered or restricted:

Alternative Driver-Level and Stack Paths

Depending on the specific Bluetooth stack (native Microsoft stack versus third-party vendor drivers like Intel, Qualcomm, or Realtek), codec negotiation overrides may also be located under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\A2DP\Parameters

For hardware-specific driver properties, codec capabilities are referenced within the network adapter class keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{e0cbf06c-1708-4540-a140-6d42775312b4}

Device-Specific Negotiated Settings

To view or clear cached codec parameters negotiated with previously paired devices, Windows stores endpoint-specific configurations in the enumeration key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\BTHENUM

Under each device’s unique MAC address subkey, the Device Parameters folder contains operational profile settings. Restarting the Bluetooth Audio Gateway Service (BTAGService) or rebooting the computer is required for any manual registry modifications to take effect.