ESET NOD32 Antivirus v3.0.672 discussion thread

[agoretsky]

Hello,

Please use this message thread to discuss ESET NOD32 Antivirus v3.0.672.0.

You are welcome to discuss things you like, experiences with installing and using the software and so forth.

NOTE: If you have require assistance troubleshooting the program or wish to post a bug report, please create a new message thread to discuss it as these types of message threads tend to become very large over time and the issue may not receive prompt attention from ESET's support staff or developers if it is posted here.


Regards,

Aryeh Goretsky

[ASpace]

Well , the eset.com site/servers still point to 3.0.669 build

[ronjor]

Changelog for ESET Smart Security and NOD32 3.0 (http://www.eset.com/joomla/index.php?option=com_content&task=view&id=4113&Itemid=5){QUOTE-> August 22, 2008 - 3.0.672

* Fixed problem causing instability on Microsoft Windows Vista 64-bit
* Fixed problem in antispam module causing "Unexpected exception 003 and 007" error messages <-QUOTE}

[element119]

thank you!!!!!!!

[reelmccoy]

As HiTech_boy points out, the page to download the Vista 64 bit version is still 669. http://www.eset.com/download/home-64bit.php

This may explain the support ticket e-mail I got. They probably wanted me to try the new release. :)

[ASpace]

{QUOTE-> As HiTech_boy points out, the page to download the Vista 64 bit version is still 669. http://www.eset.com/download/home-64bit.php

This may explain the support ticket e-mail I got. They probably wanted me to try the new release. :) <-QUOTE}

Actually , as of now , the version should be 3.0.672 . Even though the site says 3.0.669 , the version which the server provide is signed 21 August.

[ronjor]

This ESET partner has all versions posted for download. http://www.computersecurityassociates.com/downloads/downloads.htm

[reelmccoy]

Sure enough. Downloaded and installed the 64 bit version and it is 672. It's just the reported version on the page that needs updating.

Thanks, ESET. Now to install this on 2 more systems and inform some friends to download the latest. :)

[Roadkil]

I'm guessing by the change-log that this still doesn't fix the 100% cpu usage. So is the only solution to solve it to disable AH and runtime packets still?

[TBacker]

Just lurking in this forum, I get the feeling that the 100% CPU problem won't be fixed, because it seems ESET doesn't think it's a problem, rather it's the price one pays to use the AH and the runtime packer scan features.

I for one would say if it's that indeed the case, if a feature is that "expensive" in processing cycles, and needs to be turned off in most cases, it's not worth having in the app.

[Roadkil]

I still don't understand how ESET can say its not a problem and fix it when it takes up 100% cpu usage and doesn't allow anything else to run and locks up the system until it decides to release the CPU. How can this not be a bug?

[John2222]

agoretsky, can we get some kind of update on the 100% cpu problem please?

The ESET users here are probably your most technical ones and your first line of defense for our clients using your software. The problem has been open now for 3+ months.

Can't we just know where it stands or what is happening?

[Marcos]

{QUOTE-> The problem has been open now for 3+ months.
<-QUOTE}

Does that mean that you didn't have this problem with older versions? If you think the issue started occuring after upgrading to a newer version than 3.0.650 or so, I could provide you that older version so that you can test it and confirm or deny that it makes a difference.

[John2222]

{QUOTE-> Does that mean that you didn't have this problem with older versions? If you think the issue started occuring after upgrading to a newer version than 3.0.650 or so, I could provide you that older version so that you can test it and confirm or deny that it makes a difference. <-QUOTE}
No I didn't have the problem with 2.7 (Vista Home Prem), but did with 3.0.x. I reverted back to 2.7 for awhile, now have 3.0.669 running ok with Advanced Heuristics and runtime packers disabled. I've been following the 100% cpu thread which as I said has been active/open now for 3+ months.

Is it a secret what ESET is doing to correct this problem? Just a short synopsis of the current status and plans would help me (and others) understand what is going on and what to expect.

[mongatu]

I think you can see how ESET deals with such issues as this from the way they handled the BSOD issue on x64 machines. They basically didn't admit it was a problem with their software, and just asked for memory dumps from people having problems, and never gave any public info. Finally, after a couple of months, they came out with a new version that is claimed to, and hopefully does, resolve that issue.

My GUESS is we can expect more or less the same regarding the 100% CPU issue. THere will be a cone of silence (essentially refusing to publicly admit there is a problem) until they are ready to release a new version that addresses (and hopefully fixes) it.

It would be great if they would prove me wrong by addressing and answering your questions in a serious and detailed manner.

[BerserkerPup]

You know, this is disappointing to hear that they haven't fixed a problem that has been occurring for months now. It seems silly that users have to disable portions of their protection in order to have the program run without interfering with other programs.

I periodically try the latest 3.0 versions, but have always returned to the 2.7 one. I see no reason to even try this version.:-\

[SpHeRe77]

Hi, I’m running version [3.0.677.0] and have had no major problems. When installing an update can I install straight over an existing version or will I need to uninstall any one before I install this?

Thanks Sphere

[cocolucho]

Version 3.0.677.0 ??????

[nmadani]

{QUOTE-> I think you can see how ESET deals with such issues as this from the way they handled the BSOD issue on x64 machines. They basically didn't admit it was a problem with their software, and just asked for memory dumps from people having problems, and never gave any public info. Finally, after a couple of months, they came out with a new version that is claimed to, and hopefully does, resolve that issue.

My GUESS is we can expect more or less the same regarding the 100% CPU issue. THere will be a cone of silence (essentially refusing to publicly admit there is a problem) until they are ready to release a new version that addresses (and hopefully fixes) it.

It would be great if they would prove me wrong by addressing and answering your questions in a serious and detailed manner. <-QUOTE}


Hi - I couldn't agree with you more about this. I also think that the majority of AV products are overrated and NOD32 is no exception (e.g. see this link: http://winnow.oitc.com/AntiVirusPerformance.html). The greatest advantage of ESET having such a fan base is that it helps improve support. Users are more likely to post in public forums and problems are more visible. At the same time, I do not believe that any of the other security products fair better in this respect.

[SpHeRe77]

{QUOTE-> Version 3.0.677.0 ?????? <-QUOTE}

Yeah I know, but I have had no issues. Just didn't see any reason to update just to have the latest version...

Thanks again

EDIT[Installed working fine]

{QUOTE-> If you have not run into any issue, there's no reason to upgrade to the latest module and it's enough to wait for an automatic program update.

http://www.wilderssecurity.com/showpost.php?p=1275083&postcount=5 <-QUOTE}

[Alpine]

Ok, I'm a bit confused here. The latest release apparently fixes some issues with 64-bit stability. Yet the 64-bit version is still 669? What am I missing here? The only updated builds are for 32-bit Home/Business builds. The link on the site to 64-bit installs are still 669. None of the people downloading these new builds are actually running a 64-bit Vista OS. If they are, the site directs them to 669 builds. So how does this improve 64-bit stability if its a updated available only to 32-bit users? :-\

And if 3.0 is essentially a hybrid that runs in 32-bit on a 64-bit system but can run certain aspects in 64-bit when the OS calls for it, why the hell is there even a seperate 64-bit install version to begin with? Wouldnt it run on both 32 and 64 the same anyway according to ESET's own FAQ?

It doesn't make much sense to me...

Thanks in advance.

FROM FAQ
{QUOTE-> ESET NOD32 Antivirus 3.0* is a hybrid program in that it contains both 32-bit and 64-bit program code. The engine and interface modules used by ESET NOD32 to protect a system from malware are the result of years of development to create highly-optimized x86 assembly language code. During testing, it was discovered that recompiling certain portions of the program to 64-bit code resulted in increased memory usage with no discernable improvement in performance, stability or reliability.

When a 64-bit interface needs to be monitored, such as for on-access or Windows Socket layer scanning, 64-bit code is used to do so. As evidenced by ESET NOD32's high scanning throughput and detection rate under 64-bit operating systems, this does not cause any complications.

The general rule-of-thumb for ESET NOD32 Antivirus 3.0 is that parts of the program which need to run as 64-bit do, while parts which have no advantage running as 64-bit remain 32-bit code. <-QUOTE}

[Bakker]

Just to confirm, the 64 Bit fix in this release, is it the one where a BSOD would occur after logging into windows and NOD32 was loading?

The one where people sent in their full memory dumps and such?

[element119]

{QUOTE-> Just to confirm, the 64 Bit fix in this release, is it the one where a BSOD would occur after logging into windows and NOD32 was loading?

The one where people sent in their full memory dumps and such? <-QUOTE}

THATS correct, and seems fixed for me also.

[element119]

{QUOTE-> Ok, I'm a bit confused here. The latest release apparently fixes some issues with 64-bit stability. Yet the 64-bit version is still 669? What am I missing here? The only updated builds are for 32-bit Home/Business builds. The link on the site to 64-bit installs are still 669. None of the people downloading these new builds are actually running a 64-bit Vista OS. If they are, the site directs them to 669 builds. So how does this improve 64-bit stability if its a updated available only to 32-bit users? :-\

And if 3.0 is essentially a hybrid that runs in 32-bit on a 64-bit system but can run certain aspects in 64-bit when the OS calls for it, why the hell is there even a seperate 64-bit install version to begin with? Wouldnt it run on both 32 and 64 the same anyway according to ESET's own FAQ?

It doesn't make much sense to me...

Thanks in advance.

FROM FAQ <-QUOTE}

the site says the wrong version. but the downloaded file is correct. at least that was the case for me.

[SaphireX]

Just installed the "new" Vista 64-bit version on a fresh install of Vista Ultimate 64 and no problems so far...The previous .669 version on install did cause a crash after it was running for awhile and forced a reboot (no BSOD) and it also deleted without my consent.... some critcal files from the Lexmark 64-bit printer drivers?

So this new version did not delete any Lexmark files and after a full in-depth scan - all options checked and with auto cleaning turned off no threats!

Good Work ESET

SaphireX

Version of virus signature database: 3385 (20080825)

Scanned disks, folders and files: Operating memory;C:\Boot sector;C:\;F:\Boot sector;F:\;G:\Boot sector;G:\;H:\Boot sector;H:\
Operating memory - is OK
Number of scanned objects: 273376
Number of threats found: 0
Time of completion: 2:50:13 PM Total scanning time: 1489 sec (00:24:49)

http://img.photobucket.com/albums/v242/Saphirex/8-26-20084-04-01PM.jpg

[Bakker]

{QUOTE-> THATS correct, and seems fixed for me also. <-QUOTE}
Hmm that'd be nice,

I'm going to leave .650 on those clients for a few weeks though, and i'll monitor the forums.

[agoretsky]

Hello,

I am checking with our web team. The version number should be corrected shortly.

Regards,

Aryeh Goretsky

[PcVersteher]

Hello Eset!
What is wrong with you?
The scanner becomes more slowly version of version
NOD32 ignores exclusions completely
Under or optimized scan intelligent I understand of files that files scrutinized before will not be scanned any more.
The Tray icon orange and is regular the lied reports not been carried out update or false user name or password.
If something does not improve soon there, I become of eat my available exchange, licence not activated yet. In every regard a new product in a yellow box of which ESET digs off the water against.

Translate with linguatec Personal Translator 2008

Best Regards

PcVersteher

[ALEX(XX)]

Hello! Such question, there was version 3.0.672, in it have corrected a bug shown in work under х64 Vista. Before there was version 3.0.669. In time to an exit of the new version almost all modules of an antivirus were updated. If I have correctly understood, updatings of modules of an antivirus insufficiently and it is necessary to download version 3.0.672? Whether So it? Excuse for English, I use the translator.

Yours faithfully, ALEX (XX).

[DarkButterfly]

I was a user of Eset NOD32 3.0.669.0 and had no problems of what so ever with CPU usage. I upgraded to 3.0.672.0 and CPU usage at 100%. The "solution" I found was to deactivate AP and then activate again, but the all process takes a hell of time. Not what users want as a solution.

I know went back to 3.0.669.0 and fine again.

What is exactly the problem with this issue? Why isn't there a fix, yet?

[rnfolsom]

{QUOTE-> . . . Please use this message thread to discuss ESET NOD32 Antivirus v3.0.672.0. . . .
NOTE: If you . . . require assistance troubleshooting the program or wish to post a bug report, please create a new message thread to discuss it as these types of message threads tend to become very large over time and the issue may not receive prompt attention from ESET's support staff or developers if it is posted here. <-QUOTE}
Aryeh Goretsky

Understood --- except, where should a troubleshooting or bug report new message thread be put? Directly under the parent of the current thread (ESET NOD32 Antivirus Forum), or in some other location that distinguishes NOD32 v3 from NOD32 v2?

Cordially, R.N. (Roger) Folsom

________________________________________________________________

P.S.: NO NEED TO REPLY TO THIS P.S.!
You may (or most likely do not! <grin>) remember me from a year or more ago when we corresponded about:
a) a false positive threat report (i.e. a threat that wasn't a threat, because it involved a now never-used utility called Envoy, then distributed with WordPerfect), and
b) some suggestions I had about improving the NOD32 interface.

You did a great support job with regard to item a), and you apparently appreciated my b) suggestions (or at least were courteous about them), and invited me to beta test 3.0, but unfortunately I had to decline due to time constraints.

Last week I had another need for support (this time about an apparently real threat, caught by a Nod32 v2 routine in-depth analysis demand scan). The problem did get solved, although since I had to innovate, my solution was inefficient and denied Eset some information which might have been useful to Eset and its users.

Based on that most recent experience (admittedly, a statistically inadequate sample of a single incident), the quality of Eset's support has declined down to Dell's worst levels.

If your time (or the time of some other Eset manager) permits, I encourage you to look at the following case numbers: .438708.212594_4400933_115374.4d83fcc91d.
In addition to my initial telephone support request (which went reasonably well, although one of my emails did suggest some improvements), there should be a total of four emails between Eset and me, each subject line containing the number 175949. In the last of these emails, I requested that the case be closed, so there's no need for you (or anyone else) to follow up. Please do not follow up with me. But "in-house," my judgment is that Eset's technical support needs improvement, to reach its earlier high standard.

Nevertheless, today I've renewed my three NOD32 licenses for another two years, and will download version 3. I'm looking forward to trying out the new user interface, on my now rather elderly Dell and IBM laptops.

Cordially, Roger Folsom

[agoretsky]

Hello,

Normally, I would expect someone to start a new message thread. That way, they would receive prompt attention to the issue they are reporting.

I will check on case # 175949.

Regards,

Aryeh Goretsky

[JuliusB]

I'm currently using version 3.0.667.0.
Will it update automatically or do I need to update it manually?
Also are there any other fixes or benefits updating to this new version or just vista 64 crash bug fixed? I am using vista 64 and it's always very stable.

[rnfolsom]

{QUOTE->
Normally, I would expect someone to start a new message thread. That way, they would receive prompt attention to the issue they are reporting.
. . . <-QUOTE}
Understood. But from your answer, I guess the answer to my question of "where should a [NOD32 v3.x] troubleshooting or bug report new message thread be put?" is to put it in the "ESET NOD32 Antivirus Forum," since apparently NOD32 v3.x and v2.x don't have separate forums.

But including "NOD32 v3" in the new thread's subject line would probably be useful, to attract v3 users and potential users and to avoid wasting the time of committed v2 users.

Thanks.

Roger Folsom

[doktornotor]

{QUOTE-> since apparently NOD32 v3.x and v2.x don't have separate forums.
<-QUOTE}

Hmmmm? ???

NOD32 v2 Antivirus Forum (http://www.wilderssecurity.com/forumdisplay.php?f=16)

[rnfolsom]

{QUOTE-> Hmmmm? ???
NOD32 v2 Antivirus Forum (http://www.wilderssecurity.com/forumdisplay.php?f=16) <-QUOTE}

Thanks for correcting me. Since there is a NOD32 v2.x forum, apparently the "ESET NOD32 Antivirus Forum" would be the default forum for new NOD32 v3.x threads, as well as for new threads applying to both v2.x and v3.x.

Roger Folsom

[Bizadi]

I still have v3.0.657.0 on my 32-bit system. Should I update to v3.0.672 or not worry about it? And why does ESET not notify its licensed users via e-mail when a version change is released (no, my e-mail filter is not blocking them)?

[funkydude]

The current version is 3.0.684.0 and yes I recommend you upgrade as it has several performance improvements.

[Bizadi]

Okay, but why do I have to come to this fine forum to learn of a new version? Shouldn't ESET be contacting me directly?

[funkydude]

{QUOTE-> Okay, but why do I have to come to this fine forum to learn of a new version? Shouldn't ESET be contacting me directly? <-QUOTE}

I've wondered that aswel. Come v4 we hope ESET push these "engine" updates as PCUs. (Downloadable via updates)

[mickhardy]

{QUOTE-> I've wondered that aswel. Come v4 we hope ESET push these "engine" updates as PCUs. (Downloadable via updates) <-QUOTE}
This comes up quite often. Consider the readers of this fine forum to be release candidate testers. The newer versions are released to us and anyone else who likes keeping things ship shape. If we don't have too many issues, the releases are scheduled for the rest of the world via automatic updates.

I think this is OK even though I've requested a more granular approach where the specific version is offered and previous roll back versions are also available all through the automatic update engine.

In reality, using ERA, and a small amount of effort, this scenario is already available for business users.

V4 Beta is rock solid in my humble opinion but I don't think they'll change this particular philosophy.

[Bizadi]

{QUOTE-> This comes up quite often. Consider the readers of this fine forum to be release candidate testers. The newer versions are released to us and anyone else who likes keeping things ship shape. If we don't have too many issues, the releases are scheduled for the rest of the world via automatic updates.

<-QUOTE}

Other than the daily signature database updates I have never received an engine (or NOD32 version) update automatically from ESET. Am I missing a setting or something? It really is quite irritating to "only" hear about the new NOD32 update from this forum. ESET knows my e-mail address and I have paid for Smart Security so why don't they simply notify me directly to tell me about improvements?

[mickhardy]

{QUOTE-> Am I missing a setting or something? <-QUOTE}
The options under advanced update settings control the program component updates. You won't receive a major version automatically like V3 to V4 but you should recieve minor version upgrades a few months or more after they are released for download.

You'll receive emails from ESET when your license is about to expire or you submit a support request. They might also let you know about a major release. I seem to remember being emailed when V3 was released.

Check this thread (http://www.wilderssecurity.com/showthread.php?t=230624) out.

205581

[Bizadi]

Thank you for the Advanced setup tip and thread link.