NOD32 v3 What A Mess!

[DasFox]

I had nod32 the other day popup an alert, and I asked it to delete the files, then today the alert goes off again, and I click the delete button and the alert popup keeps flashing up over and over as I clicked delete, and nothing happens.

Then I look in the directory and see the infected files just sitting there, well sorry guys that was it for me, and time to remove v3.

Then I went to uninstall and it said that the logs were being accessed by another program and to kill it then hit the Retry again, well I knew of no apps accessing this, nor was there any I was using.

After a few minutes of this, and a few reboots, finally I just shut off the services from running at startup, then the Eset directory was not completely removed and when I went to delete it, it gave me accessed denied over egui, so then I had to boot into safe to remove the directory.

WOW what an adventure guys, SORRY to burst some bubbles here, but I'm a PC geek, and this is not a final version of software, this should still be in RC, or Beta....

It's v2 for me again...

[SamSpade]

My problem (the one I could find during the 24 hours it was installed) was different -- I could not log off my computer; it would not shut down but just froze at the "Windows is shutting down" window (!!). So, with my personal experience and the other horror stories I'm seeing/hearing about on this heavily battered site , I share your sentiments.

Eset guys and gals: you seem to have rushed this one out before it was done!! Come on. We love you because you created a nice-working app in NOD32. Don't try to be something you are not! Let Kaspersky be Kaspersky; you just be Eset!!! If I wanted a suite full of bells and whistles I know where to find one; you are good because you do one thing very well: light, fast, good-working, reliable, safe anti-virus. Please keep your strength!!



||||

[DasFox]

Yes this came out way to early, this is clearly not stable final software...

[saffron]

Originally Posted by DasFox

Yes this came out way to early, this is clearly not stable final software...

The way I see it V3 wasn't ready for final release, but the salesmen had big promotions planned and they didn't want to miss the publicized release date so they pushed it out the door with all its known bugs and hoped for the best.

I feel a bit sorry for the ESET programmers. A few First Day Bugs sneak out with every new program but V3 had so many it must have been hiding under the bed while the Raid was being sprayed. Another week of testing and there would have been more praise than complaints, but the best turned sour and the spin doctors will be in Controllus Damagius Maximus for some time yet.