One client of mine got hit. ESET corrected the problem one hour later with an update which retrieved the False Positive from Quarantine and put it back in its original location.
I have been trying to get their Support on the phone for a different issue since then but they don't even call back. I am assuming they are inundated by calls because of this mistake, but that is no excuse for bad support. Peter -----Original Message----- From: Micheal Espinola Jr [mailto:[email protected]] Sent: Tuesday, March 10, 2009 9:49 AM To: NT System Admin Issues Subject: Re: NOD32 FP What did you have to do to recover? -- ME2 On Tue, Mar 10, 2009 at 9:39 AM, Steve Kelsay <[email protected]> wrote: > Yes. > > > > From: Andy Ognenoff [mailto:[email protected]] > Sent: Tuesday, March 10, 2009 9:20 AM > To: NT System Admin Issues > Subject: NOD32 FP > > > > Anyone hit by this? > > > > http://www.eset.com/joomla/index.php?option=com_content&task=view&id=5839&Itemid=2 > > > > "Unfortunately, an error in the heuristics module, coupled with the > specific virus signature database update, caused ESET to incorrectly > identify several Windows operating system files, including dllhost.exe and > msdtc.exe, as being infected with Win32/Kryptik.JX." > > > > - Andy O. > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
