There's every chance this is microsoft's fault, but bluetooth is also an ungodly mess of hacky junk that seems to get patched just enough to work with big hardw

There's every chance this is microsoft's fault, but bluetooth is also an ungodly mess of hacky junk that seems to get patched just enough to work with big hardware vendors, and then forgotten about. My theory is that the bluetooth hardware community doesn't have any rigorous testing suite for compliance with the spec. Instead implementors just test with a few other vendors' half broken implementations of the stack, and then they patch their own hardware just enough to make it work and release things. I bought a bluetooth keyboard and mouse a few weeks ago (both from different vendors). Neither device works over bluetooth on my linux workstation. I can get the keyboard to work by running some random commands I found on the internet, but it stops working when I sleep my computer. (A suddenly broken keyboard is the worst kind of surprise). The mouse has never worked over bluetooth. It just spits errors into my kernel's bluetooth stack. Both devices are just plugged in via USB cables now. I suspect linux's bluetooth stack is spec compliant, but its missing all the dirty workarounds for broken hardware that exist in macos and windows. Anyway, Microsoft shouldn't have broken your headphones. But Bose is probably just as much to blame.