NIS 2012 reinstalled after removing NIS2011-- removed from programs (Vista ultimate 32 bit0 then ran removal tool twice between reboots, Have been using for several weeks and everything seems OK. Noticed Quick scan messages showing no threats founs. Then immediately ran manual quick scan it found many cookies. Have repeated this a couple of times. Settings are set to remove cookies etc.
malpaso started a discussion of this on Nov.1 and I responded Nov.2 as I noticed the same thing. I'm using 2011 NIS,IE8. From the discussion that malpaso started someone mentioned if you have IE9 that IE9 does most of the removing of cookies so not much done by NIS. You might want to read this discussion. It doesn't pertain to me because I have IE8.
Holly
The last reply to malpaso was today.
Holly wrote:It doesn't pertain to me because I have IE8.
Holly
Same here using IE8 and FF 7.0.1.
this can NOT be the case becuase the manual scan was run immediiatly aftwr the auto scan
I dont believe the automatic quick scan removes cookies
Well it should and did in 2011,
I believe you are incorrect! Auto quick scan is suppost to remov cookies.
Perhaps someone can clarify for us
In NIS2010 or 2011, when idle quick scan runs, will it detect tracking cookies?
Calls wrote:
Perhaps someone can clarify for us
In NIS2010 or 2011, when idle quick scan runs, will it detect tracking cookies?
Hi Calls. If auto quick scan did remove tracking cookies, the weekly idle full system scan would never find any.
Consequently, idle quick scan does not remove tracking cookies unless it is called manually by the user (from Norton Tasks) or the idle quick scan is run as part of an out-of-date-warning live-update-session.
As far as I am aware, the above is by design.
The following is my reasoning for why things work the way they do - and is subject to modification by any Symantec Employee who knows more about the process than I do:
On powerful machines, it is possible for the web browser to incur a very small CPU load. As a result, idle quick scan could run on this class of machine while the web browser is in use. Thusly, if the idle quick scan did remove active tracking cookies while the web browser was in use - this could disrupt an active browser session.
That's not a very good idea. The browser would then be the slave of two masters concurrently - with no mechanism in place to prevent conflicts between the cookie management the browser is expecting to perform - and the cookie management the idle quick scan is expecting to perform - on the same cookie fileset.
So, for safety's sake, it is better to err on the side of stability and reliability of browser sessions - and thusly idle quick scan is prevented from modifying the cookie fileset while there is a good possibility the browser is in use. IMO, this is a sensible and prudent precaution.
The weekly idle full scan is the logical place for tracking cookies to be deleted. Since an idle full scan cannot start until the idle time has expired (default of 10 minutes) - all browser sessions would be inert (no activity) when the full system scan started. As a result, a tracking cookie scan could be performed safely as part of an idle full system scan.
Hope this helps your understanding.
As far as I remember, NIS 2011 and this new one are both operating in the same way, in that an idle quick scan doesn't remove tracking cookies but a manual one will. Mine literally just completed a quick scan and deleted none. I immediately ran a manual quick scan and it deleted 32 cookies!
I am using IE 9 sp1 64bit, NIS 2012.
NIS 2012 reinstalled after removing NIS2011-- removed from programs (Vista ultimate 32 bit0 then ran removal tool twice between reboots, Have been using for several weeks and everything seems OK. Noticed Quick scan messages showing no threats founs. Then immediately ran manual quick scan it found many cookies. Have repeated this a couple of times. Settings are set to remove cookies etc.