On Windows 11 build 25309, you can enable an early preview of the new volume mixer in the Quick Settings flyout, and in this guide, you will learn how.
Microsoft is now testing (via @PhantomOcean3) an enhanced version of the volume mixer that allows you to change the volume per app individually and audio output directly from the Taskbar, using the Quick Settings flyout. In addition, the team has added a new “Windows key + Ctrl + V” keyboard shortcut to open the new volume mixer directly. And this update makes it easier to enable the Windows Sonic experience with a quick access list of installed spatial sound technology.
The new interface has been officially announced and it should enable by default on build 25309, but if it’s not, there’s a quick way to enable it. If you want to get hands-on with the new feature, you can use a third-party tool called “ViveTool” created by Rafael Rivera and Lucas on GitHub, to enable the option on your computer.
This guide will teach you the steps to turn on this new feature on Windows 11.
Enable new volume mixer in Quick Settings on Windows 11
To enable the new volume mixer on Windows 11, use these steps:
Open GitHub website.
Download the ViveTool-vx.x.x.zip file to enable the new volume mixer.
Double-click the zip folder to open it with File Explorer.
Click the Extract all button.
Click the Extract button.
Copy the path to the folder.
Search for Command Prompt, right-click the top result, and select the Run as administrator option.
Type the following command to navigate to the ViveTool folder and press Enter:
In the command, remember to change the path to the folder with your path.
Type the following command to enable the new volume mixer on Windows 11 and press Enter:
vivetool /enable /id:42106010
Restart the computer.
Once you complete the steps, open the System Tray and click the sound icon on the right or use the new “Windows key + Ctrl + V” keyboard shortcut to open the new volume mixer directly.
If you change your mind, you can revert the changes with the same instructions, but on step 10, make sure to run the same commands but use the
/disable switch instead of