With 2004 patch its even worse. Now my bluetooth speakers cant even reconnect. They dont care. It’s the only OS available. You have to use it no matter how buggy it is.
Having Bluetooth Stuttering Issues on Windows 10
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
As of recent, when connecting any pair of bluetooth headphones or devices, I would get stuttering problems where when using bluetooth headphones, the audio would frequently cut in and out randomly, and it would frequently disconnect, even when it was fully charged. And yes, I've tried to fix the issue by disabling audio enhancements, but it hasn't helped at all. Additionally, I've had problems with other bluetooth devices where they would also frequently disconnect. Is there a fix to these problems?
Windows for home | Windows 10 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
166 answers
Sort by: Newest
-
Anonymous
2020-07-14T17:41:29+00:00 -
Anonymous
2020-07-14T14:02:47+00:00 It's so interesting that this thread has been going on 2 years, is monitored by MS, and they still can't fix such a simple, universal problem. Do better MS.
-
Anonymous
2020-07-13T19:47:06+00:00 I ran the "fix", it reported a "radio" fixed, but it did not fix the stuttering
-
Anonymous
2020-07-12T03:15:21+00:00 So it seems this is a general issue with Windows' Bluetooth drivers/stack?
I got myself the Bose QC35 II and Sony WH-1000XM3 and both have the same issues.
No issues when connected to a phone.
-
Anonymous
2020-07-06T00:11:45+00:00 I'd suggest not holding your breath for a fix to this problem via MS Feature Update 2004. My observation is that this problem only began for me after I had installed that feature on the laptop I run.