Registry change being reset

Ok, I've now completed steps 2-4, and the files created for step 3 all work when tested on their own.

However, I had the following issues:

Step 2 - There is no admin prompt when I add things to the Tools folder, despite following all the instructions. I notice that in Properties > Security, although Authenticated Users are now restricted to Read and Execute, System and Users both have full access - should I change either/both of those just to Read and Execute too?

Step 4 - Should the schedule be set to run at start-up, or log-on? I set it as start-up.
Also, having made the schedule, nothing happens when I try to test it by clicking Run. I've exported the task (creating an xml file) and would have attached it here, but using the image upload brings up a message saying it's an invalid file.

Ok, I managed to get it all working - I had the Action set up wrong.

Everything now works fine, and the registry values are updated properly whenever I reboot.

Thanks again Denis for all you did and explained to help me - much appreciated!

Now that it's too late (just found this thread right now) I'll chime in…

I've been braining this same issue for quite some time now too.

First for @AshleyJT , shouldn't you be using 00 00 00 00 rather than FF FF FF FF? I'm going off the info on this post: Windows 10 popping sound in speakers

Second for @Try3 or anyone else. I use the task scheduler to merge the .reg file containing those 3 keys.
I use this as my start program: "%windir%\system32\reg.exe", and use "import file.reg" as the arguments. It'll merge the entries without any prompts. Supposedly "%windir%\system32\regedit.exe /s file.reg" should work too. I should also point out that I'm using LTSC and keep secureboot disabled so that might have some bearing.

This has sort of fixed my problem with popping speakers (they still pop occasionally, just not a loud) There is another reg entry related to power management that constantly gets reset (not just during reboot) that I can't seem to lock.

Try3 said:

Not Bob,



Using Task scheduler to run a Reg command avoids prompts as both you and Ashley have witnessed. I suggested running Reg Add commands through a batch file whilst you are using a Reg Import command and you commented on a RegEdit /s command.
- All are valid methods
- All can avoid prompts

Because I have not tried using Reg Import commands or RegEdit /s commands in Task scheduler, I do not know if a command window flashes up on the screen or not. I always use batch files set up through an intermediary vbs script to avoid this.



Finding out how to counter an unpredictable change can be very difficult. If there is a particular sequence of actions that causes it then you might get somewhere by
1 Seeing if Event viewer records anything you could use as a marker to trigger a Task scheduler task to reset the Registry value concerned.
2 Monitoring the processes that take place at the time using MS SysInternals ProcMon
But investigating things using either of these tools can make your brain melt.

You could post a request for help in a TenForums thread of your own in the hope that somebody else has the same hardware and sees the same symptoms.
- Include the name & version of the hardware in the question title itself so that you attract the attention of somebody who knows about the subject.

Best of luck,
Denis

I hear you about melting your brain. TBH, this .reg/task schedule thing is probably above my pay scale to begin with.
I might give that sysinternals monitor a look, I also might check the powercfg stuff you posted initially. I can confirm from using ancient drivers that this popping problem will go away if I disable power managment to the sound chip. Of course Realtek removed that option from their control panel a while back, so I need to find another way to do it.

I did post a question in the thread I earlier posted, but no response yet.