Windows 10 Creators Update is the latest iteration of Microsoft’s OS which launched a while back. The company decided to throw the old model out of the window and stop launching a new operating system every year or every couple of years.
Instead, it will be focusing on updating Windows 10. In other words, Microsoft will continue to refine Windows 10, polish the imperfections, and squash all the bugs that its engineers can find. The Creators Update is a huge upgrade that has been in the works for many months, culminating in a release this month.
Unfortunately, early adopters report that the OS is not perfect. It has its own little imperfections and small problems here and there. Users have already started to take it to the forums, asking for help in solving various issues. One user who goes by the name Spritanium, posted a lengthy cry for help on Microsoft’s forum, hoping to get some help for a particular Bluetooth issue.
A few points, PLEASE read all of these thoroughly to avoid posting answers I can’t do anything with:
- Using Windows 10 x64, the latest Creators Update
- My headphones are Altec Lansing, model MZX300
- The headphones work 100% fine on my Android phone, connecting instantly
- Yes, the headphones are in “discoverable” mode, and I’ve tried many, many times
- I have tried connecting via the “Connect” option in the Action Center, the bluetooth settings, and the “Add a device” wizard. On Android I don’t even have to attempt to discover the headphones, they just appear.
- I have disabled bluetooth on my phone to ensure there is no conflict. The headphones stay in “discoverable” mode (flashing red and blue light, as indicated by the instructions) until they power off due to inactivity.
- I have checked “Allow Bluetooth devices to find this PC”
- It’s not a driver issue, this same problem occurs on two separate computers with different bluetooth radios (generic & realtek)
- Both of the bluetooth-related services in services.msc – including the one specifically related to bluetooth headsets – are enabled and set to start automatically.
Why is bluetooth on Windows such garbage? Since there obviously won’t be any helpful solutions posted, should I just switch to OSX?
So far, no one was able to provide a solution to fix this issue, leaving the user waiting for an official reply from Microsoft.
RELATED STORIES TO CHECK OUT: