Windows 10 version 1803 April 2018 update broke bluetooth volume control.

Anonymous
2018-05-02T03:45:36+00:00

My pc automatically updated to the April 2018 update, version 1803.

After restarting my PC I notice my volume control via Bluetooth will not adjust the volume anymore. Speakers are Creative T30

However if I am in WMP or iTunes the slider changes the volume.

If I use my Microsoft keyboard volume keys or the speaker Icon on the taskbar the slider moves but no volume is changed. However if I slide all the way left the volume turns off.

Anyone else having issues.

Any ideas or is a Microsoft patch already required?

I have tried uninstalling driver and rebooting but no change.

Cheers

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.

0 comments No comments
Answer accepted by question author
Anonymous
2018-11-14T20:40:54+00:00

Microsoft is aware of reports that the Absolute Volume feature is incompatible with some Bluetooth devices, resulting in the inability to adjust the Bluetooth device’s volume.  If you are experiencing this issue, neither the volume slider in the taskbar, nor the device’s volume controls have any effect on volume.

To resolve this issue, first make sure you’ve installed the latest Windows Updates.  A solution was included in the October 24, 2018—KB4462933 (OS Build 17134.376) update for Windows 10 version 1803.  To check for updates, select the Start button, and then go to Settings> Update & security> Windows Update, and select Check for updates.

Three devices that are known to experience the issue will automatically have the Absolute Volume feature disabled and should no longer experience the issue once you’ve installed KB4462933:  Creative T30 Wireless Speakers, Edifier R2000 DB, and the JBL Go.

For other Bluetooth devices, once you’ve installed KB4462933 or once you've installed Windows 10 version 1809, you can resolve the issue by disabling Absolute Volume manually by making a change in the registry.  (Warning:  Serious problems might occur if you modify the registry incorrectly. For added protection, back up the registry before attempting to modify it.)

To disable the Absolute Volume feature manually:

1.     In the Search box, type cmd.  Right-click Command Prompt in the Search results and select Run as administrator.

2.     In the Command Prompt window, type the following command:

reg add HKLM\SYSTEM\ControlSet001\Control\Bluetooth\Audio\AVRCP\CT /v DisableAbsoluteVolume /t REG_DWORD /d 1 /f

To re-enable the Absolute Volume feature:

1.     In the Search box, type cmd.  Right-click Command Prompt in the Search results and select Run as administrator.

2.     In the Command Prompt window, type the following command:

reg add HKLM\SYSTEM\ControlSet001\Control\Bluetooth\Audio\AVRCP\CT /v DisableAbsoluteVolume /t REG_DWORD /d 0 /f

You may need to restart Windows for the registry change to take effect.

Was this answer helpful?

50+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2018-05-22T02:09:21+00:00

Windows bluetooth dev here

If anyone can't control their BT speaker/headphones volume from the PC after the update, can you share a product link to what device you're using?

We added "absolute volume" in the last update which lets the Windows volume slider directly control the local volume of BT speakers/headphones who support it.

Sorry to hear this is happening, I already made a note to look into the Creative T30/T50, Edifier 1700BT, JBL Bar 5.1, we want this to work as best as possible so let me know the devices you're having issues with and we'll look into it.

Thanks guys!

Was this answer helpful?

4 people found this answer helpful.
0 comments No comments

161 additional answers

Sort by: Newest
  1. Anonymous
    2018-08-06T04:45:35+00:00

    If that's the case, why does using legacy Bluetooth drivers solve the issue for some?

    I don't know enough about how it works but the process of installing the drivers performs some sort of forced/override function. I recall when I found the newest drivers for my BT hardware (which were released around the same time as ver 1803) that the notes with them made reference to this. The bottom line is that installing those Bluetooth UART (Universal Asynchronous Receiver Transmitter) drivers on my tablet fixed the issue for me. Different BT devices use different drivers and different ways of working though and someone earlier mentioned their BT receiver doesn't even have a UART driver - perhaps its called something else with newer BT hardware?

    Bluetooth Audio device manufacturers shouldn't need to release new drivers for their devices (because they rely on the Bluetooth protocols to work and that's the job of the actual Bluetooth receiver or UART in the computer). So its the right drivers for this that need to be found and installed/reinstalled. The audio device manufacturers should be able to offer some help getting to the bottom of the problem though because the bottom line is this matter stops their equipment from working or at least working with full functionality. It would be worth asking them to see what they have to say and hopefully they can offer a more detailed explanation.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-08-05T22:45:21+00:00

    Let's put it this way. Before 1803 all was well with my BT devices. Now I only can connect and get audio.

    The Manufactures of these headsets don't supply a driver nor should they have to. All their functions work when using either Android or iOS, and I don't have to supply an app to get them to work. The protocol for pause/stop/next track/previous track FF/Rw is a BT specification independent of OS or Manufacturer. Go to www.bluetooth.com they have all the BT specs from 1 to 5.0.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-08-05T21:56:07+00:00

    None will control pause/ff/back/play/stop.

    Before 1803 in device manager there was Windows Bluetooth Protocol Support Driver, after there isn't any.

    There have been huge changes in the way BT Audio works under ver 1803 but the fact all of those functions are working now (after a BT driver update) with my Anker Soundbuds Tag headset tells me it's not strictly an OS issue but a need to have drivers that fully support the hardware with this OS version.

    What do your audio and BT hardware manufacturers have to say about this? Any brand new drivers?

    If that's the case, why does using legacy Bluetooth drivers solve the issue for some?

    Was this answer helpful?

    0 comments No comments