How do I stop teams from turning my headset volume up to 100% in the "App volume and device preferences" before each call?

Anonymous
2023-04-25T20:51:49+00:00

The title says it all. The only way to prevent my ear drums from bursting is:

  1. Join a call before anyone else
  2. open Settings
  3. search for "Sound mixer options" (which takes you to the "App volume and device preferences" screen)
  4. turn the teams volume down for my headset

This happens 100% of the time and it's absolutely ridiculous.

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

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

86 answers

Sort by: Most helpful
  1. Anonymous
    2025-06-10T07:00:03+00:00

    How can MS Teams be unaffected by the MASTER VOLUME slider?
    Please stop adding features and work on fixing the basic functionality PLEASE

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-04-09T09:42:53+00:00

    I think I may have actually found the solution here.

    Step 1. Go to your computers settings.

    Step 2. Click system.

    Step 3. Click sound.

    Step 4. Scroll down to App volume and preferences

    Step 5. Notice that for some really bizarre reason there are two separate Microsoft Teams App volumes - I don't know why, there just are.

    Step 6. As counterintuitive as this is, the two Microsoft Teams App Volumes should NOT be set to the same thing. ONE of them needs to be set to "Default" and the other should be set to whatever your headset earpiece is (I would have expected them to need to be the same but nope). Changing the top Microsoft Teams App volume to "Default" seemed to fix the problem.

    I don't know why they set it up this way, but it really does seem to work.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-03-06T18:05:07+00:00

    Nope. Workarounds of changing "sync" settings in MS Teams for 'device' or 'mic' didn't help.

    Seriously Microsoft???

    From another MS Community post, there's another workaround to try:

    https://answers.microsoft.com/en-us/msteams/forum/all/why-does-new-teams-set-every-calls-volume-to/0752ee57-7ff7-4667-a837-74d45b1dca3f

    • Find the speaker icon in the system tray and right-click, then choose "Open Sound Settings".
    • Select the device properties and choose "Additional Device Properties".
    • In the Speaker Properties menu, choose the "Advanced" tab and ensure that both boxes under "Exclusive Mode" are unchecked.

    I will report back later with my results.

    P.S. - in my last post I said either the word h*ck or cr*p or h*ll and it changed it to all **** like I said some kind of terrible thing, LOL

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-09-10T21:55:50+00:00

    The worst part is the unpredictable call via Teams when you happen to be listening to a video - there's nothing you can do, you just get blasted by the sound of a ringing call. This happened to me again today about an hour ago and my ears are throbbing still.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-08-21T16:43:26+00:00

    I get the same experience as Spredmore - I use a wired 3.5mm headset and Teams overrides my volume selection. I go into windows settings to lower the volume for teams (it saves the changes I have made for system sounds etc.) but Teams resets it to 100%. I haven't found a consistent timing on when this happens - it's not before every call, because sometimes a call may retain the lower volume setting if I just set it. But if I join a meeting later (say a scheduled meeting an hour from now), I have to re-set my volume down again. This happens in "New" teams, so not sure if it's a new bug, but it didn't seem to happen with Win10 or on a previous computer - just a recently issued laptop.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments