ESET NOD32 Antivirus 3.0.667 released

Hello,

ESET NOD32 Antivirus v3.0.667 has been released in English, Slovak, Czech, Polish, Russian, Hungarian, Croatian and German. Other language versions will follow shortly. This release contains the following main changes:

- improved stability for Microsoft Windows Mail users
- improved reinstallation / upgrade process
- improved Antistealth to detect new kinds of rootkits
– fixed delay issue when opening files from network

Licensed users can download their registered versions here from the Download section of ESET's web site.

Even though reinstallation over an older version is fully supported, those who have been experiencing issues may want to uninstall the current version first and install the new one from scratch.

In the case of any persisting problems, try deleting the "C:\Documents and Settings\All Users\Application Data\ESET\ESET NOD32 Antivirus" folder (on Vista it's "C:\Users\All Users\Application Data\ESET\ESET NOD32 Antivirus") after uninstalling the previous version and prior to installing the new one.


Regards,

Marcos

 

Clarification Please,

Is the download page correct(20MB) or is the file size(17MB) I just downloaded ?

Code:

[U]Revision Number[/U] {6FCED904-886A-4D1D-9CE4-198679D17E5A}

 

Marcos, are you planning to release this version in more languages?

Thanks.

 

Yes, other language versions will follow as soon as they pass the pre-release QA testing.

 

As it is not mentioned in the fix list can I conclude that the problem with the limit on the length of the computer name when sending alerts via SMTP is not yet solved?

Regards
Preben

 

I suggest a immediate manual signature update be performed. I downloaded and installed 667 and the sig definitions were at 3192 and they updated to 3198 after I did a manual update.

 

Hi!

Here is another mistake:

 

When can we expect some Program Component Upgrades? It's quite troublesome having to manually install the new version upon a new release.

 

Does this version fix the 100% cpu usage?? I hope so. **crossing fingers**

 

Quick question.

With NOD32 6.0.657 and earlier versions running on Vista 32-bit I would see the following drivers under Non Plug and Play Drivers in Device Manager (have to do View, Show Hidden Devices to see them) - EAMON, EPFWTDIR and EASDRV.

In fact, those entries would still show up after uninstalling 657 and earlier versions. I would manually uninstall them before installing any new version, which I did before installing 667.

I notice with 667, that these entries don't show up in Device Manager any longer. Is that the case for everybody on Vista 32-bit, and is that intended by ESET?

 

new module: Anti-Stealth support module: 1001 (20080616) !!!!!!
this looks like a major update.

 

I stopped the service and both processes and attempted an overwrite...I would not advise it. You can disable the AV but you can't 'stop' it as you could with v.2.7 which I think makes it hard to overwrite.

My old settings were jumbled, some before were there, some gone. When making a test re-boot, the NOD tray icon would turn red - warning that updates were 'out of date', and that was when they were just updated previously and all update scheduling settings checked and reset.

I rolled back to an Acronis image I made with v.xx.657 in play. I'm not attempting a clean install as it's just not worth it. Something is just not right with this version in my opinion.

 

This update doesnt seem to fix the 100% CPU problem that has plagued the last few releases.

Still getting the 'Amon: Released File: PortLoop' error in the Eset Event Log every 20-30 seconds.

 

I have never been affected by the CPU problem. And all my Eset Event logs are all A.OK. I wonder why it is affecting some and not others
By the way NOD32 updated on it own this morning after last nights manual update. I always think it wont..... but it does.

 

Im not sure why it effects some machines and not others. I currently have around 1100 machines running Nod32 and the 100% CPU issue only effects around 40 of them, the others all run with no CPU issues.

Hopefully Eset will put a little more effort into resolving this issue now that 3.0.667 has been released.

 

I extremely agree with you.
My customers will most happiest if PCU finally works.

 

Hmm interesting Tragard.
Sorry if youve been asked this before but is there anything that is common amongst the affected machines ? Something which is unique to those and not to the unaffected ones ?
Thanks.

 

Just for the purpose of a test, could you set the real-time file protection to scan only files with default extensions (these may potentially carry malicious code) instead of all files? Does it make a difference?

 

Marcos,

That does seem to resolve the issue, however it's less than ideal, especially as we have already had to disabled scanning of web traffic due issues with ekrn.exe crashing when accessing certain secure web pages. (Though to be fair I havn't been able to test this since the new version release as yet)

Thanks

 

FYI, I run NOD32 v3 on a number of SBS-based networks and find that it chokes client workstations at various times, but particularly at logon. I narrowed this down to NOD32's scanning of log files (particularly the %ProgramFiles%\Microsoft Windows Small Business Server\Clients\SBSClientApps.log file, which grows quite large over time).

Actually NOD32 v2 performs poorly when scanning .log files, but v3 is awful. Excluding *.log (as well as .edb and .tmp files) from real-time scanning cured most of our performance problems.

 

New to NOD32 and updating it and my question, I'm sure is very simple to answer.

Do I need to download this new version to upgrade from 3.0.551.0 to 3.0.667 or will my installed version automatically update itself?

Rey...

 

The program will NOT update itself. You need to download the new version.
The safest method is to first remove the current version from your computer
as directed here:
http://www.eset.com/support/kb.php?option=com_kb&Itemid=29&page=articles&articleid=93

 

Just to clarify this, an automatic program component update (PCU) will take place as soon as no problems are reported with a current installer. It wouldn't do any good if all users were updated automatically to a version which has certain problems. When we are sure the installers are ok and ready to be distributed to all users, we'll release a PCU. That will be announced here.

 

I have to say, that is a quite astonishing statement. How long ago was NOD32 v3 released? What you are saying is that after all these months, the quality of your product is still sufficiently poor that you are not ready to risk offering people automatic updates. So, effectively we are all still beta testing this product.

 

Hi!

Every program is developed long after release. Did you wait that everything will work without problems? Everyone has got different configuration of computer and one program has to be compatible with everyone. Developers still work on uncovering errors and new features.

Regards