From Newsgroup: alt.comp.os.windows-11
Andy Burns wrote:
As I remember, when Windows was shut down with BlueTooth device A
connected and BT device B disconnected, next time Windows was booted
device A would be connected and device B would be disconnected.
THAT'S HOW IT WORKED.
But how it works now is Windows connects both devices and treats one of
them with priority.
I only occasionally use bluetooth devices, I like wires they just work.
But it wouldn't surprise me if the first of a given class of device to
reply "wins" and gets used ...
I'm in cahoots with the low-bluetooth-use model for Windows, as my Windows
PC is from 2009, so it doesn't even have a bluetooth daughter card on it.
Even so, the possible race condition Andy speaks of isn't a universal
Bluetooth rule as, AFAIK, Windows can reconnect to more than one paired
device when they're available.
Being connected doesn't necessarily mean both are actively playing audio.
a. Windows uses the selected/default audio output
b. And some apps can sometimes choose their own output.
So, AFAIK, the "first device to reply wins" idea is plausible for some Bluetooth adapters or drivers, but it isn't guaranteed behavior.
The actual result can depend on the devices, Bluetooth adapter and driver, Windows version and audio settings.
Usually, IMHO, if these are two Bluetooth headsets, each may reconnect independently and a headset's own multipoint feature can affect which other devices it connects to.
For the OP, see if you can control which one plays sound by hitting...
Settings -> System -> Sound -> Output.
If the unwanted device keeps reconnecting and you don't need it paired,
remove it under Settings -> Bluetooth & devices -> Devices.
Often removing and adding back a bluetooth device has worked for me in the
past on devices (usually mobile devices for me though) with BT conflicts.
--
On Usenet, sharing empirical knowledge means learning from one another.
--- Synchronet 3.21d-Linux NewsLink 1.2