Microphone Volume Keeps Changing in Windows 10/11? Stop Teams Auto Gain, Driver and Audio Utility Resets

Microsoft’s current Windows guidance confirms that both Windows 10 and Windows 11 let you select an input device, test it, and change its input level from Sound settings. Microsoft’s Teams documentation also confirms that Teams can automatically adjust microphone sensitivity during meetings. In other words: the “reset” may be intentional behavior from software, even if it is not the behavior you want.

First, confirm which microphone is actually changing​

Many PCs expose several inputs at once:

• A laptop’s built-in microphone array
• A webcam microphone
• A Bluetooth headset hands-free microphone
• A USB microphone
• A virtual device installed by streaming, recording, or noise-filtering software

Before adjusting anything, ensure Windows is using the microphone you mean to use.

Windows 11​

1. Open Settings.
2. Go to System > Sound.
3. Under Input, select the microphone that should be used for calls and recording.
4. Open its properties page.
5. Under Input settings, set the Input volume to the level you want.
6. Use Start test, speak normally for several seconds, then stop the test and play it back.

Windows 10​

1. Open Settings > System > Sound.
2. Under Input, select the correct device in Choose your input device.
3. Open Device properties if it appears, and adjust the microphone level.
4. Use the microphone test indicator to confirm that Windows is receiving audio.

If the level shown in Windows changes while you have not opened any calling app, the problem is more likely to involve a driver, manufacturer utility, or device profile. If it changes only after launching a specific app, that app should be your first suspect.

Quick diagnostic: Set the microphone level, close all communications apps, restart Windows, and check it again before opening Teams, Zoom, Discord, a browser tab, or recording software. This separates a Windows-or-driver issue from an app-specific one.

Click to expand...

Stop apps from taking exclusive control​

Windows has a legacy audio setting called Exclusive Mode. When enabled, an application can request direct control over an audio device. That capability can be useful for specialized recording and playback workflows, but it can also make troubleshooting feel like you are sharing a steering wheel with an octopus.

Microsoft’s support documentation specifically identifies exclusive control as a possible source of audio conflicts.

1. Open Settings > System > Sound.
2. Scroll to Advanced and choose More sound settings.
3. Select the Recording tab.
4. Right-click your microphone and choose Properties.
5. Open the Advanced tab.
6. Under Exclusive Mode, clear:
   • Allow applications to take exclusive control of this device
   • Give exclusive mode applications priority, if available
7. Select Apply, then OK.

On Windows 10, you may reach the same Sound dialog through the legacy sound-control options. The labels can vary slightly by Windows build and audio hardware, but the destination is the same: Recording > microphone Properties > Advanced.

What this setting does—and does not do​

Disabling Exclusive Mode can prevent one app from locking down the microphone device. It does not necessarily prevent every app from applying its own gain or sensitivity processing inside the app. That distinction matters. An app can leave the Windows slider alone while still making your voice louder or quieter for people on the call.

Check Teams and the calling app itself​

If the microphone level changes when you join or start a Teams meeting, inspect Teams before reinstalling drivers.

Microsoft’s Teams documentation includes an Automatically adjust mic sensitivity option in the app’s audio settings. When enabled, Teams adjusts sensitivity to help keep a participant audible during a meeting. That can be helpful in a noisy room or with a quiet speaker, but it is the opposite of a fixed, manually controlled microphone level.

In Teams:

1. Select Settings and more.
2. Open Settings > Devices.
3. Under Audio settings, confirm that the right microphone is selected.
4. Look for Automatically adjust mic sensitivity.
5. Turn it off if you need Teams to stop dynamically managing your microphone sensitivity.
6. Run a test call after changing the setting.

Do the same kind of audit in any app that coincides with the problem. Look for controls named:

• Automatic gain control
• Automatically adjust microphone volume
• Automatic microphone sensitivity
• Voice normalization
• Audio enhancements
• Noise removal or voice isolation

These features are not inherently bad. They are designed to make calls more intelligible. But if you use a studio microphone, an audio interface, a carefully tuned headset, or a consistent recording workflow, automatic control may turn your predictable setup into a small daily science experiment.

Check microphone permissions—but do not confuse them with volume control​

Microphone privacy permissions determine whether an app may access the microphone. They generally do not set the microphone’s level, but a blocked or incorrect permission can make it appear that your chosen microphone settings are being ignored.

Windows 11​

Go to Settings > Privacy & security > Microphone and confirm:

• Microphone access is on.
• Let apps access your microphone is on when needed.
• Let desktop apps access your microphone is on for desktop calling and recording apps.

Windows 10​

Go to Settings > Privacy > Microphone and confirm that microphone access is enabled for the device, apps, and relevant desktop software.

Microsoft notes that desktop apps are handled differently from Store apps and may not appear as individually switchable entries. So, an app’s absence from the list does not prove it cannot access the microphone.

Refresh the audio driver—carefully​

When a microphone level reverts immediately after every restart, an audio driver or vendor control component becomes a stronger suspect. This is particularly common on laptops using integrated audio chips and bundled effects suites, where the Windows driver is only one part of the audio stack.

Start with the low-risk route:

1. Right-click Start and choose Device Manager.
2. Expand Sound, video and game controllers.
3. Right-click the relevant audio driver.
4. Select Update driver.
5. Restart the PC and retest the microphone level.

Microsoft also recommends reinstalling audio devices and drivers when Windows cannot detect a microphone or normal troubleshooting has failed:

1. In Device Manager, expand Sound, video and game controllers.
2. Right-click the applicable audio device and choose Uninstall device.
3. Restart the PC.
4. Windows should attempt to reinstall the audio device and driver automatically.
5. If necessary, return to Device Manager and select Scan for hardware changes.

Use this step with some caution if you depend on a niche USB interface, broadcast microphone, or specialized production hardware. For those devices, download the current driver package only from the PC maker or the audio-device manufacturer—not from a random driver-download site wearing a suspiciously cheerful “Update Now” button.

Inspect manufacturer audio utilities​

Laptop and motherboard vendors often bundle software that controls features such as:

• AI noise cancellation
• Microphone effects
• Beamforming for microphone arrays
• Voice clarity modes
• Headset detection
• Audio presets
• Communications profiles

These tools can apply settings at startup, which explains why a microphone level may look correct until the next reboot. They may also apply a different profile when a headset is plugged in, Bluetooth reconnects, or a meeting app begins using the device.

Open the audio utility supplied with your PC or motherboard and look for microphone gain, automatic level adjustment, enhancements, presets, and restore-default options. Disable only the feature you can identify as changing input behavior; do not blindly turn off every effect if you rely on its noise suppression or hardware-specific features.

If the utility has no useful controls, update it alongside the audio driver from the device manufacturer’s support page. An old driver paired with a newer Windows 11 update can produce delightfully vintage behavior, and not in the good vinyl-record sense.

Use this order of operations​

For the fastest path to a stable microphone level:

1. Select the correct input device in Windows Sound settings.
2. Set and test the input volume in Windows.
3. Restart without opening calling apps and check whether the level persists.
4. Disable Exclusive Mode for the microphone.
5. Turn off automatic mic sensitivity in Teams or the app that triggers the change.
6. Inspect manufacturer audio utilities for automatic gain, voice enhancement, or profile controls.
7. Update or reinstall the audio driver if the setting still changes after reboot.

When the slider is stable but your volume still changes​

A stable Windows input slider does not guarantee stable call volume. Teams and other communications software can process audio after Windows captures it. Noise suppression, voice isolation, automatic gain, and headset firmware can all alter the level heard by other people without visibly moving the Windows slider.

That is why the best final test is two-part:

• Record a sample using Windows’ microphone test or a simple recorder.
• Make a test call in the affected app.

If the recording is consistent but the call is not, Windows is probably innocent. Focus on the calling app’s microphone settings, effects, and selected device. If both change after a restart, focus on the driver and manufacturer utility layer first.