Typical MS Fanboy bull.
the THEORY. The FLOWCHART, of windows 10 bluetooth UX is drop dead simple.
So simple in fact that they never managed to get it to work in most cases.
Again, let me walk you through the DROP DEAD SIMPLE steps of troubleshooting!
Isolate the problem. This requires you to have a few devices to shuffle things around. So we isolate the problem by trying different combinations of devices, adapters, operating systems, etc. In my own house I have 2 windows 10 PCs, Samsung Galaxy S6 phone, Samsung Galaxy Tab A, all of these devices have their own built-in bluetooth adapters. I also have an ASUS BT-400 USB adapter. I have a skullcandy Sesh BT earbud set, and a SENSO bluetooth headset. This gives me pretty much everything I need to test.
Connect SENSO to PC2 via Onboard = Failure - problem could be with SENSO, Onboard adapter, PC, or Windows.
Connect SENSO to PC2 via ASUS = Failure - problem is unlikely to be with the onboard adapter. Could be with SENSO, PC, or Windows.
Connect SENSO to PC1 via ASUS = Failure - Problem is unlikely to be PC, onboard, or asus adapter. Could be with SENSO or Windows.
Connect SENSO to S6 via onboard = Success - crystal clear audio. Problem is unlikely to be SENSO. Could be Windows.
Connect SESH to PC2 via Onboard = Failure. Problem could be SESH or PC2.
Connect SESH to PC1 via ASUS = Failure. Problem could be SESH or PC1 or ASUS adapter.
Connect SESH to PC2 via ASUS = Failure. Problem could be SESH or PC2, unlikely asus adapter (since problem already exists with the same hardware but an onboard adapter)
Connect SESH to S6 via onboard = Success! Crystal clear audio! Rules out the problem being Sesh
See how this works? We rule out the sesh by getting crystal clear audio in another device. We rule out the adapter because the problem persists even with other adapters. We rule out the tower's hardware by swapping tower hardwares. And a previous user here has even used all the exact same hardware and switched only the operating system from Windows to linux. With EVERY ELEMENT OF HARDWARE COMPLETELY IDENTICAL windows fails the connection and Linux operates seamlessly.
This is science.
"Well mine works fine."
This is an anecdote.
Troubleshooting is not always about -you- until you have had the problem, and solved it, your input is very rarely helpful, and only serves to insult, degrade, and cover up an actual problem that many people are having. Replies like yours make people who have legitimate problems NOT SEEK HELP.
So with all due respect, which is none, shut your hole until you do some actual research beyond "well I never had the problem so you must be an idiot."
TLDR; Yeah me too, and I really need a solution that doesn't involve windows being junked.