Bluetooth volume broken after Windows 10 1803 update

Anonymous
2018-05-23T19:48:30+00:00

I have a Samsung DA-E670 bluetooth(BT) speaker that I use as my main speakers connected via BT. After the Windows 10 version 1803 update recently, I can no longer adjust the volume of these speakers from the master mixer in the taskbar.

The slider moves but the volume doesn't change unless it's slid to the minimum then it mutes.

The same issue happens on my laptop after this 1803 update.

However, on my new Sennheiser headphones the behaviour has changed differently. Adjusting the volume on the headphones built-in volume control, changes the Windows main mixer volume. I can learn to adjust to this change but I would need to be able to control the volume of my Samsung speakers via Windows like before.

My research points to something about a mismatch of Bluetooth profiles. Has anyone had this issue and if so, are there any work arounds or fixes?

Also, I have been in touch with Microsoft support chat a bunch of times (5 or 6 times) and they have tried everything from;

BT troubleshooter

Re-installing drivers

Updating drivers

Installing bad drivers, breaking the BT

some weird registry and other actions I don't know the details about

[Moved from:  Windows / Windows 10 / Windows update, recovery, & backup]

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
2019-02-13T20:21:11+00:00

Hello guys, 

I also have a problem with my Edifier R2730DB, however I solved the problem by changing a value from 0 to 1 in the registry. 

Follow the steps from this post:

"You should try this fix It worked to me:

  1. Open Windows Registry (regedit.exe).
  2. Jump to  Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Bluetooth\Audio\AVRCP\CT
  3. Create  REG_DWORD  DisableAbsoluteVolume and set it's value to  1.

Important: You need to restart your PC for changes to take affect.

Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar Problem." Quoted from https://social.technet.microsoft.com/Forums/azure/en-US/71e51613-721d-45aa-9b94-34fbce8472bc/bluetooth-volume-problem-after-windows-10-april-2018-update?forum=win10itprosetup

(Check last post of the page).

Hope this solves the problem for you too. Looking forward to actually get a fix from Microsoft with next updates ...

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments

84 additional answers

Sort by: Newest
  1. Anonymous
    2018-06-25T23:49:22+00:00

    I would have loved to stay on 1709 but Microsoft thought it would be great to force us to this buggy build. This forced upgrades needs to stop. We do not like having to reload our system multiple times a year cause MS can't get it right! Never ever had this type of issues with Windows 7 or 8.

    By the why I'm not reloading Windows 10 Fall Update 1709 on this Laptop, downgrading back to Windows 7 Professional. Should have blocked 10 from the get go!!!

    Some of us use our PC for productivity not playing games on it. MS is treating its user like they are running a Tablet, for which we all know is for playing Angry Birds while you poop.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-06-25T02:27:42+00:00

    Thanks for the update, Dildeep. With these results, we've confirmed that the Bluetooth devices are not compatible with the 1803 update. Let's report this to our engineers using Feedback Hub. Feedback items regularly receive Microsoft responses on the submissions in the Feedback app so you can see what we are doing about your feedback. Please revisit frequently to see the status of your feedback items.  

    In order to submit new feedback, please follow these steps:  

    1. On a Windows 10 device, search for “Feedback Hub” in Cortana search, then launch the app.
    2. Navigate to Feedback in the left menu, then press + Add new feedback.
    3. Select the Problem, and share any details you think are relevant, and choose an appropriate category and subcategory.
    4. Important: If possible, reproduce the problem(s) after clicking Begin monitoring (or Start capture) near the end of the form; Stop monitoring when you’re done.
    5. Once you’ve completed the form and monitoring, click Submit.
    6. Click Continue using Feedback Hub.
    7. Click My feedback at the top, then find the item you submitted (it may take a while to appear).
    8. Open the item you submitted, then click Share.
    9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/link>).

    In the meantime, I advise that you go back to 1709 if you want to use your Bluetooth speakers. Here's how to go back: click Startbutton > SettingsUpdate & securityRecoveryand selecting Get startedunder Go back to the previous version of Windows 10. Please note that you can only go back to the previous version within 10 days. In-case that 10 days have already passed, you can follow Andre Da Costa's instructions here on this thread to get 1709 ISO.

    Reply back if there are improvements.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-06-25T02:18:55+00:00

    How does Microsoft want me to pay hundreds of dollars to activate a pirated version of Windows 10 if they are not even able to deliver a decent OS? Shame on you!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-06-20T19:47:26+00:00

    This is more a workaround rather than a proper fix, which does not work on every device either.

    It would be nice if Microsoft finally adressed this issue. It has been almost 3 months! Good lord, If I only could downgrade to 1709

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments