Skip to content

feat(Taskbar10): add Windows 11 sound flyout - #5234

Open
4yx wants to merge 2 commits into
valinet:masterfrom
4yx:add-win11-sound-flyout
Open

4yx wants to merge 2 commits into
valinet:masterfrom
4yx:add-win11-sound-flyout

Conversation

@4yx

@4yx 4yx commented Nov 5, 2026

Copy link
Copy Markdown

Closes: #2454, #4980, possibly #792 (though not for the reason mentioned)
Partially addresses: #1451

Add the "Sound output" flyout from Quick Settings (Control Center) as a "Windows 11 flyout" option for the sound icon of the Windows 10 taskbar's system tray, done in a similar manner to how flyouts are implemented for the Network icon (specifically, IAT patching the CoCreateInstance import in sndvolsso.dll).
The flyout is accessed via ms-actioncenter:controlcenter/volume, which first appears in build 25281 (tested and confirmed). Checks have been added to ensure the option does not appear in builds below 25281.

@pyrates999

Copy link
Copy Markdown

was this generated by AI?

@4yx

4yx commented Nov 5, 2026

Copy link
Copy Markdown
Author

AI assistance was used during development, yes. That being said, I have a good understanding of the code I am submitting and can defend it, as it is nearly entirely based on the existing implementation of the Windows 11 network flyout.

@Amrsatrio

Amrsatrio commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

Hi.

https://github.com/valinet/ExplorerPatcher/pull/5234/changes#diff-f347020d9725f4ccfc9780f9a767e93e3ced79cac114313ec19aa0de520a70d9R2518

I'm on 22621.4317 and ms-actioncenter:controlcenter/volume opens this:

image

Is that what you get in 25281+? If yes, please broaden the checks because I want Nickel (226xx/22H2/23H2) to stay supported. You can tell your AI to scan the binaries in https://winbindex.m417z.com/ to get the precise build range.

@4yx

4yx commented Nov 7, 2026 •

Copy link
Copy Markdown
Author

Yeah, that is what I'm getting.

The check I added is wrong; I'd traced the addition of the volume path to 25281, and tried the build before that (25276) which failed, so I incorrectly assumed it wouldn't exist in builds with a lower number (forgot that features get backported, and didn't really have a grasp on how Microsoft's build numbering worked, which I looked a bit more into now). Sorry for that, and thanks for checking and letting me know.

I had the AI look into it more with the resource you pointed me to, and it claims the first trace of the volume path of controlcenter exists since build 22621.2215 / 22621.2283 (same hashes on the files containing the relevant logic between those two builds) . I'd accept that as an answer, but at the same time I was doing some manual testing (installing older Windows builds and testing the URI) and it didn't work on 22621.2428, even though the path is supposed to be there.

So far I've successfully tested and found it working down to 22621.2506. My main problem right now is at how the strings clearly exist in some older builds (22621.2215...22621.2428), and yet, the routing to the Control Center works but the routing to the specific Sound output page does not. I'll keep looking and try to further narrow it down, as well as accurately find and explain why it isn't working on the other builds, and what the actual condition for its existence is.

@4yx

4yx commented Nov 8, 2026

Copy link
Copy Markdown
Author

Update: The AI and I are done investigating, and have successfully limited the checks to revision >= 2506 for Nickel (22H2/23H2), and any build higher than 25281 (so all builds after that, predating 24H2, and every 24H2 and higher build).

Scanning the binaries in winbindex, the AI found evidence of ms-actioncenter:controlcenter/volume existing in builds as early as preview build 22621.2215 and stable build 22621.2283, but the functionality to make it navigate to the sound output page is either absent or toggled off before preview build 22621.2506 and the subsequent stable build 22621.2715.

While the AI was doing this scan, I also had a look at Microsoft's support page for updates, and it seems to somewhat corroborate this. These two updates (KB5031455 / 2506 and KB5032190 / 2715) mention in their highlights the addition of the volume mixer, and the WIN + CTRL + V shortcut whose presence inspired me to try and add it as a sound flyout in the first place, so it makes sense to me that this is when this path was activated.

I have added an IsWindows11SoundFlyoutAvailable helper with this new information, and corrected the checks. If you'd like me to squash the commits, or need anything else from me, let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants