Share via

Bluetooth Audio Accessories connects only as "music" (headphone under sound), not "calls" (headset under sound) - Windows 10 (Reset 3 times)

Anonymous
2025-06-03T08:47:25+00:00

My post is about the same issue described in this post: Bluetooth headset connects only as "music", not "voice" - Microsoft Community](https://answers.microsoft.com/en-us/windows/forum/all/bluetooth-headset-connects-only-as-music-not-voice/23ea9ca1-d215-429b-859a-cc420afe80b2 "answers.microsoft.com"), by @[Rishi Chheda I have tried the steps suggested there.

However, I did not see a real solution there, even for the original author of the post.

The issue, previously all my Bluetooth devices used to show "Connected music, Calls".

Now, none of them have "calls".

I know the Bluetooth accessories are working fine as they connect well with other mobile as well as windows devices (with calling).

I have shown example of a JBL Bluetooth speaker with calling function as well as a Sony headset that I use regularly, but I have also tried with 5 Bluetooth devices in my family, and it is the same.

Conclusion: The problem is not the accessories, and it is not with a few accessories but all of them.

Same situation under "Sounds" all of the "Speaker"/"Earphone" parts of the same device connect but the "Headset" part which is used for calling doesn't, "connect" option doesn't actually do anything.

You can see the same problem in the "recordings" tab, any other microphone which is on the webcam, onboard the laptop of wired, gets connected. (I even used Win + H for dictation in windows)

Just the Bluetooth devices don't get connected. "Connect" option doesn't actually do anything

Things I have tried:

  1. Bluetooth Troubleshooter
  2. Individual Device Troubleshooter
  3. .
  4. Unpair and paired the accessories multiple times.
  5. Disabling and reenabling the devices from "Sound" (this I have tried on all steps whenever I fiddled with the drivers also, also restarted laptop)
  6. Uninstalling, reinstalling the Devices from Device Manager and same from devices and printers
  7. Also updated the driver using "Click "Browse my computer for drive software"
  8. Resetting the Laptop 3 times. (EDIT: Windows fully updated after each reset)

The main issue is problem is that there are no errors anywhere.

Every device shows "This device is working properly", which is not true!

Can someone really knowledgeable on Windows & Bluetooth, please help me out to get to the bottom of this issue?

I think we need to see the logs somewhere that I simply do not know.

Windows for home | Windows 10 | 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

8 answers

Sort by: Most helpful
  1. Anonymous
    2025-06-07T10:58:37+00:00

    Hello Zack,

    Thank you for your response!

    Regarding 4) I have updated my post with the information now "EDIT: Windows fully updated after each windows reset"

    1. I could not find "Handsfree Telephony" but I see the following services:

    (Is it missing in my system? But I reset and updated windows 3 times but maybe this is the issue. Also, I never fiddled with these services)

    Since "Bluetooth Support Service" running, I did not change the manual triggers to automatic, let me know if I still should.

    1. I don't see an option related to hands-free or telephony from properties when selecting from Bluetooth settings like so

    BUT from Devices and Printers I see this:

    For 3)
    It is not possible to set it as any kind of default device until it shows connected in sound devices, I have already included that screenshot where handsfree shows disconnected even though the stereo audio part of the same accessory is connected.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-06-07T10:29:52+00:00

    What you are looking at in all those screenshots are meaningless.

    There are 4 parties -- (a) the OS, (b) the app, (c) the actual bluetooth device and (d) you.

    1. You set a "default communications device" in the OS. What this means is that when (b) and (d) don't tell the OS which specific headphone/mic to use, it will use this device in a telephony type of app.
    2. You set a "default device" in the microphone department. What this means is that when (b) and (d) don't tell the OS which specific mic to use, it will use this mic in a recording app.
    3. If you want some other mic in some specific app, you go into that particular app and specifically tell the app to use some other specific mic.

    If that app doesn't have the option to choose a specific mic, then it will use the OS' defualt devices in (1) and (2). It is not the Windows OS' fault for not giving you a choice to pick a particular mic. It is the app's fault for not giving you a choice to pick a particular mic inside that app.

    Hi Joseph,

    Thanks for your response but I maybe you missed my point.
    Why I posted these screenshots is because there is no sign of any Bluetooth Device connecting as a calling device. (C as per you)

    The A+B+C+D with 1+2+3 settings you mention work only after the device is connected.
    And it is working for wired devices, problem is not related to just mics, or just earphones, as they work with wired devices and also USB accessories.
    Bluetooth Telephony Connections very specifically are not working for any accessory.

    Was this answer helpful?

    0 comments No comments
  3. JosephT71 9,215 Reputation points
    2025-06-03T17:18:36+00:00

    What you are looking at in all those screenshots are meaningless.

    There are 4 parties -- (a) the OS, (b) the app, (c) the actual bluetooth device and (d) you.

    1. You set a "default communications device" in the OS. What this means is that when (b) and (d) don't tell the OS which specific headphone/mic to use, it will use this device in a telephony type of app.
    2. You set a "default device" in the microphone department. What this means is that when (b) and (d) don't tell the OS which specific mic to use, it will use this mic in a recording app.
    3. If you want some other mic in some specific app, you go into that particular app and specifically tell the app to use some other specific mic.

    If that app doesn't have the option to choose a specific mic, then it will use the OS' defualt devices in (1) and (2). It is not the Windows OS' fault for not giving you a choice to pick a particular mic. It is the app's fault for not giving you a choice to pick a particular mic inside that app.

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2025-06-03T13:27:58+00:00

    Hello Shishir,

    Thank you for sharing your concern on community forum,

    As I can understand, you are facing issue regarding using your headset at the time of calls. Here are some steps you may consider.

    1. Make sure that necessary Bluetooth services are running. You can do that by opening services.msc in run dialog box and ensure that "Bluetooth Support Service" and "Handsfree Telephony" are set to automatic and running.
    2. Turn on the headset telephony feature. Go to Bluetooth settings, select your device, and ensure the "Hands-Free Telephony" option is enabled under properties.
    3. Make your headset the default communication device. Navigate to "Sound" settings (mmsys.cpl), under "Playback" and "Recording" tabs, and ensure the headset is set as the default communication device.
    4. Sometimes, outdated system can cause the issue. Make sure that your windows are up to the date. Please check - Install Windows Updates - Microsoft Support

    I appreciate your understanding and patience,

    Kind regards

    Zack | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments