What you need to know
- A recent cumulative update for the Windows 10 May 2019 Update has broken Bluetooth audio for some users.
- Microsoft recently published a support document confirming the issue with update KB4505903.
- A workaround is available if you've experienced this issue.
If you've noticed that you can't connect Bluetooth speakers or headphones to your PC since installing a cumulative update for the Windows 10 May 2019 Update in July, you're not alone. Microsoft recently published a support document (opens in new tab) (via Windows Latest) that confirms an issue playing audio over Bluetooth after installing cumulative update KB4505903, which was released in July. The bug appears to affect PCs that have their own internal speakers.
THere are a few ways in which you might experience this bug. Here's how Microsoft describes the issue:
- A Bluetooth speaker can't connect to the computer.
- A Bluetooth speaker can connect to the computer. However, the speaker output sounds noisy (bad quality).
- A Bluetooth speaker can connect to the computer. However, the sound is generated by the internal speaker instead of the Bluetooth device.
Fortunately, there is a workaround available. If your PC is impacted, you can use the System File Checker (SFC) tool to repair missing and corrupted system files. From Microsoft:
- Open the command console by using administrative authority.
- At the command prompt, type the following command, and then press Enter:
- sfc /scannow
- After the process is finished, restart the computer.
Microsoft has since released a Patch Tuesday update for the month of August, but it's unclear if that cumulative update corrects the issue. If you're still running a Windows 10 May 2019 Update on KB4505903 (build 18362.267), you can use the above workaround to get Bluetooth audio working correctly again.
Windows Central Newsletter
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.