Can't connect to bluetooth device and troubleshooter missing files.

Reported
Anonymous
2023-08-10T21:22:16+00:00

When connecting to my Bluetooth speakers, it says: "We didn't get any response from the device, try connecting again.

When trying to troubleshoot this issue an error pops up stating: "ms-contact-support://settomgs/settingspagetroubleshootbluetooth. this file does not have an app associated with it for performing this action. Please install an app or, if one is already installed, create an association in the default app settings page."

this all happened after I upgraded from Windows 10 to Windows 11. Please help

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

112 answers

Sort by: Newest
  1. Anonymous
    2024-04-17T22:32:39+00:00

    Please help, end my suffering.

    0 comments No comments
  2. Anonymous
    2024-04-17T11:12:42+00:00

    i am not able to connect my bluetooth devices

    0 comments No comments
  3. Anonymous
    2024-04-16T11:41:48+00:00

    my bluetooth is undiscorable

    0 comments No comments
  4. Anonymous
    2024-04-16T06:26:47+00:00

    hello sir

    i have some problem in my devies

    in this devie i doesn't turn on blutooth option

    and fingerprint option

    0 comments No comments
  5. Anonymous
    2024-04-15T20:23:58+00:00

    I have the same problem, Bluetooth icon is not in my Taskbar, initially it was not in the device manager but then I installed the driver, restarted, but it's still not working. I changed the startup of Bluetooth support service to automatic, restarted, still not working. Windows is updated, no restart required.

    I opened the Event viewer and found event id 2: Bluetooth HID device  either went out of range or became unresponsive.
    I had run sfc /scannow in CMD and I checked and restored corrupted files. I am out of ideas. The only option I know that could solve the problem is to roll back to the update before this problem happened.

    0 comments No comments