The best part of computing.
Persevering and patient technical people along with users remaining in a good mood :)
I've never used any buds. I have only meddled with my Sony BT stereo headphones and a software surround emulation.
Nevertheless, the problems/solutions should be pretty similar.
My headphones work fine but lately I had to go to Bluetooth settings and manually connect to them. It should have happened automatically soon as I switched on the headphones. Blame it on applied 'enhancements' to improve Windows (maybe as in (3) below).
Points to check:
1. Disable Windows fast boot.
2. As mentioned above, do not allow the computer to turn off the BT adapter to save power.
3. Services:
Set both Bluetooth Support Service and Bluetooth User Support Service_xyz... to start automatically.
The User Support Service might complain for wrong parameter... In this case, open an Admin command prompt and run:
sc config BluetoothUserService start= auto
(you'll see the service set to Automatic after restarting Windows).
4. If you haven't yet, delete the buds connection in Bluetooth Settings and pair it fresh.
5. Switch off the buds
6. Restart Windows
If everything is in place (and I haven't forgotten something critical), when you switch on the buds, it should connect right away.
Open Bluetooth settings while doing that to see the change from not connected to connected.
All the best.
Update:
Adding this in case it helps.
I found it as a possible solution that seems simpler, when I was searching for a reason why the Generic Bluetooth Radio is yellow marked (code 31).
It is the Microsoft default driver, dated 2006, and its 2 .sys files in \system32\drivers have a 9/22/2026 date. Updating the driver tells me it can't find a better driver than what I already had. The installed driver's details are zilch. Go figure...
Anyway, if you disable this Generic driver (disable, uninstall will put it back after a reboot and enable it) and restart Windows, the Bluetooth problem goes away. It seems the MS driver has priority over whatever BT adapter is installed and that could cause the problem.
The relevant thread is here:
Coffee time...