It might help understanding what I'm trying to do in order to contextualize my question, so here goes.
I'm trying to hack the realtek sound jacks on my mobo to have the front audio stream routed out both the back panel's green and black jacks. Realtek drivers, or windows itself has really messed up quadrophonic audio, and speaker fill, so this is the only way to go for getting music out both jacks on my setup.
To do this (based on info from around the web, such as here) all that's needed is to change the values associated with some registry keys. I followed the registry rabbit hole to
and look for
"Pin14" = Front speakers (rear green) "Pin15" = Rear speakers (rear black)
Pin15 has to be changed to
"04 00 00 00" = Front speakers
to source the same front speaker signal on both output jacks.
OK cool, right? only in theory... I can make these changes, but when I reboot to make them take effect I see in regedit that the values have been switched back to default.
I found one supposed solution that said to go to
[...]\00XX\GlobalSettings and change
ResetAudioFgOnStart to value 0. No luck on my system, still refreshes default pin values on reboot.
So, I conjured up an idea to change the registry and key permissions, with the idea of preventing the values reverting to default on reboot.
[...]\00XX key I disabled inheritance but converted the default inherited permissions to explicit permissions for this key and its child objects (and subkeys) so I could manipulate their access. I restricted write access, leaving read access available for all principals that were listed when inheritance was previously enabled (i.e. SYSTEM, CREATER OWNER, ALL APPLICATION PACKAGES, Users, Administrators...). I only left write access for administrators since it is the owner, and I obviously need to change the permissions to what I'd like them to be. I selected also 'replace all child object permissions...' to make sure those changes were recursive.
However, for whatever reason, after a reboot the default values are still loaded up, preventing my changes from taking effect. Maybe I should have revoked administrators write access after making my changes to the values, but before the reboot (was pretty sure i tried that too... but it was a couple days ago now I was fiddling with this)?
Why didn't my changes to the permissions of this key tree prevent the values from reverting on reboot?
Any ideas how to lock those values I want in the registry?
EDIT: uploaded screen capture of my registry settings (yes i whited out my user name, nsa is watching :p), after manually making changes myself to the registry value I'm working on. This shows all the deny permissions (for SYSTEM, CREATOR OWNER, ALL APPLICATION PACKAGES, each locking them out of set value, create subkey, notify, create linnk, delete, write dac, write owner actions) included to prevent not just write access, but lock out the permissions for everyone but administrators group. Still, the value gets reset to the default once rebooted. Maybe the administrators group is the culprit, I doubt it since a popup would be expected to give administrators access for an operation, so I suspect it is a system process of sorts.
WELL can't post an image since I don't have 10 reputation, ugh... whatever, stupid internets, not like the post makes it sounds like I'm absolutely clueless