Share via

Headset not working while teams call

Alex Mouawad 20 Reputation points
2026-03-17T15:04:29.2933333+00:00

Hi, thanks for the detailed steps. I’ve already gone through all of these on affected devices, including setting the Bluetooth headset as default input/output, checking microphone permissions, running troubleshooters, updating Bluetooth/Wi-Fi drivers (including Intel), reinstalling drivers, applying all Windows updates, and fully power cycling the machines.

The issue still persists: during Microsoft Teams calls, Bluetooth headsets (JBL, Ugreen, earbuds) disconnect for both audio and microphone, while wired headsets and laptop audio work fine. Since this started after a Windows update and affects multiple users and devices, it seems more like a system-level or update-related issue rather than configuration.

Has anyone identified a confirmed fix or workaround?

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video

Answer accepted by question author
  1. Killian-N 9,560 Reputation points Microsoft External Staff Moderator
    2026-03-17T17:35:54.69+00:00

    Hi @Alex Mouawad,

    Thank you for taking the time to share your detailed update. Based on everything you’ve already tested, your conclusion makes sense, this does appear to be a system‑level issue rather than a configuration problem, especially since it started after a Windows update and is affecting multiple users and devices.

    What we’re seeing in similar cases is that this behavior is usually tied to how Windows handles Bluetooth call (hands‑free) audio profiles after certain updates. When a Teams call starts and switches the headset into call mode, Windows can unexpectedly reset or drop the Bluetooth audio connection. This would explain why wired headsets and built‑in audio continue to work normally, while Bluetooth devices disconnect only during Teams calls.

    At the moment, there isn’t a confirmed permanent fix, but the following workarounds have helped some customers in enterprise environments:

    • Using Teams on the web, which bypasses the desktop app’s media stack and often keeps Bluetooth audio stable.
    • Disabling the Microsoft Bluetooth LE Enumerator in Device Manager, then re‑pairing the headset. You can review this similar thread for more information: How to PERMANENTLY disable Handsfree Telephony for a bluetooth device in Windows 11?
    • If permitted by IT policy, rolling back the Windows update that introduced the issue, as this behavior has been observed immediately after specific cumulative updates.

    Currently, Microsoft has not published an official fix, and cases raised for this scenario are generally tracked as a Windows Bluetooth regression affecting real‑time communication apps, including Teams.

    I completely understand how disruptive this is, particularly in a multi‑user environment. If you haven’t already, I’d recommend opening a Microsoft Support case and clearly noting that the issue occurs only with Bluetooth headsets during Teams calls following a Windows update, as this helps route the case appropriately.

    You can create a support ticket by signing in to the Microsoft 365 admin center and following the steps in this link: Get support for Microsoft 365 for business to create a support ticket from the admin center or by calling phone support to contact Microsoft Support: Customer service phone numbers. If you don't have admin privileges, you can ask your IT admin to do it on your behalf.

    If needed, this article may also help you identify your Microsoft 365 administrator: How do I find my Microsoft 365 admin?.

    Note: We appreciate your understanding regarding the scope of support available through this forum. As moderators, our role is to provide general guidance and assist with common troubleshooting steps. While we do not have access to internal systems or administrative tools necessary to resolve specific account or backend-related issues, we will continue to do our best to support you within the scope of our responsibilities.

    I hope this helps clarify the situation and move things forward. Please feel free to share any updates or let me know if you need further assistance. I’ll be glad to help.

    I look forward to your reply.


    If the answer is helpful, click on "Accept Answer" and please vote positively. If you have additional questions about this answer, click on "Comment".

    Note: Follow the steps in our documentation to enable email notifications if you want to receive the email notification related to this thread.

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Alex Mouawad 20 Reputation points
    2026-03-18T08:15:57.9566667+00:00

    this is the error and there is no mic and no sound somtimes work on another device and somtime no same by cable always working

    Screenshot 2026-03-11 162701


  2. Q&A Assist
    2026-03-17T15:04:51.7433333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    This behavior after a Windows update points to a Bluetooth/driver issue rather than a Teams-only problem. Use the following steps on one affected PC and then replicate for others:

    1. Confirm Bluetooth headset is default for input/output
      • In Windows 11: Select Start > Settings > System > Sound.
      • Under Output, select the Bluetooth headset.
      • Under Input, select the Bluetooth headset microphone in Choose a device for speaking or recording.
      • Use the built‑in Microphone test to verify that Windows is receiving audio.
    2. Check app access to the microphone
      • If on Windows 10: Start > Settings > Privacy > Microphone.
      • Turn on Allow apps to access your microphone and ensure Allow desktop apps to access your microphone is On.
      • If the headset has an integrated mic via camera, also check Settings > Privacy > Camera and ensure access is enabled.
    3. Run the Recording Audio troubleshooter
      • Windows 11: Settings > System > Sound.
      • Scroll to Advanced and choose Input devices under Troubleshoot common sound problems.
      • Windows 10: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Recording Audio.
      • Let it detect and fix issues with the Bluetooth microphone.
    4. Update Bluetooth drivers
      • Select Start > Device Manager.
      • Expand Bluetooth.
      • Right‑click the Bluetooth adapter (may include the word “radio”) and select Update driver > Search automatically for updated driver software.
      • Complete the wizard, then restart the PC when prompted and test a Teams call again.
    5. Update Wi‑Fi/Bluetooth platform drivers if using Intel
      • In Device Manager, under Bluetooth, right‑click Intel(R) Wireless Bluetooth > Properties > Driver to check the version.
      • Under Network adapters, check the Intel(R) Wi‑Fi component driver version.
      • If outdated, download and install the latest Intel Wireless Bluetooth and Wi‑Fi drivers from the Intel site referenced in the documentation, then restart and retest.
    6. Check for Windows Updates
      • Start > Settings > Windows Update > Check for updates.
      • Install all available updates, restart, and test again. This is important if the issue started immediately after a prior update.
    7. Power‑cycle the PC fully if Bluetooth disappeared or is unstable
      • Shut down the PC.
      • Turn off power (for desktops, switch off PSU or unplug for several minutes; for laptops, fully power off and wait, then power back on).
      • Boot and verify Bluetooth is present and stable, then re‑pair the headset and test Teams.

    If Teams works with wired headsets and with the built‑in mic, but multiple different Bluetooth headsets all show “Bluetooth microphone disconnected” during calls, the most effective long‑term fix is usually updating or reinstalling the Bluetooth and audio stack (steps 4–6) on each affected device.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.