I am trialing NOD32. Every time that I install NOD, it flags a file called wrsssdk.exe from Webroot's Spy Sweeper program as a baddie of some sort. Can I ASSume that this is a false positive? There are two reasons for me to think so: number 1. I trust Webroot, and number 2. Neither my regular AV, nor any of the other AV that I am trialing, nor AdAware, nor Spybot are flagging this file. Thank you, Acadia
Thanks, Ronjor. Maybe NOD did not bother to fix this in the Trial version? (And yes, I did update the NOD signatures) Acadia
I´m using the trial version of NOD32 and SPySweeper, and got no false positive. http://tinypic.com/iy3rbn.jpg
Acadia, are you sure you are actually using the latest version 1.1332? I could't find any file wrsssdk.exe submitted via ThreatSense and still flagged as suspicious. It makes no difference whether you are a trial or paying user.
Are you sure you're not trying to run an old NOD32 installer? If I remember right, the installers were updated not so long ago.
Ok, folks, thanks for the replies. If the installer or version was changed within the past 2-3 weeks, then yes, I might be using something old. If I purchase NOD I need to uninstall the trial anyway. Thanks. Acadia
It doesn't matter whether you installed NOD32 2 weeks or months ago, if you have the latest update installed you shouldn't get any warning from NOD32 on that file.
Like I said, it only flashes that warning when I install NOD, not at any other time. I am constantly removing NOD and reinstalling it since I am also trialing other AV. Acadia
If I'm not mistaken, their installers gets updated once in a while, so maybe you should try and download the trial again. It could very well fix the issue you are experiencing
then don't worry about it - in 30 days when the trial EXPIRES, you'll not be able to see the problem any more!
Yup, that's basically the attitude that I adopted. I just want to make sure that it was indeed a false positive and that question has been answered. Thanks. (to everyone) Acadia
try uninstalling it, reboot, delet ESET folder from the installed directory, try a good registry cleaner, download a fresh copy from eset website, and try again...