This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 90%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETL%3C/text%3E%3C/svg%3E)
mic is not working for all bluetooth headset. The bluetooth show connected with both sound and mic, but there are none of Window program can access the mic function. FYI, before the Window Updates, everything is fine.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 63%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Windows 11 Pro 25H2 26200.6584 Windows Feature Experience Pack 1000.26100.234.0 Blue Parrot B450-XT II v1.05
This stopped working a few days ago. It worked for 2 months. The headset works on other devices. When you select headset for mic in an app the speaker just clicks. One time it rebooted the machine. I need these for work. I tried another headset and the same issue.
I ran Audio and Bluetooth troubleshooter, and it seemed to fix the issue. Just leaving this for others to try.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 97%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVH%3C/text%3E%3C/svg%3E)
Dear @Timothy Liew,
I’m truly sorry you’re still experiencing issues with your Bluetooth headset, especially trying all the troubleshooting steps. I know how disruptive this is when you use your mic for calls and work. Thank you for your patience and for the steps you’ve already tried.
Because the problem persists after trying all the above troubleshooting steps, the fastest and most effective way to resolve this is to work directly with Microsoft Support. They have the tools and resources to perform deeper diagnostics and apply advanced fixes for Bluetooth and audio issues, especially those caused by recent Windows updates.
Contact Microsoft Support:
Step 1:
Step 2:
Note: Please be reassured that you are not alone, I’ll continue to monitor this case and will reach out to you with any new updates as soon as possible.
I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.
Thank you for your patience and your understanding. If you have any questions, please feel free to reach out.
I'm looking forward for your reply.
Dear @Timothy Liew,
Good day and I hope you're doing well.
At this point, the most effective way to resolve the Bluetooth headset problem is to contact Microsoft Support. They have the tools to run deeper diagnostics and apply advanced fixes for issues caused by recent Windows updates.
Please let me know once you’ve reached out to them. I’ll be waiting for your update and will stay engaged to assist with any next steps or recommendations they provide.
Thank you again for your time and cooperation. Looking forward to hearing from you soon.
Dear @Timothy Liew,
I hope this message reached you.
This is my second time reaching out to check if there is any update from you. I really want to make sure your experience is as smooth as possible. If you encounter any difficulties, please share more details about the current steps you are taking. I am always happy to assist you whenever you need.
While waiting for your response, I will also be monitoring other customer questions on the forum to assist them. If you have any further questions or updates, please tag (@Vivian-HT) in the reply so I can assist you more promptly and thoroughly.
I look forward to hearing from you soon.
doen't work.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 71%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
why my airpoad not working blouthe
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 1%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPL%3C/text%3E%3C/svg%3E)
We have the same issue with all the new Windows 11 laptops we have just rolled out circa 150. Our experience is that every call that the user receives the Teams system will show as not muted, but the other side cannot hear you and the mic symbol in teams doesn't show any activity.
However, if you mute yourself via the headset and then un-mute it starts to work again.
We have also disconnected Bluetooth and re-added which works correctly for at least 1 call but then stops again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 70%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECG%3C/text%3E%3C/svg%3E)
@Peter Longley which KB/Update did you rollback exactly? Might want to try this as well.
Did everything work normal after the rollback or are the experience you describe after the rollback?
I have not rolled back at all. Although this morning I have noticed a pending restart for the Cumulative Update for Windows 11 (KB5070773) and it seems the issue might be resolved (not fully confirmed as more testing is required).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 8%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
I've just checked my machine and my OS Build is 26100.6899, but KB5070773 targets OS Builds 26200.6901 and 26100.6901, so no resolution for me yet. I also can't roll back installed updates (or at least I don't think I can, there is something I can try and will do so and report back the results if so) thanks to corporate restrictions. Guess I'll have to wait and see if 6901 gets rolled out to me over the next few days. Edit: Just realised KB5070773 is 26100.6901, but nonetheless I can't get it yet.
OK, I was able to uninstall KB5066835 and now at least my Pixel Buds 2a have started working (after re-pairing them). The Bose QC 35 II are not, even after re-pairing, and they were the ones that were actually working the best before now. Still, at least I have one bluetooth headset working now. I'll wait and see what happens when/if I get KB5070773.
Thanks Peter and Stephen for your information. I will check with one of my users, if she got KB5070773 and we will also try to uninstall KB5066835.
Unfortunately uninstalling KB5066835 did not help in our case. The headset in question was a H800 by Logitech. It got connected but was not available at all in the audio settings 😅
so for our case, we might need to wait for a fix.
That's unfortunate. I did end up removing all bluetooth headsets as I had tried three different ones, and then just re-adding the one I wanted, but I assume you have tried re-pairing yours to no avail?
I have now tested fully and the issue still remains, I have the latest patches on my W11 machine and have also tried to turn off the "Use LE Audio when available" but still the only option is to (once the call has connected (mute via the headset and un-mute again).
The issue is not just with Teams either, it has the same effect on Zoom calls.
This is a serious issue for users that have many calls\meetings every day.
Some feedback from MS to advise when the issues will be resolved and how would be appreciated.
