Nod 32 - No thanks

It all started with a Virus as it always does. After re-installing your system and adding all your software required for your work you spent about 8 hours.

Then you seek for protection.. Never the other way around, protection first.

You ask all your collegues and friends for the best antivirus software out there and Nod32 is the answer according to many.

After release 3119 I beg to differ.
Adobe programs stops working and the Nod32 is to blame.

Fine I would let another update download and fix this. It's surely just a glitch.
Since Eset updates almost every day it should go fairly quickly...
Yeah right!!

Ive had 8 lockups, because every time the antivirus program updates the system hangs. Or should I say, not exactly hangs. You are just not in control anymore. [alt] [Tab] works.. but every application is locked.

And down to the right at the clock, you'll see the silly Clown balloon caused by the last Eset update so in fact you can see the last application causing this...

I say - let the next update sort this once and for all or every one should sue them.

Better finish writing this post before Eset updates again

One more lockup And I will tell my company and others that Eset no longer is secure enough.

 

Are you using v3.650? I would look into possible other reasons for the hangs. Clown balloon? I must have missed it.

 

More information please.
Version of Windows?
What Firewall?
Version Number of NOD32?

Are you using Blackspear's settings?

Thanks.

 

Of course the original poster is correct. NOD32 is solely responsible for all these system crashes.

Windows all around the world didn't just decide to **** itself at the same time.

 

Well !!!
I'm a ESET consumer for long time and never had problems... You are right, update 3119 causes some problems (false positive) but a couple of hour later, next release were OK, and thanks to all community posting on this forum, and ESET developpers... I still will deal with ESET because EAV is a great product !
Regards

 

I had the same issue following the infamous 3119 update. Even though I managed to restore all my files from quarantine and got my Adobe apps and others back, all subsequent ESET updates continued to hang my system thereafter.

I uninstalled ESS version 650, deleted the relevant registry entries and ESET folders that remained. I then installed version 657. That seems to have resolved the issue for me.

JD

 

I use NOD32 for years and I never had problems too...but problem with 3119 update was BIG PROBLEM! (which isn't mentioned on official site)
What about people who use NOD32 and don't know about this forum and what about people who trialing NOD32 for the first time?!

I have just one word: THE SHAME!

 

I have to admit to having missed this error, although I'm surprised we didn't experience it. I will have to do some backtracking to see where we are, and how we got past this.

I've been in IT, software, etc for 30 years (hate to say that!), been a CIO, CTO, run 300+ person consulting teams, and run strategy and support for many Fortune 100's, 400's, etc.

We've lived through Symantec/Norton eating machines alive, CA, McAfee, and just about all the others.

NOD32 hasn't been 100% flawless - but over the past several years, it's been darn close. I've had it installed in networks from 5 to 500 users, and only ran into two issues:

1) some problems our IT folks reported turned out to be purely due to misconfiguration.

2) once, about 5 years ago, we have a short-lived conflict between NOD32 and Backup Exec: seems that at the time, NOD32's entanglement in the winsock stack messed up the way the BE client and server communicated. That was solved in a subsequent release.

Aside from these, I've had teams installing NOD32 for several hundred people over the last few years, in a wide variety of configurations and environments, and it has been a home run every time. It is, by far, the lightest weight, fastest, and most unobtrusive AV product I've used, and it simply works. While it's been "on the job", even in relatively undisciplined user environments, NOTHING has gotten through.

I tend NOT to be a fanboy of products for their own sake, and I tend to revisit my evaluation of products every year or two, leveling the playing field and searching for "best of breed" each time. If something else turns out to be better - I will often drop the old product in favor of the new best of breed with little or no hesitation.

I have not seen anything that compares with NOD32 so far. From what I'm reading the problem in this thread, it sounds like a lot of folks just had a bad experience. I somehow missed this, and I guess I was lucky. But overall, the product has been SO good for SO long in so many different environments. I wish all commercial products would be this well thought out or written...

- Jon

 

it is this kind of well reasoned approach that is required in evaluation of software for the enterprise - the home users tend to be more of a knee-jerk reaction type decision making process... when we went through a similar review process of all the solutions available, we became resellers for Eset. We are also resellers for quite a few other major and minor vendors - in the AV/AS arena, it is Eset's Antivirus that gets my vote every time. In backup solutions - obviously an area that Eset doesn't work in, I am prone to recommending the Backup Exec solution from Symantec - do I recommend their AV solution... ahem.... if you have a compelling reason to STAY then it will renew ok...I guess....

There are far too few well rounded discussions in when a problem occurs - and far too many "give me my life back" type arguments... sometimes you need to step away and let the solution provider actually provide the solution (in this case the subsequent update)....

 

No doubt there is a need for cool heads. Its not like this wiped hard drives - unlike much of the software it most effectively protects us from. And as an IT Director I know it is impossible for any software company to test for all possible contingencies and potential conflicts. In other words sh*t happens (and when it does its a great reminder to back up).

But I do agree with those others who have questioned ESET's customer service response. I struggled for 5 hours trying to contain this before any mention of ESET's problem made it my way (though the problem had been identified by ESET hours earlier). And that was only after I found this forum via a Google search related to COMODO Firewall and virus infection. As for ESET I never received any kind of notification or email alert of any kind.

I have been using NOD32 for 3 years without incident. It has protected me several times from virus and malware threats. It has a small footprint, its fast, and its clearly effective. On all those I give ESET high marks. But on customer service on this matter I am afraid they get a failing mark.

In the future I hope ESET learns from this and does a better job of alerting all clients. Sending out an email alert to the email list (where all IT guys usually go first when something like this happens) is good corporate practice for any sofware company.