[Byteman]

I haven't seen this posted at TechGuy forums so here you are>

ESET Smart Security / ESET NOD32 Antivirus detected some Windows files as Win32/Kryptik.JX and quarantined them

http://kb.eset.com/esetkb/index?page...tp=LIST_RECENT

[perfume]

That's a chiller of a post! ESET has to answer that. Till now,Nod32 was held in high esteem as a leader in A-V programs with KAV not far behind! I really think we seriously take note of all the posts by lotuseclat79,showing us how vulnerable a PC is,when connected to the internet. Thanks for the post!

[TOGG]

There's a 'Sticky' in the NOD32 section over at Wilder's Security Forum about a 'rogue' update (which I had noticed, but ignored, since it didn't affect me); http://www.wilderssecurity.com/showthread.php?t=235606

I suppose even the best programs can suffer glitches from time to time but, if the Eset statement is to be believed, they acted promptly to deal with this (although I appreciate that that wasn't much comfort to the 5% that were affected!)

The current definitions are at 3942, which shows how things have moved on since 9th March.

[Byteman]

When we post notices like this, it isn't meant (at least from me), that the program is bad,..... it is meant to give folks that may be using it a heads up.... those who could hear about the problem before they had certain computers "turned on" could possibly avoid getting the bad update. I've come to read posts here many times and gotten a just in the nick of time warning

If a widely used program has a system-crippling update given out, it is common to find posts about them in our Stickied threads at the top of the main forum pages.

In Dec 2007, a Kaspersky update found a virus/malware in Windows Explorer (false detection) , which did cause a lot of grief for those who were using Kaspersky and got the update.
http://www.kaspersky.com/technews?id=203038717


Those who had their antivirus program set to delete, and not quarantine, found themselves having to pull new explorer.exe file into Windows.

[TOGG]

I didn't intend my response to be seen as a criticism of the original post, nor as any sort of 'defence' of Eset, so if it read like that, I apologise.

I just thought that it might be helpful to any NOD users who were alarmed by the 'headline' to know that the error had been noticed and dealt with fairly quickly.

As you say, anyone allowing their AV to 'delete' rather than to quarantine suspect files could have found themselves with serious problems if the misidentified files had been crucial (perhaps they were in the Eset case, I don't know enough about Windows to be able to tell!).

[Byteman]

TOGG- You should have been able to see who I was replying "to" from looking at the post before mine..... a reply is not always answering the post immediately before it.

Usually, I put the person's name at the beginning so that any other poster does not feel that my post is directed at them....

In this case I didn't but I will try hard to. I was replying to perfume, who commented about the reputation of Eset etc and I was trying to point out that false positives etc are quite common