Windows 10: Bluetooth is not connect with device and not show any device

i was trying but still my device is not connected

:)

 

Bluetooth not showing devices, won't connect new devices

I'm on Windows 10 Pro, Version 22H2.

I'm on a laptop using the built-in Intel Wireless chip, which also comes with Bluetooth. I'm using one Bluetooth device - a headset, Jabra Evolve 65 - every day without issues.

Now I acquired another Bluetooth device - a game controller - and I cannot get the PC to detect it. My Android phone finds and connects to both the old headset and the new controller, so the peripheral devices shouldn't be at fault. After an extended online research, I found that something more fundamental is off with my Bluetooth - there seems to usually be a list of devices, both paired and "foreign, but detected", that is just missing from my interface.

I cannot be sure, but that list might just be missing ever since, I never paid attention. The Bluetooth on/off toggle works as intended, my headset disconnects and reconnects as expected. By the way, the "printer and devices" window is also empty, even though I do have a printer, mouse and keyboard up and running (and showing in device manager). The issues seem related, according to online searches. Windows Update is up to date and so is the Bluetooth driver, according to device manager. I removed every Bluetooth-related entry from device manager and restarted, they showed up again as per screenshot (automatically re-installed on restart, I reckon). I completed both an SFC scan and a DISM scan. I checked services.msc and both the Bluetooth and the printer spooler services are up and running. The issue persists. Any ideas?

 

Cannot use bluetooth device

mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm

 

Cannot use bluetooth device

1 Pairing is done in Settings, Devices
1.1 You click on Add Bluetooth or other device
1.2 You choose Bluetooth
1.3 If there is a pairing button on the bluetooth device itself then you press that now. You need to check the instructions for your bluetooth device to see how to do this - several automatically go into pairing mode when they switch on, others have a button that needs to be pressed for, say, 5 seconds.
1.4 The computer detects all available bluetooth devices and you select yours from the list. If yours is not on the list then Windows could not detect it.
1.5 It connects - pairing includes connecting
1.6 The computer sounds a buzz in the earpiece then displays Your device is ready to go and you click on Done
1.7 The device is shown in the devices list below the subheading Audio and it shows it as connected
1.8 The device should also appear in Control panel, Sounds, Playback tab
1.9 The device should also appear in Control panel, Devices & printers
1.10 {I just paired some bluetooth earphones as I typed so I could make sure these notes were correct} You use a music player and the sound comes out of the bluetooth earphones

2 If this is not happening for you then go to Contol panel, Devices & printers
2.1 Right-click on the device & select Remove device
2.2 You can now try pairing from scratch again
2.3 Several other users have reported that only removing the device with Bluetooth command line tools - BluetoothInstaller allowed them to re-pair again [see xzion's guidance below]
2.4 Yet others reported that only the KeithM code or Bungee's guidance worked for them [see below]

3 Where is this all going wrong for you?
[I assume we are definitely talking about bluetooth headphones/earphones. I understand that WiFi ones do also exist.]


4 Additional guidance -

Unpair a Bluetooth Device - TenForumsTutorials
Connect a Bluetooth device in Windows - Windows Help

Steps to completely remove a belutooth device so pairing can be done again [post #9, xzion] - TenForums
Steps to completely remove a belutooth device so pairing can be done again [post #22, KeithM] - TenForums
Steps to completely remove a belutooth device so pairing can be done again [post #39, Bungee] - TenForums
Several people registered in TenForums just to be able to thanks xzion, KeithM & Bungee. Apparently, what worked for some people did not work for others so each solution seems worth trying.


Denis