Managing sound and video settings during Teams meetings and calls for optimal communication
I have installed an add on from Microsoft itself that seems to control the issue: EarTrumpet.
Just go to Microsoft store and install
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The title says it all. The only way to prevent my ear drums from bursting is:
This happens 100% of the time and it's absolutely ridiculous.
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.
I have installed an add on from Microsoft itself that seems to control the issue: EarTrumpet.
Just go to Microsoft store and install
I've had this issue for a few years and MS has not fixed it. I was able to do the common fix which was to reduce the Teams volume in the App Volume and device preferences setting (I had to go down to 8 to make it listenable without hearing damage). This was a workable fix. As long as my computer was not restarted, it would remember that setting for each call and Teams wouldn't override.
Now, with "new Teams", it does not remember. Every single time I rejoin a call, it will push the volume back up to 100% which is at a damaging level for me. It's been years and it's time to address this MS. I can't believe it hasn't been as many organization such as mine have users utilizing Teams for calls and meetings.
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
Had the same problem since a few days. After unpairing my bluetooth handset and repairing it, the volume control starting working again as expected.
It's been almost a year and this bug hasn't been fixed yet. It's ridiculous.