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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-06-13T16:31:59+00:00

    There's something you need to keep in mind: Microsoft does not often discuss its engineering challenges with the public.  It is possible that the development team has not pinned down the issue yet; it is estimated that Windows 10 is approximately 50 million lines of code and sifting through code like that is not easy.  It's also possible that the onus has been placed on individual hardware manufacturers to update their drivers, and they were either not consulted properly or are still scrambling to get their devices to work with 1803. 

    Whatever the case, for a Microsoft O/S, wait and see is the only approach.  You will continue to get high-priority security updates; 1803 was more of a feature release than anything else so unless you had a specific feature from 1803 you were waiting for, I wouldn't put it back on and wait for the next feature release (keep in mind this is not advice from Microsoft and I'm not a Microsoft employee, just someone who's spent 12 years in the IT world).  Your best chance is to mention Bluetooth in the Roll Back notes because of the customer-facing feedback, it has the highest likelihood of being seen by actual engineers and specifically by QA.  Generally people like to know when they screw up so bad as to render their pride and joy they worked on completely unusable.

    All sane and rational advice. However, a Microsoft support rep came on this thread and requested  information from people here. The MS rep has not explained why they wanted this information, nor  have they responded since. That is annoying and highly unprofessional. I have been using Windows since 3.1. I have never lost functionality because of MS before. Not being able to adjust volume is a complete joke. I have no problem if it is a tough fix for MS. But the very least the rep could have done is said so.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-06-13T12:20:58+00:00

    There's something you need to keep in mind: Microsoft does not often discuss its engineering challenges with the public.  It is possible that the development team has not pinned down the issue yet; it is estimated that Windows 10 is approximately 50 million lines of code and sifting through code like that is not easy.  It's also possible that the onus has been placed on individual hardware manufacturers to update their drivers, and they were either not consulted properly or are still scrambling to get their devices to work with 1803. 

    Whatever the case, for a Microsoft O/S, wait and see is the only approach.  You will continue to get high-priority security updates; 1803 was more of a feature release than anything else so unless you had a specific feature from 1803 you were waiting for, I wouldn't put it back on and wait for the next feature release (keep in mind this is not advice from Microsoft and I'm not a Microsoft employee, just someone who's spent 12 years in the IT world).  Your best chance is to mention Bluetooth in the Roll Back notes because of the customer-facing feedback, it has the highest likelihood of being seen by actual engineers and specifically by QA.  Generally people like to know when they screw up so bad as to render their pride and joy they worked on completely unusable.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-06-13T12:15:13+00:00

    What's the point? A Microsoft support rep came on here a month ago asking for people's specs etc. Many people provided this info and received no reply from the rep. Why ask the question if you are not going to reply? Highly unprofessional.

    Was this answer helpful?

    0 comments