iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Windows 11 does not have a general Settings page that lists every Bluetooth audio codec or reveals the currently negotiated classic Bluetooth codec. You can check Microsoft’s documented codec support for your Windows version, identify the Bluetooth adapter and its driver, check whether the PC exposes LE Audio, and use a codec-aware diagnostic utility to see what a connected headset supports and which codec Windows selected.
For classic Bluetooth stereo audio, Microsoft documents support for SBC, AAC, aptX Classic, and—on selected systems with compatible Qualcomm Bluetooth radios—aptX Adaptive. That is a capability matrix, not a guarantee that every Windows 11 PC can use every codec. The headset, Bluetooth radio, firmware, driver, Windows build, and current audio profile must all agree.
Use the workflow below when you need to distinguish between the codecs Windows can support, the codecs your headphones advertise, and the codec actually being used.
Free tools Windows power users keep installed
One-click scans. No signup required.
What “supported Bluetooth codec” actually means
Bluetooth codec questions are often confusing because supported can refer to four different things:
#1 Best Overall
- LONG BATTERY LIFE: With up to 50-hour battery life and quick charging, you’ll have enough power for multi-day road trips and long festival weekends.(USB Type-C Cable included)
- HIGH QUALITY SOUND: Great sound quality customizable to your music preference with EQ Custom on the Sony | Headphones Connect App.
- LIGHT & COMFORTABLE: The lightweight build and swivel earcups gently slip on and off, while the adjustable headband, cushion and soft ear pads give you all-day comfort.
- CRYSTAL CLEAR CALLS: A built-in microphone provides you with hands-free calling. No need to even take your phone from your pocket.
- MULTIPOINT CONNECTION: Quickly switch between two devices at once.
| What is being checked | Meaning |
|---|---|
| Windows inbox support | Codecs that Microsoft’s Windows Bluetooth audio stack is documented to support in principle. |
| PC-platform support | What your particular Bluetooth radio, firmware, OEM driver, Windows build, and audio implementation expose. |
| Headphone support | Codecs advertised by the exact headphones, earbuds, or speaker model and revision. |
| Negotiated codec | The codec selected for the current connection, profile, and usage mode. |
A headset may support aptX Adaptive on a phone but use AAC or SBC on a particular Windows laptop. Similarly, a PC may expose AAC while the connected headset supports only SBC. For classic A2DP audio, Windows selects the first codec in its supported order that both the host and the Bluetooth audio device can use, subject to the driver and current connection state. Microsoft describes this selection behavior in its classic Bluetooth audio documentation.
Which Bluetooth codecs does Windows 11 support?
Microsoft’s current generic Windows 11 A2DP documentation lists the following codec order:
| Codec | Documented Windows 11 support | Qualification |
|---|---|---|
| aptX Adaptive | Windows 11 version 24H2 and later | Only on selected Windows devices with compatible Qualcomm Bluetooth radios. Microsoft also documents the lossless mode associated with aptX Adaptive on compatible systems. |
| AAC | Windows 11 version 21H2 and later | Both the Windows host and the Bluetooth audio device must support AAC. |
| aptX Classic | Windows 11 version 21H2 and later | Requires a compatible host, driver, and headset. |
| SBC | Windows 11 version 21H2 and later | The mandatory baseline codec for classic A2DP audio. |
Windows starts at the top of this list and chooses the first codec supported by both sides. The table is Microsoft’s documented Windows capability baseline; it does not mean that every Windows 11 computer, USB adapter, driver, or headset exposes all four codecs.
LDAC, aptX HD, and aptX Low Latency are not included in Microsoft’s generic inbox Windows 11 A2DP table. That does not make them impossible on Windows. A vendor-specific driver or dedicated USB Bluetooth transmitter can provide a different audio path, as explained below. It does mean you should not assume that the standard Windows Bluetooth driver will offer them.
Microsoft also provides separate Bluetooth Classic Audio accessory guidance, but the more detailed classic-audio codec matrix is the better reference for Windows-version details.
Step 1: Check your Windows 11 version and build
The Windows version matters because codec and LE Audio capabilities differ between releases. Check it before comparing your PC with a headset specification.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Open Settings.
- Go to System > About.
- Under Windows specifications, read Version and note the OS build if shown.
You can also press Win + R, type winver, and press Enter. Microsoft’s instructions are available in its guide to finding the Windows version.
Windows release branches change over time. Microsoft’s release-health information currently lists Windows 11 versions including 24H2, 25H2, and 26H1. The 26H1 release is intended for new devices rather than as a normal in-place feature update for existing PCs, so check the actual version shown by winver rather than assuming that every Windows 11 PC has the newest branch.
Step 2: Identify the actual Bluetooth adapter
Knowing that a PC has Bluetooth 5.x is not enough to identify its audio codec support. Find the actual radio and its driver instead:
Rank #2
- 65 Hours Playtime: Low power consumption technology applied, BERIBES bluetooth headphones with built-in 500mAh battery can continually play more than 65 hours, standby more than 950 hours after one fully charge. By included 3.5mm audio cable, the wireless headphones over ear can be easily switched to wired mode when powers off. No power shortage problem anymore.
- Optional 6 Music Modes: Adopted most advanced dual 40mm dynamic sound unit and 6 EQ modes, BERIBES updated headphones wireless bluetooth black were born for audiophiles. Simply switch the headphone between balanced sound, extra powerful bass and mid treble enhancement modes. No matter you prefer rock, Jazz, Rhythm & Blues or classic music, BERIBES has always been committed to providing our customers with good sound quality as the focal point of our engineering.
- All Day Comfort: Made by premium materials, 0.38lb BERIBES over the ear headphones wireless bluetooth for work are the most lightweight headphones in the market. Adjustable headband makes it easy to fit all sizes heads without pains. Softer and more comfortable memory protein earmuffs protect your ears in long term using.
- Latest Bluetooth 6.0 and Microphone: Carrying latest Bluetooth 6.0 chip, after booting, 1-3 seconds to quickly pair bluetooth. Beribes bluetooth headphones with microphone has faster and more stable transmitter range up to 33ft. Two smart devices can be connected to Beribes over-ear headphones at the same time, makes you able to pick up a call from your phones when watching movie on your pad without switching.（There are updates for both the old and new Bluetooth versions, but this will not affect the quality of the product or its normal use.）
- Packaging Component: Package include a Foldable Deep Bass Headphone, 3.5MM Audio Cable, Type-c Charging Cable and User Manual.
- Right-click Start and open Device Manager.
- Expand Bluetooth.
- Find the physical Bluetooth radio. It may be named Intel, Realtek, MediaTek, Qualcomm, Broadcom, or similarly.
- Do not mistake Microsoft Bluetooth Enumerator, Microsoft Bluetooth LE Enumerator, or Bluetooth Device (RFCOMM Protocol TDI) for the radio itself.
- Right-click the physical adapter, choose Properties, and open the Advanced tab.
- Under Bluetooth Radio Information, read the LMP value.
The LMP value maps to the highest Bluetooth Core Specification the radio fully supports. It is useful for identifying Bluetooth capability, but it is not a codec list. Bluetooth 5.2, 5.3, or 5.4 does not automatically mean that LDAC, aptX HD, aptX Adaptive, or LE Audio will work. Radio implementation, firmware, Windows drivers, and the audio stack still matter. See Microsoft’s Bluetooth-version and LMP instructions.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesFor a quick adapter inventory, PowerShell can show present Bluetooth-class devices:
Get-PnpDevice -Class Bluetooth -PresentOnly | Format-Table Status, FriendlyName, InstanceId -AutoSizeThis command identifies devices and driver entries; it does not report whether the active audio connection is using SBC, AAC, aptX, or another codec. Microsoft’s Get-PnpDevice documentation describes the command.
Step 3: Check whether the PC supports Bluetooth LE Audio
LE Audio is separate from classic Bluetooth A2DP. Classic stereo playback normally uses A2DP, while LE Audio uses Bluetooth LE audio profiles such as BAP, TMAP, and HAP and Microsoft’s implementation uses the LC3 codec.
- Open Settings.
- Go to Bluetooth & devices > Devices.
- Look under Device settings for Use LE Audio when available.
- Turn the setting on if your PC and audio device are compatible.
Microsoft says Windows 11 version 22H2 or newer is required for LE Audio. If the setting is missing, Windows does not currently expose LE Audio support on that PC, potentially because of unsupported hardware or missing or incompatible Bluetooth and audio drivers. Windows 11 version 21H2 does not support LE Audio according to Microsoft’s LE Audio support guide.
Recommended Free Tools
The toggle is not proof that LC3 is currently active. The PC, its drivers, and the connected headphones or earbuds must all support LE Audio, and the devices must successfully negotiate an LE Audio connection. Also, a product described as having Bluetooth LE does not necessarily support Bluetooth LE Audio. Check the exact headset specification for the words Bluetooth LE Audio or the TMAP profile.
Step 4: Check the codecs advertised by the headphones
The most dependable source for the headset’s advertised codecs is the manufacturer’s product page, technical specification, manual, or companion application. Verify the exact model number, generation, and regional variant. Codec support can differ between otherwise similar products.
Look for entries such as:
- SBC
- AAC
- aptX or aptX Classic
- aptX HD
- aptX Adaptive or aptX Lossless
- LDAC
- Bluetooth LE Audio or LC3
A phone companion app may also show or let you select a codec, but that setting may apply only to the phone connection. It is not proof that the Windows Bluetooth driver exposes the same codec.
Step 5: See the codec Windows actually selected
Windows Settings does not normally expose a simple current-codec readout for classic Bluetooth audio. The most practical purpose-built option identified for this task is Bluetooth Tweaker from Luculent Systems. Its product page says it can show both the codecs supported by a connected headphone and the codec Windows selected.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Using Bluetooth Tweaker
- Connect the Bluetooth headphones, earbuds, or speaker to Windows 11.
- Make sure it is the active playback device.
- Start ordinary audio playback. This ensures that the relevant audio connection is active.
- Install and open Bluetooth Tweaker.
- Select the connected device in the left pane.
- Click Refresh CODEC Information.
- Compare the separate information for CODEC supported by device and CODEC selected by Windows.
This distinction is the answer most troubleshooting guides miss. The supported-codec list tells you what the headset advertises. The selected-codec field tells you what Windows negotiated for that connection at that moment.
Rank #3
- 2-IN-1 HEADPHONES & WIRELESS SPEAKER Enjoy private listening in headphone mode or rotate the earcups to switch into Bluetooth speaker mode and share your music with friends and family. A unique design that combines two devices in one.
- POWERFUL SOUND WITH 3 EQ MODES Dual 40mm dynamic drivers deliver deep bass, clear vocals, and balanced audio. Choose between Bass Boost, Balanced, or High Definition sound modes to match your music, movies, and daily listening preferences.
- BLUETOOTH 5.3 & TF CARD PLAYBACK Experience a fast and stable wireless connection up to 33 feet. Insert a TF card and enjoy your favorite music without needing a phone, making it perfect for travel, workouts, and everyday use.
- CLEAR CALLS & ALL-DAY COMFORT Built-in microphone supports hands-free calling while soft protein leather ear cushions, memory foam padding, and an adjustable headband provide lasting comfort for work, study, travel, and entertainment.
- 18 HOURS PLAYTIME & PREMIUM GIFT PACKAGE Recharge with modern USB-C charging and enjoy extended listening. Includes a premium carrying case and elegant retail packaging, making it a thoughtful gift for men, women, teens, students, and music lovers.
Bluetooth Tweaker requirements and limitations
- Windows 10 or Windows 11 x64.
- The Windows inbox Bluetooth stack.
- Administrator privileges to install and remove the software.
- Internet access for trial-license retrieval and purchasing.
- Third-party Bluetooth stacks are not supported by the vendor.
- The trial lasts seven days and checks codec information for only one Bluetooth device during the trial.
The vendor lists version 1.4.9 for x64 Windows 10/11. Its published version history officially lists support through Windows 11 version 25H2. Support for Windows 11 version 26H1 is not verified in that published list, so treat compatibility with 26H1 as unconfirmed rather than guaranteed. Use the vendor’s download page, version history, and FAQ for current requirements.
Why Bluetooth Tweaker may show no codec information
If Refresh CODEC Information returns an error or a blank result, use this sequence:
- Confirm that the headphones are connected and selected as the Windows playback output.
- Start audio playback.
- Leave Bluetooth Tweaker open with the device selected.
- Open Settings > Bluetooth & devices > Devices.
- Disconnect the target device, then reconnect it.
- Return to Bluetooth Tweaker and click Refresh CODEC Information again.
- Install the latest version of the utility and update the Bluetooth driver from the PC or adapter manufacturer.
The vendor says version 1.4.9 addressed a refresh problem associated with newer Intel Bluetooth adapters. If the result remains blank, report the codec as not exposed or unverified. Do not infer SBC from a blank field, a Windows sample-rate setting, or the sound quality.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →If the Bluetooth driver may be missing, outdated, or incompatible, Outbyte Driver Updater is an optional way to check for available Windows driver updates, but confirm any result against the PC or adapter manufacturer’s driver.
The HFP microphone trap: why the codec or quality changes
Classic Bluetooth uses different profiles for different jobs:
- A2DP: stereo media playback.
- HFP: two-way voice audio when the headset microphone is required.
When Teams, Zoom, Discord, a browser, a game, or another application opens the headset microphone—or creates a communications-category audio stream—Windows can switch the device from A2DP to HFP. Classic HFP supports mono playback and capture, using CVSD narrowband speech at 8 kHz or mSBC wideband speech at 16 kHz. The result is often muffled or telephone-like audio. When the microphone closes, Windows may switch back to A2DP.
For a fair codec check:
- Close applications that may be using the headset microphone.
- Check Windows privacy settings or the application’s audio settings if microphone access appears to remain active.
- Select the stereo playback endpoint rather than a headset communications endpoint where both are listed.
- Start music or another ordinary stereo stream.
- Refresh the codec information while the microphone is not in use.
LE Audio can behave differently. On compatible hardware, drivers, Windows builds, and headsets, Windows 11 can maintain stereo playback while the microphone is active. Microsoft documents enhanced stereo microphone behavior for Windows 11 version 24H2 and build 26100.4484 or later on compatible systems, but this behavior is not universal. See Microsoft’s LE Audio quality-settings guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why Windows uses SBC instead of AAC or aptX
If a diagnostic tool confirms SBC, possible explanations include:
- The headset does not advertise AAC or aptX for this connection.
- The PC’s Bluetooth radio or OEM driver does not expose the codec.
- The headset is in HFP call mode rather than A2DP stereo mode.
- Audio was not playing when the connection was inspected.
- The headset supports the codec on certain phones or branded transmitters but not through the standard Windows driver path.
- The headset’s supported-codec list is being confused with Windows’ selected-codec result.
Try the following recovery steps:
- Close microphone-using applications and begin ordinary stereo playback.
- Disconnect and reconnect the headset.
- Forget and re-pair the headset if reconnection does not change the result.
- Install the latest Bluetooth and audio drivers supplied by the PC manufacturer. For a USB adapter, check the adapter manufacturer as well.
- Compare the exact headset specification with Microsoft’s Windows codec matrix.
- Refresh the codec information again.
If Windows still selects SBC, that may be the correct result for the installed driver and hardware combination. A headset working with LDAC or aptX HD on a phone does not prove that the standard Windows path supports those codecs.
Does the Windows audio format reveal the Bluetooth codec?
No. The format shown in the Windows sound device properties—such as 2-channel, 16-bit, 48,000 Hz—describes the Windows audio endpoint format. It does not definitively identify whether the Bluetooth transport is using SBC, AAC, aptX, aptX Adaptive, or another codec.
Microsoft’s Bluetooth audio troubleshooting page may recommend changing an audio format as a troubleshooting step. That setting should not be treated as a Bluetooth codec selector or codec checker.
Rank #4
- 【40MM DRIVER & 3 MUSIC MODES】Picun B8 bluetooth headphones are designed for audiophiles, equipped with dual 40mm dynamic sound units and 3 EQ modes, providing you with stereo high-definition sound quality while balancing bass and mid to high pitch enhancement in more detail. Simply press the EQ button twice to cycle between Pop/Bass boost/Rock modes and enjoy your music time!
- 【120 HOURS OF MUSIC TIME】Challenge 30 days without charging! Picun headphones wireless bluetooth have a built-in 1000mAh battery can continually play more than 120 hours after one fully charge. Listening to music for 4 hours a day allows for 30 days without charging, making them perfect for travel, school, fitness, commuting, watching movies, playing games, etc., saving the trouble of finding charging cables everywhere. (Press the power button 3 times to turn on/off the low latency mode.)
- 【COMFORTABLE & FOLDABLE】Our bluetooth headphones over the ear are made of skin friendly PU leather and highly elastic sponge, providing breathable and comfortable wear for a long time; The Bluetooth headset's adjustable headband and 60° rotating earmuff design make it easy to adapt to all sizes of heads without pain. suitable for all age groups, and the perfect gift for Back to School, Christmas, Valentine's Day, etc.
- 【BT 5.3 & HANDS-FREE CALLS】Equipped with the latest Bluetooth 5.3 chip, Picun B8 bluetooth headphones has a faster and more stable transmission range, up to 33 feet. Featuring unique touch control and built-in microphone, our wireless headphones are easy to operate and supporting hands-free calls. (Short touch once to answer, short touch three times to wake up/turn off the voice assistant, touch three seconds to reject the call.)
- 【LIFETIME USER SUPPORT】In the box you’ll find a foldable deep bass headphone, a 3.5mm audio cable, a USB charging cable, and a user manual. Picun promises to provide a one-year refund guarantee and a two-year warranty, along with lifelong worry-free user support. If you have any questions about the product, please feel free to contact us and we will reply within 12 hours.
Can BluetoothView, Event Viewer, or PowerShell show the active codec?
They may help identify devices, drivers, endpoints, or connection events, but they are not guaranteed end-user codec readers. Codec fields may be missing, and a log entry that mentions Bluetooth does not necessarily identify the negotiated A2DP codec.
Microsoft does expose codec capability and configured-codec information through low-level A2DP sideband interfaces intended for Bluetooth and audio driver development. These interfaces are not ordinary PowerShell commands. The relevant Microsoft documentation covers A2DP sideband definitions and the A2DP sideband audio architecture. For ordinary users, a purpose-built diagnostic tool or the status display of a dedicated transmitter is more direct.
Can Windows 11 use LDAC, aptX HD, or aptX Low Latency?
Not through the generic Microsoft inbox codec table. Microsoft’s documented Windows 11 A2DP list includes SBC, AAC, aptX Classic, and selected aptX Adaptive systems; it does not list LDAC, aptX HD, or aptX Low Latency as universal inbox codecs.
There are two separate ways to add a different codec path:
Use an alternative A2DP driver
The vendor’s Alternative A2DP Driver replaces the Windows inbox A2DP driver and lists support for codecs including aptX HD, aptX Low Latency, and LDAC, in addition to SBC, AAC, and aptX Classic. This is a system-driver change, not merely a diagnostic application. Consider it only when you want to change the audio transport and accept the additional compatibility and troubleshooting responsibilities.
| Codec | Standard Windows 11 driver, according to the vendor comparison | Alternative A2DP Driver |
|---|---|---|
| SBC | Yes | Yes |
| AAC | Yes | Yes |
| aptX Classic | Yes | Yes |
| aptX HD | No in the generic table | Yes |
| aptX Low Latency | No in the generic table | Yes |
| LDAC | No in the generic table | Yes |
Use a dedicated USB Bluetooth transmitter
A USB transmitter can bypass the PC’s normal Bluetooth audio path and handle codec negotiation itself. The transmitter appears to Windows as a separate USB audio device, and its companion application, firmware, or LED may show the selected codec. The headphones must still support the same codec.
Examples include Creative’s BT-W6, which Creative documents as supporting aptX, aptX HD, aptX Adaptive, aptX Lossless, SBC, and LC3, with codec status available through its app and LED. Sennheiser’s BTD 700 is another example that the manufacturer documents for aptX, aptX Adaptive, aptX Lossless, SBC, and LC3 on Windows 10 or later. These are examples of a product category, not universal recommendations.
A transmitter costs extra, may change microphone behavior, and may require vendor software or firmware. It can nevertheless be preferable when a specific codec, predictable negotiation, or visible codec status matters more than using the PC’s built-in Bluetooth radio.
What to do when the LE Audio setting is missing
If Use LE Audio when available does not appear, Windows says that the PC does not currently expose compatible LE Audio support. Work through these checks:
- Confirm the Windows version with
winver. - Install Bluetooth and audio drivers from the computer manufacturer, not only generic drivers.
- Check whether the installed Bluetooth radio is the original factory-supported radio.
- Verify that the headset or earbuds support Bluetooth LE Audio, not merely Bluetooth LE.
- Do not assume that a Bluetooth 5.x label guarantees LE Audio.
If the setting appears after a driver update, that still does not prove that LC3 is being used with a particular headset. Both sides must support LE Audio and successfully negotiate it.
Quick decision guide
| Your goal | Best method | What it can prove |
|---|---|---|
| See Microsoft’s documented Windows capability | Check the Windows version and Microsoft’s classic-audio codec matrix. | The documented inbox baseline, with version and hardware qualifications. |
| Check the Bluetooth radio | Device Manager > Bluetooth > radio Properties > Advanced. | The physical adapter and LMP; not the codec. |
| Check LE Audio capability | Settings > Bluetooth & devices > Devices. | Whether Windows exposes the LE Audio setting. |
| Check headset advertisements | Exact manufacturer specification, manual, companion app, or Bluetooth Tweaker. | What the headset reports as supported. |
| Check the active classic codec | Bluetooth Tweaker while stereo playback is active. | The device-supported codecs and codec selected by Windows, when exposed. |
| Force or obtain LDAC, aptX HD, or similar | Alternative A2DP driver or a compatible USB transmitter. | A different codec path, subject to the product, driver, and headset. |
Frequently Asked Questions
Does Windows 11 support AAC Bluetooth audio?
Yes. Microsoft documents AAC support for Windows 11 version 21H2 and later, but both the PC’s Windows audio path and the connected Bluetooth device must support AAC. The active codec still needs to be verified separately.
Best Value
- Optional 6 Music Modes: Adopted most advanced dual 40mm dynamic sound unit and 6 EQ modes, BERIBES updated headphones wireless bluetooth black were born for audiophiles. Simply switch the headphone between balanced sound, extra powerful bass and mid treble enhancement modes. No matter you prefer rock, Jazz, Rhythm & Blues or classic music, BERIBES has always been committed to providing our customers with good sound quality as the focal point of our engineering.
- 65 Hours Playtime: Low power consumption technology applied, BERIBES bluetooth headphones with built-in 500mAh battery can continually play more than 65 hours, standby more than 950 hours after one fully charge. By included 3.5mm audio cable, the wireless headphones over ear can be easily switched to wired mode when powers off. No power shortage problem anymore.
- All Day Comfort: Made by premium materials, 0.38lb BERIBES over the ear headphones wireless bluetooth for work are the most lightweight headphones in the market. Adjustable headband makes it easy to fit all sizes heads without pains. Softer and more comfortable memory protein earmuffs protect your ears in long term using.
- Latest Bluetooth 6.0 and Microphone: Carrying latest Bluetooth 6.0chip, after booting, 1-3 seconds to quickly pair bluetooth. Beribes bluetooth headphones with microphone has faster and more stable transmitter range up to 33ft. Two smart devices can be connected to Beribes over-ear headphones at the same time, makes you able to pick up a call from your phones when watching movie on your pad without switching.（There are updates for both the old and new Bluetooth versions, but this will not affect the quality of the product or its normal use.）
- Packaging Component: Package include a Foldable Deep Bass Headphone, 3.5MM Audio Cable, Type-c Charging Cable and User Manual.
Does Windows 11 support aptX?
Microsoft documents aptX Classic from Windows 11 version 21H2 and aptX Adaptive from version 24H2 on selected systems with compatible Qualcomm Bluetooth radios. This does not guarantee aptX on every Windows 11 PC or adapter.
Does Windows 11 support LDAC or aptX HD?
LDAC and aptX HD are not listed in Microsoft’s generic inbox Windows 11 A2DP codec table. They may be available through a vendor-specific driver or a dedicated USB Bluetooth transmitter, which is a separate audio path.
Does Bluetooth 5.3 guarantee a high-quality Bluetooth codec?
No. Bluetooth version and codec support are related only indirectly. The radio implementation, firmware, Windows driver, audio stack, headset, and negotiated profile all affect codec availability.
Why does my headset use SBC instead of aptX or AAC?
Possible causes include missing host-driver support, a headset variant that does not advertise the codec to Windows, HFP microphone mode, or a connection that has not completed negotiation. Close microphone-using apps, start stereo playback, reconnect the headset, update the driver, and check the result with a codec-aware tool.
Why does Bluetooth audio become muffled when I open Discord, Teams, or Zoom?
With classic Bluetooth, opening the headset microphone generally switches Windows from stereo A2DP to mono HFP audio. Closing the microphone may allow Windows to return to A2DP. Compatible LE Audio systems can behave differently.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesDoes the Windows sample-rate setting show the Bluetooth codec?
No. A setting such as 2-channel, 16-bit, 48,000 Hz describes the Windows audio endpoint format, not the Bluetooth transport codec.
How do I check whether LC3 is supported?
Go to Settings > Bluetooth & devices > Devices and look for Use LE Audio when available. Also verify that the headset specification explicitly lists Bluetooth LE Audio or LC3. The setting alone does not prove that LC3 is active on the current connection.
Can PowerShell show the active Bluetooth codec?
Microsoft’s documented Get-PnpDevice command can list Bluetooth devices and adapters, but it does not directly print the negotiated A2DP codec. Microsoft’s codec interfaces are low-level driver-development interfaces rather than normal end-user PowerShell commands.
Is Bluetooth Tweaker free?
Bluetooth Tweaker is third-party software with a seven-day trial. The vendor lists a one-device codec-information limitation during the trial, x64 Windows requirements, the inbox Bluetooth stack requirement, administrator privileges for installation, and internet access for licensing. Download it from the vendor’s official site and review its current compatibility information.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What if Bluetooth Tweaker shows no codec information?
Confirm that the headset is connected and selected for playback, start audio, disconnect and reconnect it while the utility remains open, then refresh the codec information. Update the utility and Bluetooth driver if necessary. If it remains blank, treat the codec as unverified rather than guessing from the sample rate or audio quality.
The Bottom Line
The reliable answer is a combination of checks: use Microsoft’s codec matrix for the Windows baseline, Device Manager for the actual Bluetooth radio, the LE Audio setting for LC3 capability, and the headset’s exact specification for advertised codecs. To see what classic Bluetooth codec is being used right now, inspect the active connection with a codec-aware tool such as Bluetooth Tweaker while ordinary stereo playback is running and the microphone is closed. If Windows still chooses SBC, the limitation is usually the intersection of the PC driver, Bluetooth hardware, headset, and current A2DP/HFP mode—not the headset’s phone-side codec list.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
