10-05-2012 02:25 PM - edited 10-05-2012 02:27 PM
As you can see by the subject history these 2 are in my history and recent history as trying to acess process data and it's been blocked. i really don't understand this setting and what is being blocked. I hope it's not my program cleanmem or OpenDNS. Are these processes that are being blocked by Norton or is the program being blocked or acess to the program? I think someone has told me not to worry about these history settings but I like to know what this means if that's ok with anyone in the know.
Solved! Go to Solution.
10-06-2012 06:08 AM
What is happening with Cleanmem.exe is that it is attempting to clean the Norton process memory usage, but Norton Product Tamper Protection is preventing Cleanmem from doing so, and thus the Norton logs are being flooded with this data. What I have done and would recommend doing is configure Cleanmem to use the ignore list and add ccSvcHst.exe to that list. This will tell Cleanmem to ignore the Norton process and the attempts should no longer be logged.
10-06-2012 06:51 AM - edited 10-06-2012 06:55 AM
I am assuming that you are referring to a firewall setting? I am not really good with those, so unles you can give me a little guidance I will probably get lost. Is this also happening with the Conhost and whatever else is in those Blocked History settings? I just get overwhelmed with these security suite settings sometimes. I just don't know how Noooobies get through all this without burning their computers down. I struggle and do have better than average skills. It almost sounds like Norton is blocking CleanMem frrom running the way it comes across in the settings, but it does run doesn't it?
I went to program control and didn't see any ignore list so I guess I am in the wrong area?
10-06-2012 07:03 AM - edited 10-06-2012 07:13 AM
Actually the setting is with CleanMem. Here is what you'll want to do:
(1) Open CleanRem Settings by clicking Start > All Programs > CleanMem > CleanMem Settings.
(2) Click the Next button until you get to step 3/4. Change the setting to "Ignore List" and then click Next.
(3) Click the little plus (+) sign and then type in "ccSvcHst.exe" (without quotations) and click OK.
(4) Click Next again and then click Finish.
Wait a day or two and then check the Norton logs again. CleanMem should no longer be listing.
What is happening is Norton has a Product Tamper Protection setting which is on by default (and should be left on) which prevents other products from changing Norton files, settings, and registry entries. This prevents malware from disabling or corrupting the Norton installation and increases security. However, since this protection is not selective it blocks all other programs from interferring, so Norton is loggin CleanMem's attempt to free up memory from the Norton process. In short, yes, Norton is keeping CleanMem from doing what it is trying to do, but only with the Norton products. CleanMem should continue working fine to free up memory for your other programs. There is really nothing to worry about with these logs, but I prefer not to having my Norton logs flooded with unnecessary data which can easily be remedied, so I tell CleanMem to ignore the Norton process (ccSvcHst.exe).
10-06-2012 07:05 AM
As for Conhost.exe I couldn't give a clear answer on that for now, but it is normal. Mine shows several instances of Norton Product Tamper Protection preventing Conhost.exe from interferring with Norton.
10-06-2012 07:19 AM
Done. One question while I'm here. Is CleanMem going to know what we're referring to when we use "ccSvcHst.exe" that is supposed to refer to Norton IS? I was just wondering if that shouldn't be refined a bit more, but if that's your setting and it works then that is how I'll roll.
10-06-2012 07:26 AM
Yup, that's exactly how I have mine. it just ignores all open processes by that name.
10-06-2012 07:33 AM
Conhost.exe has been asked about before on these forums. Simply type "Conhost.exe" in the search at the top of the forums page and it'll show you the results. It's nothing to worry about.
10-06-2012 08:00 AM
I guess this topic has freaked many a Norton user. I guess it's the way that Norton logs these items. I'd like it better if they just forget telling me about that. It really doesn't concern me in the fact that I need to make a decision. It's just info.