Bluetooth not working properly on Windows 11 24H2

Anonymous
2024-12-04T00:07:58+00:00

So i have been having this issue for a while on my PC desktop currently running the latest release of W11, 24H2.

Basically whenever i try to connect any device to my bluetooth, the device gets connected, but when i try to actually use it, i get no audio coming from it, at all, or if there is, it's just really occasional and it only lasts a fraction of a second, and it's low, jittery and stuttery, like it was struggling with signal being low, and it's indeed what's actually happening i think, as whenever i go closer with my head to where the bluetooth drivers should actually be located and the signal coming from, that is, back of the pc, or motherboard, the signal is way stronger, but even so, sometimes even so close it gets really sputtering and laggy, like a low signal.

It's definitely not normal behaviour, i have three different devices that can work through bluetooth, and all of them have issues on my pc when trying to use bluetooth.

To test this out, i tried connecting them to a laptop that still has W11 23H2, and they all work without an issue.

By process of elimination i think it's clear that the problem is either my current release of Windows, or my motherboard, which is the device producing the bluetooth signal.

I tried many different things, like installing bluetooth drivers provided by Intel, or drivers directly taken from my motherboard website, which are dated July this year, but all the devices i own are older than that. i tried editing bluetooth keys in the file register to allow Windows to use other bluetooth codecs, reinstalling the devices from device management, i used third party softwares to allow different codecs, and eventually, even doing a clean Windows 11 reinstall, nothing works.

I've had other issues with 24h2 before, not bluetooth related, but other issues so i assume that for some aspects, the release still has to be tweaked accordingly to some things and drivers, and especially considering that i have no issues on my laptop running 23h2

Or...my motherboard is the problem, but it's quite a new one, designed to run AM5 chipset CPUs by AMD which is the newest generation there is, i checked compatibility and the version of bluetooth shouldn't be an issue. My motherboad's bluetooth gen is 5.2, and the device i'm interested to connect is 5.1, i'm not an expert but i don't think there should be any issue

Even more specifically, my motherboard is an Asus x670e Tuf Gaming Plus Wifi

The device not working properly is a pair of earbuds, JBL Wave Flex

I managed to find online some issues of compatibility between these earbuds and windows 11, but they were all old discussions prior to 24h2, and most importantly, the device works on my laptop, as well as on my phone, so they are definitely not the problem.

really don't know what to do at this point haha. Can you guys help me?

Windows for home | Windows 11 | 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.

0 comments No comments

66 answers

Sort by: Most helpful
  1. Anonymous
    2024-12-05T21:06:01+00:00

    Thank you for trying to help.

    Unfortunately none of the fixes listed above seem to bring to a solution.

    The only thing left to be tried is using a usb dongle, however according to the other reply to this post i'll doubt it'll work, but who knows, each machine is different.

    I'll buy one and i'll let you know in the following days.

    The only thing i didn't exactly do as described was:

    When checking services.msc, one of the services you listed was either missing, or was called in a different way: i managed to find "BluetoothUserService_XXXX", but not "UserSupportService", maybe that's the one and on some PCs it's just called differently, i don't know, and i also wasn't able to switch to automatic for that specific service. It says "incorrect parameter" and that's it, it sticks to manual.

    No troubles about the others two instead, i found them both and switched to automatic.

    It didn't do anything and i doubt that even if the service i didn't manage to find/switch was set properly it would solve anything at this point, but just in case i'm telling you every detail.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-09T10:21:21+00:00

    I have same problem. Brand new headset really getting over the whole thing. Trying to watch webinar is a joke

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-12-07T19:48:48+00:00

    Hi,

    i've resolved upgrading Intel bluetooth drivers to at least to v. 23.60 prior to upgrade to 24h2.

    It can be downloaded directly from Intel webiste.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-12-22T17:35:22+00:00

    Hi,

    i've resolved upgrading Intel bluetooth drivers to at least to v. 23.60 prior to upgrade to 24h2.

    It can be downloaded directly from Intel webiste.

    This also slighlty solved the issue, but not completely, the only thing i got was more signal range with such older drivers, but it was still laggy and bad audio, and the range was still quite poor. But it did something redargless. My ultimate solution was to use an usb adapter instead of the motherboard.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-12-22T17:32:20+00:00

    Hey, it's been a while.

    After countless tries eventually i solved by switching bluetooth source from motherboard to an external usb adapter.

    At this point it could really be anything, either my motherboard having the bluetooth faulty in some way, or just Windows 24h2, according to some users down here as well; i would probably need more PCs running the latest release to know for sure. I'll report the bug to Microsoft nonetheless.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments