In Windows 10's "Playback" tab in the "Sound" window, I would get two devices listed for each pair of Bluetooth headphones I would have connected. For my ear buds, we first have the buds listed as headphones and then as headset. The headset device is intentionally disabled by me. We'll get to why in a moment. On a clean install of Windows 11 on the same machine with the same devices / drivers, I am only shown the headphones:
How can I force Windows 11 to show me my buds as both headphones and headsets just like in Windows 10?
The reason I want this is because it gives me control over what Bluetooth profile is used with my ear buds because of the oligophrenic way Windows handles this.
Say I am listening in glorious A2DP stereo to a podcast while working. After some time, I have to join a Slack call. When I enter the call, the sane thing for Windows to do would be to switch to the headset profile but it more often then not does not do that. As a result, I could hear everyone on the call in stereo quality but they can't hear me.
On windows 10 the fix is simple: open the playback devices window (pictured above), disable the "Headphones" version of my buds and enable the "Headset" version. Lo and behold, I can now both hear and speak on my Slack call.
What happens after the call ends and I want to continue listening to the podcast? That's right, Windows refuses to switch back to stereo mode and I am stuck listening to my podcast in potato quality. Back in the playback devices window I go, disable the headset and enable the headphones.
In windows 11 I can no longer do that. Sometimes I can fix it by disabling and re-enabling Bluetooth in windows or turning the buds on or off. Other times, the only thing that works is going into services and restarting the "Windows Audio Endpoint Builder" service.
Bluetooth headphones/headsets have always been more of a handicap than a feature in Windows but with windows 11, instead of actually fixing it, they somehow made it worse. How hard can it be? Phones have been doing it for decades...
I already tried checking every combination of Bluetooth services inside the properties of my buds but doesn't seem to affect the problem: