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
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
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

161 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-08-26T04:47:44+00:00

    Microsoft broke AVCRP in Bluetooth, which is probably related to your problem. AVCRP is a specification that was implemented early on in BT devices. The functions specifications haven't changed. I'll bet your device works just fine if you were to use either a iPhone or Android phone.  Everyone at MS is ignoring this problem and playing stupid. It is not a driver/software issue it's a MS issue. 

    My device now works just fine including with its remote control functionality (FWD, Pause etc) after updating my BT UART driver. Before then I had both problems with remote control functionality (AVCRP) and Audio breakup when using stereo over Bluetooth (A2DP) but NOT Handsfree Audio Profile (Mono) audio (HFP). I'm reluctant to accept there are problems with how 1803 handles those profiles because the new BT UART driver eliminated all the issues I was having.

    I see here https://en.wikipedia.org/wiki/List\_of\_Bluetooth\_profiles that AVRCP took onboard support for Absolute Volume Control when it got to version 1.4 but that Wikipedia link shows there have been 2 newer revisions since. That said, if companies that have designed BT Speakers to work with AVRCP 1.3 and below, now find Win 10 ver 1803 stops them working how they always have done, thats definitely an issue to take up with Microsoft through their channels. Windows has supported A2DP, AVRCP and HFP since Windows 7/Vista however and according to this page https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/general-bluetooth-support-in-windows Windows 10 ver 1803 now supports AVRCP 1.61 (although no word on what build it jumped up from 1.3 on).

    That's great for you, but not for the people like me for whom it's not working on 1803 and it was before the "Upgrade". There is no fix for the Broadcom drivers. If you go to the Broadcom site this is their response: 

    Windows drivers for Broadcom Bluetooth devices are no longer posted here. They should be available through Microsoft's Windows Update service. If drivers were not downloaded automatically by Windows Update, use Device Manager to refresh the driver from Windows Update, or contact the device manufacturer.

    If I go to the device MFG (ASUS) they tell me to go to either Microsoft, or Broadcom, as it's a Broadcom chipset.

    Like I said it's a MS problem as it was working before 1803 and not now.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-08-26T04:27:38+00:00

    Microsoft broke AVCRP in Bluetooth, which is probably related to your problem. AVCRP is a specification that was implemented early on in BT devices. The functions specifications haven't changed. I'll bet your device works just fine if you were to use either a iPhone or Android phone.  Everyone at MS is ignoring this problem and playing stupid. It is not a driver/software issue it's a MS issue. 

    My device now works just fine including with its remote control functionality (FWD, Pause etc) after updating my BT UART driver. Before then I had both problems with remote control functionality (AVCRP) and Audio breakup when using stereo over Bluetooth (A2DP) but NOT Handsfree Audio Profile (Mono) audio (HFP). I'm reluctant to accept there are problems with how 1803 handles those profiles because the new BT UART driver eliminated all the issues I was having.

    I see here https://en.wikipedia.org/wiki/List\_of\_Bluetooth\_profiles that AVRCP took onboard support for Absolute Volume Control when it got to version 1.4 but that Wikipedia link shows there have been 2 newer revisions since. That said, if companies that have designed BT Speakers to work with AVRCP 1.3 and below, now find Win 10 ver 1803 stops them working how they always have done, thats definitely an issue to take up with Microsoft through their channels. Windows has supported A2DP, AVRCP and HFP since Windows 7/Vista however and according to this page https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/general-bluetooth-support-in-windows Windows 10 ver 1803 now supports AVRCP 1.6.1 (although no word on what build it jumped up from 1.3 on).

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-08-25T22:12:09+00:00

    Well, that's the problem in the first place - the updates from windows.

    As I said, there are numerous bluetooth speakers that do not have this "absolute volume" feature and because of the hardware they have it will not be possible to implement it at all ?!

    Therefore, if Windows decides to upgrade the bluetooth to the current standards, I honestly think that Microsoft at least should give us some kind of legacy support or to enable it in some way for older devices (the same way like running an older software in compatibility mode). 

    I think that's the golden rule in IT development (unless a totally new technology is discovered): you don't cut the compatibility with older stuff.

    What am I supposed to do now? Contact Edifier for what? They just made a product with the standards of that time. How are they supposed to "update" it now?

    I have two different laptops (Acer and Asus ~2015) and both have now the same problem after 1803 update. I guess it's either Acer/Asus/Edifier problem but not Microsoft, right?

    Android did the same with the bluetooth, but at least they let us still use the legacy mode for those who do not want to upgrade their peripherals just because the new standard requires.

    This has nothing to do with new vs old or anything like that, this is just an example of MS not adhering to the spec properly, trust me, I do driver development, MS sucks at adhering to industry standard specs.

    Was this answer helpful?

    0 comments