Izagaia
06-20-2005, 10:05 PM
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005052514152448?OpenDocument&src=ent_hot&dtype=corp&prod=Symantec%20Client%20Security&ver=3.0&tpre=
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005042710304248?OpenDocument&src=ent_hot&dtype=corp&prod=Symantec%20Client%20Security&ver=3.0&tpre=
If I read both pages correctly, then I am under the assumption that SAV10 is performing some sort of "quickscan" after each time my virus definitions are updated. I do not have much of a problem with that, mind you- I hardly notice any change or slow-down in my system at all after doing so. However, on reading reading down further I see that SAV is also doing this "quickscan" each time Windows is rebooted/started. And I DO notice a considerable amount of CPU useage for an extended period of time after the Windows start-up/logon cycle. I am assuming it is this scan taking place.
Or is that right?.. :unsure:
If that is the case and if anyone else is experiencing a similiar scenario and would prefer this scan not occur... well- there is your fix then. ;)
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005042710304248?OpenDocument&src=ent_hot&dtype=corp&prod=Symantec%20Client%20Security&ver=3.0&tpre=
If I read both pages correctly, then I am under the assumption that SAV10 is performing some sort of "quickscan" after each time my virus definitions are updated. I do not have much of a problem with that, mind you- I hardly notice any change or slow-down in my system at all after doing so. However, on reading reading down further I see that SAV is also doing this "quickscan" each time Windows is rebooted/started. And I DO notice a considerable amount of CPU useage for an extended period of time after the Windows start-up/logon cycle. I am assuming it is this scan taking place.
Or is that right?.. :unsure:
If that is the case and if anyone else is experiencing a similiar scenario and would prefer this scan not occur... well- there is your fix then. ;)