Hi Zach,
If you look at this Topic:
Help me remove ad-aware se personal (temporarily), need removal tool , you will see that there were some problems with McAfee conflicting with Ad-Aware SE, until they were forced to issue a compatability patch.
Since these repetetive Reg Mods are coming from McAfee, I would like to ask you to post an Ad-Watch Event-Log, just in case the two are somehow related (and may be affecting others, who are yet to report it).
First, bring up the Ad-Watch GUI, click on Tools (bottom-right), then select Options > Blocking Options and configure as in this screen-cap, (if you have the first two selected
green tick, that may be the cause):
Click to view attachmentThen, to make sure that you have an Event-Log, select Options > Event History - make sure that "Create Event-History" is selected .
Click to view attachmentIf this is not currently selected, then please re-boot a couple of times, accepting the McAfee Reg Mods, to create Event details. Once the "AWEVLOG.txt" is created, just click on "View current event history", and copy and paste back here the Reg Mod events - a reg mod event would look something like this :
25/12/2006 9:09:14 a.m.> Registry modification detected
25/12/2006 9:09:14 a.m.>
25/12/2006 9:09:14 a.m.> Root:HKEY_LOCAL_MACHINE
25/12/2006 9:09:14 a.m.> Key:Software\Microsoft\Windows\CurrentVersion\Run
25/12/2006 9:09:14 a.m.> Value:MSConfig
25/12/2006 9:09:14 a.m.> Data:C:\WINDOWS\PCHealth\HelpCtr\Binaries\MSConfig.exe /auto
25/12/2006 9:09:14 a.m.> New Data:Yes, there is an "Ignore" function, but it would be better to find out why it keeps repeating and fix it, if possible. Sorry for the extra work
Regards,
Spike