NOD32 Antivirus 2.7 or ESET NOD32 Antivirus 3.0

Hello,
Tell us what do you prefer, NOD32 Antivirus 2.7 or ESET NOD32 Antivirus 3.0?
Thanks for your opignion.

 

Version three without a doubt. The GUI changes and faster scann times are great in version three. But shouldn't this be in the poll section?

 

I send it in general section because there is too versions in my post.
But people talk that version 3 si slower than 2.7?
What do you think?

 

NOD32 Antivirus 2.7

 

I been using 2.7 for a long time and tried 3.0 without success several times, but since 3.0.657.0 i found 3.0 to be just as good and now using 3.0.667.0 without any issues. Regarding the speed/performance i cannot see any difference, but i never do on demand scans of my harddisk.

If you currently use 2.7 and thinking about upgrading i would recommend to save the settings, uninstall 2.7, reboot and then install 3.0.667.0. If you don't like it or have problems it's easy and fast to go back to 2.7.

 

Hi!

In security you have to come to realize that malware's routines and techniques are still better and software, which fight againt that have to be developed. Yes, v2 was nice and fast, but you can't stop development. I believe that problems will be solved fast. Wait for new version, which will provide more options.

 

Yes, if we are talking in general...BUT...In "brand new and improved" v 3 I've forced to disable Advanced heuristics and Runtime packers (in Realtime protection) in order to make my machine capable...v 2.7 worked fine with all settings on max...so I really don't see how v 3 can protect me better than v 2.7

 

I don't think this is a problem in general, but a problem that only some users seems to experience. So it's not exactly correct to say that using 3.0 you cannot enable these features. In your case that might be correct, but not necessarily for everyone else as well. I have runtime packers enabled for the realtime protection without any issues. I also have advanced heuristics enabled for created and modified files. I do not have advanced heuristics enabled in general (when reading files), but that option is not available in 2.7 so hard to compare. Using 2.7 you can only enable advanced heuristics for created and modified files unless i'm wrong. Using 3.0 you also have the option to enable advanced heuristics in general for the realtime protection, but it's not recommended to do so.

 

I'm talking about my experience with both versions...not in general. From my point of view there's a problem.

Good for you With this options enabled I have slowdown and randomly 100% CPU usage (not frequent).

Why then option to enable?!

Btw I can tell you my experience with web module, problem with Acrobat...but I don't want to go offtopic.

 

I was just adding some comments so MrGSM don't think everyone experience these kind of problems, but i'm in no doubt there could be problems in some cases like you describe. The best thing to do is to try the new version to see how it works since the result can obviously differ on different computers. It's really hard to decide which version is the best without try the new version since there is a lot of opinions.

Well i read a post from eset (I think it was Marcos) where he said it's not recommended to enable. I guess it's not recommended because of the performance hit, but still give the users the option to enable if security is very important and they can live with the slowdown. I can only guess since i don't know why it's there if recommended to not enable.

If you already posted about this issue i can see if i can find that post and read about it. Not that it will be of any help for you, but i don't have any issues with acrobat either.

 

V2 didn't support advanced heuristics and runtime packers on file access at all It's up to the user whether he'll enable these options at the cost of higher cpu utilization on file access when emulating certain files.

 

The issue with version 3119 and some Acrobat files was related neither to heuristics nor signatures. An update with a fix was released within an hour.

 

Thanks for the clarification

 

I'm not talking about problematic 3119 update...no...I talk about this thread https://www.wilderssecurity.com/showthread.php?t=196035 and your answer at the end of it...don't take it as offense but why then I don't have problems with other AV (see signature) in the same scenario? (btw I still use NOD32 on my second machine )

 

It's a good idea, but what i think is that v2.7 is faster than V3.0.
What's the main difference between V3.0 and V2.7, just graphic interface?

 

Again i read people claim that 2.7 is faster and some claim that 3.0 is faster. For me i didn't notice any difference. Maybe the result can differ on different computers......i don't know.

For me the main difference is that 3.0 will be further developed/enhanced. I find it hard to believe there will be any further developement of 2.7. 3.0 is supposed to be better at cleaning and smaller updates, but since i have not been infected in years i cannot tell based on my experience. GUI is changed and some features is added while some is removed and something changed. I'm sure someone else can fill in here.

I would still recommend to try out the new version and see for yourself. Maybe you like it and maybe not, but then it's easy and fast to go back to 2.7.

 

v2.7 may look faster on older computer with single core processors . However , on newer computers with multi-core processors , v3 is definitely the faster one . Modern computers do come with multi-core processors ("dual core , do more" )

I guess it is already further developed . The last version - 3.0.667 started the process or changes . It includes the anti-stealth support module (v 1001 currently) addition , which hasn't been not added in v2.7 , as far as I know . ESET are gonna make other changes which v2.7 users won't receive. Small things but with the time being they will become more and more ...
Users with NT based OS should upgrade to v3.

 

The first time Antistealth was added in 2.7.

 

Hi Kosak . I know that the anti-stealth was first added in 2.7 . I wrote about the improved part - something that is not added in 2.7 , AFAIK (si mple because v2's developement is not existing)

 

I agree it's already developed further, but as you said there is more to come while v2.7 will not be further enhanced. That is what i meant about the main reason for me to use v3 is that it will be further enhanced. What we seen so far since the first 3.0 release is mostly bugfixes and minor improvements, but i'm sure there will be more now that most of the bugs is sorted out.

 

Like shown here https://www.wilderssecurity.com/showpost.php?p=1266495&postcount=54
With NOD32 2.7 we have by default "Scan all files" is Ticked and it's faster than NOD V3, when we tick it in V3 we have 100% usage in CPU so we' will be not protected as well.

 

"Scal all files" is default for v3.0 , too . On my Intel Dual Core ~2 Ghz processor , v3 is faster and even ligher than v2.7

This is something specific , which not all users experience . You are protected with the "selected files extensions" , too . The kernel module and the on-demand scanner will continue scanning all files types and you can't get unprotected - don't worry about that

 

Personally, I'm not really concerned with how long it takes to do a manual scan, because scanning a 340GB of a 500GB HD is going to take a while, no matter how fast the scan is.

I periodically try the latest versions of 3.0, but v2.7 simply plays better with everything I have on my Vista duo-core. 3.0 seems to run more frequently and use more CPU when the computer is inactive, compared to 2.7.

So I continue to wait until a version comes along that will match 2.7's functionality on my computer.

 

You're ESET reseller, right?...and you say that v3 work for you (even lighter that v2.7...lol)...good...but on my machine NOD32 v3 don't work well as v2.7...and now I ask you as a paid user of NOD32 v3, which case is more relevant?

Not all but many of them...and many of them are on this forum.

 

I prefer Nod 3.0. However, there are still problems with the uninstall procedure.
I have a very basic setup and have to run uninstall more than once to remove NOD. The uninstall procedure is improved with the latest version but still has problems.