G
Guest
Hi,
I have WinDefend B2 as well as Webroot SpySweeper (4.5.9 build 709)
installed on my XP Pro SP2 box. SpySweeper has a feature where it takes over
the
C:\WINDOWS\system32\drivers\etc\hosts file and uses it to block nasty sites
with regular updates.
The issue is that WinDefend detects SS's (apparent) access to the hosts file
and puts up an alert. I say 'apparent' because the WinDefend messages do not
identify the process or application involved. I will do more testing to be
absolutely sure that if I turn off SS's use of the hosts file, the messages
in WinDefend will go away, but the certainly began immediatly upon
installation of SpySweper.
I would like to ask the WinDefend folks if they have the means to detect
Spysweeper's processes and identify them to avoid the appearance of this
issue. One might ask why the need to run multiple programs for the same
purpose but I'm sure that's one we could debate all evening. It just
doesn't seem that one program does it all, yet.
Rob
I have WinDefend B2 as well as Webroot SpySweeper (4.5.9 build 709)
installed on my XP Pro SP2 box. SpySweeper has a feature where it takes over
the
C:\WINDOWS\system32\drivers\etc\hosts file and uses it to block nasty sites
with regular updates.
The issue is that WinDefend detects SS's (apparent) access to the hosts file
and puts up an alert. I say 'apparent' because the WinDefend messages do not
identify the process or application involved. I will do more testing to be
absolutely sure that if I turn off SS's use of the hosts file, the messages
in WinDefend will go away, but the certainly began immediatly upon
installation of SpySweper.
I would like to ask the WinDefend folks if they have the means to detect
Spysweeper's processes and identify them to avoid the appearance of this
issue. One might ask why the need to run multiple programs for the same
purpose but I'm sure that's one we could debate all evening. It just
doesn't seem that one program does it all, yet.
Rob