Why Microphone Boost Resets After Every Reboot on Windows 11

Quick fix: Microphone Boost reverts because the driver registers a new endpoint instance after each boot, and the per-endpoint settings save against the old GUID. Lock the boost to a permanent value with PowerShell’s Set-AudioDevice module, or set it via the Realtek/Conexant control panel which writes to a persistent path.

You set Microphone Boost to +20 dB in the legacy Sound dialog because your headset mic is too quiet. After the next reboot, Boost is back to 0 dB. Apps that worked before sound quiet again. The slider didn’t fail — the saved value is bound to a device instance ID that changes every time Windows enumerates the audio hardware.

What causes the reset

Each audio endpoint in Windows has a GUID under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture. The endpoint’s “DeviceInterface” subkey stores volume, format, and per-effect properties. Some drivers (notably some USB headset class drivers and a subset of Realtek configurations) create a new GUID after each enumeration cycle, which happens on every boot. Your boost setting was saved against the old GUID and is orphaned.

The fix is to either bind the boost to a stable property the new GUID inherits, or to push the value through a path the driver re-reads at every boot.

Method 1: Set boost via Realtek/Conexant control panel

If your machine has a vendor audio control panel, use it — vendor settings save to a path that survives endpoint re-enumeration.

1. Press Win + S and search for Realtek Audio Console, Conexant SmartAudio, or whichever brand is installed.
2. Find the microphone settings. Adjust the Microphone Boost or Mic Gain slider to your desired level (typically +20 dB).
3. If the panel has a Save settings to all applications or Apply to all profiles button, click it.
4. Reboot and verify the boost persists.

Vendor apps win against Windows Sound dialog every time because their settings push the value at driver load. If you don’t have one installed, get the OEM build from your laptop/motherboard manufacturer.

Method 2: Lock boost via AudioDeviceCmdlets PowerShell module

For USB or generic class-driver mics that don’t have a vendor panel:

1. Install the AudioDeviceCmdlets module: open PowerShell as Administrator and run Install-Module -Name AudioDeviceCmdlets. Confirm if prompted.
2. List capture devices: Get-AudioDevice -List | Where-Object Type -eq “Recording”.
3. Note the Name and ID of your mic.
4. Create a small script C:\Scripts\set-mic-boost.ps1:
   
   Import-Module AudioDeviceCmdlets

Set-AudioDevice -ID “YourMicID”

Set-AudioDevice -RecordingVolume 100
   
   (For finer boost control, also call Set-AudioDevice -RecordingBoost 20 if the module supports it — check Get-Command -Module AudioDeviceCmdlets.)
5. Open Task Scheduler. Create a task triggered at user logon, action: powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\set-mic-boost.ps1.
6. Save and test by signing out and back in.

The logon script re-applies the boost every time you sign in, regardless of GUID changes.

Method 3: Lock the registry MMDevices property directly

For users comfortable with registry edits:

1. Set the boost manually via the legacy Sound dialog first. While Windows is running with the setting active, open regedit.
2. Navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Capture.
3. For each GUID subkey, look inside the FxProperties child key. Find the volume/boost property — typically a REG_BINARY under a sub-GUID like {9855c4cd-df8c-449c-a181-8191b68bd06c},0.
4. Export the entire GUID branch to a .reg file as backup.
5. If the driver enumerates a new GUID on next boot, you can re-import the .reg file to restore the value — but this is fragile. Method 2 is more reliable for chronic resets.

Registry direct edits are best reserved for permanent installations on the same hardware. The PowerShell logon-script approach scales better.

How to verify the fix worked

• Open the legacy Sound dialog (mmsys.cpl) → Recording tab → right-click your mic → Properties → Levels. Boost shows your set value.
• Reboot. Reopen the same dialog. Boost still shows the set value.
• Open the Voice Recorder app and record a 5-second clip; speaking at normal volume produces a strong audio level (yellow zone, not flat).
• If using a vendor panel, the panel’s gain shows the same value.

If none of these work

If boost still resets after Method 2’s logon script, the script may be running before the audio device is fully initialized. Add a Start-Sleep -Seconds 10 at the start of the script. For some USB mics that don’t support boost via the class driver at all, the only path is hardware-level — check the headset/mic for a gain knob or DAC switch on the device itself. Some streaming-grade USB mics (Blue Yeti, Shure MV7) have desktop apps with persistent gain settings independent of Windows.

Bottom line: Mic Boost reverts because endpoint GUIDs change on boot. Vendor control panels and PowerShell logon scripts both push the value at a stable layer that survives enumeration. Pick whichever your driver supports.