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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi all,
I have an issue with my headphones (WH-1000XM3) when having teams calls probably after the last team update to version 1.5.00.28361 as it was working fine before. The issue is that I cannot use the stereo setting when on call which provides the noise cancellation feature of my headphones. Please note that this feature works fine in all the other applications I am using including youtube, skype etc.
So here are my default settings which won't give me noise cancellation.
If I switch to stereo I only hear my voice. (cannot hear the rest that is in the call)
Managing sound and video settings during Teams meetings and calls for optimal communication
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.
Hello
I don't know if anyone is still following this but in my case I think the problem has been fixed ?
Did someone noticed the same ?
Sajjad747 - As you can see from the comments on this post, there are a number of frustrated people over this issue. Has there been any further action taken to resolve this bug?
I'm not saying we won't get an official response here, but it is unlikely. For that reason, I'm trying to work through my IT department to escalate through Microsoft's official support channels. With business/enterprise accounts, Microsoft will only support account administrators.
If you're able to do the same, I'd recommend it - the squeaky wheel gets the grease.
No, still the same for me :/
I should have noted that I was running Windows 10.
I was upgraded to Windows 11 over the weekend and the workaround doesn't work either.