Windows 10: How to make windows 11 remember volume level for different audio devices?

I switch between laptop speaker/mic & bluetooth headphones many times in a day. Sometimes I take the call with laptop and midway connect my bluetooth headphones. Previously on windows 10, windows used to remember the volume level. laptop always used to be on 80% and bluetooth headphones always on 20%.This is no longer the case with windows 11. Headphones volume also remains the same as laptop volume and every time I connect the headphones, I have to manually reduce the volume. This happens on a different windows 11 laptop also, so issue is not with laptop, it is with windows 11.Please help

:)

 

Build 1909 not remembering volume levels in the Volume Mixer

I recently updated from 1803 to 1909 and I've noticed that the Volume Mixer does not store volume levels for any apps and instead just resets them to 100% if they are restarted.

This was not an issue I experienced with 1803, I've already tried seeing if it was just an issue with my user profile/registry by testing on a newly created user profile, as well as attempting to fix it by adding a missing registry key as suggested in this reddit post.

I've also tried simpler steps such as reinstalling my audio drivers and using a headset with a USB soundcard (HyperX Cloud II's) but these were also unhelpful.

Any help would be appreciated *Smile

- - - Updated - - -

Actually, ignore this - I created the registry key mentioned in the reddit post above under HKEY_LOCAL_MACHINE instead of HKEY_CURRENT_USER, creating the keys in the correct location and restarting my PC fixed the issue.

For anyone else with the same issue just follow the steps in the reddit post given in the OP, i.e. create the following registry key(s) manually:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\LowRegistry\Audio\PolicyConfig\PropertyStore

 

Windows 11 Volume Mixer not remembering sound levels for "SYSTEM SOUNDS"

Windows 11 Volume Mixer not remembering sound level for System Sounds. I usually set the 'System Sounds' volume level to 5% because I find them annoying but they reset itself to 100% after a restart or randomly while using the PC. I've seen other reports of this exact same issue on this forum and on Reddit and the responses are always the same generic answers like "install latest drivers", "roll back to previous driver", "run SFC /SCANNOW", etc.

Since the launch date of Windows 11 I've been experiencing this problem on three different systems with totally different hardware configurations.

In my main system I'm running Windows 11 Pro 2H22 (Build 22621.819) with latest drivers.

Thanks in advance for any help to fix this issue.

 

WIndows 11 Update - Main Volume Level Cannot Be Changed on Realtek Speakers

Hello

I have updated my Dell XPS-13 to Windows 11.

When running on the inbuilt Realtek Audio speakers, now the main volume controls (both the volume control keys and the volume control slider on the taskbar) do not work properly. The mute function works (click mute key or click with mouse on mute icon on taskbar slider). If I put the volume on, however, there is absolutely no change to the volume level through the speakers - i.e. 2% is as loud as 100%. The volume level is quite loud, I would say close to maximum if not at the maximum.

Volume control within individual apps works okay - for example, I can raise or lower the volume within my Plex app using the volume slider within that app. The one exception to this is Spotify (Premium) where, curiously, there is no sound whatsoever*.

If I run the audio through my Sony Bluetooth headphones then all goes back to normal and the main volume controls work again.

My Windows 11 build is up to date. In trying to fix the issue with the in-built speakers so far, following advice provided elsewhere, I have:

• Restarted Windows Explorer
  
• Restarted my Audio Services
  
• Reinstalled the device driver for the speakers (Realtek Audio) and made sure it is up to date.
  
• Run the Audio Troubleshooter
  

Does anyone have any other suggestions? Thanks.

* This might just be a problem with Spotify, I haven't got around to looking at this yet.