New version : ESET NOD32 Antivirus v4.0.437.0 released

[nanana1]

Find it here :

http://www.eset.com/download/registered_software.php

[subhum4n]

It still have the some problem with Vista SP2 RTM

[a_kerbouchard]

Dnt see any server fixes.

[bodean]

Originally Posted by subhum4n

It still have the some problem with Vista SP2 RTM

What a shame. And for a minute there I thought ESET was listening to it's customer base with this major issue. Guess not

[vulliw]

Originally Posted by subhum4n

It still have the some problem with Vista SP2 RTM

It still have the problem with Vista SP2

Unable to load image \SystemRoot\system32\DRIVERS\eamon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : eamon.sys ( eamon+51de )

Notting fix system x86

[racketeer66]

Is it the x86-version, Mates?

[nanana1]

x64 version here :

http://www.eset.com/download/home-64bit.php

[jimwillsher]

I must admit, I'm very surprised to not see the SP2 fixes included. SP2 is already RTM and it will probably reach the public in a matter of days (at a guess). People will install it, and if they have ESET they're going to get burned. Oh dear, not good ESET....

[hclarkjr]

i just upgraded, working fine so far. X64 version here

[hclarkjr]

Changes in NOD32 Antivirus 4.0.437:
* Fixed: Thunderbird plugin may corrupt email in some occasions + several minor fixes
* Minor fixes in ESET SysInspector
* Fixed: Problem with the creation of Rescue CD after reinstallation from ESET Smart Security 4 to ESET NOD32 Antivirus 4

funny no mention of the vista service pack 2 problems

[bodean]

[CivilTaz]

The sad part is that it seems Eset is trying to ignore this, at least they should mention that they are working to solve the problem.

[Marcos]

Originally Posted by CivilTaz

The sad part is that it seems Eset is trying to ignore this, at least they should mention that they are working to solve the problem.

Interesting. First you confirmed that the new version was working fine for you and now you complain?

[hclarkjr]

no, i tried it first with version 424 then today upgraded to the new version just released.

[hclarkjr]

Originally Posted by Marcos

Interesting. First you confirmed that the new version was working fine for you and now you complain?

read here http://www.wilderssecurity.com/showthread.php?t=241025

[CivilTaz]

Originally Posted by Marcos

Interesting. First you confirmed that the new version was working fine for you and now you complain?

I said, It seems to be working fine, you never responded after that, so i thought u were not interested anymore in the issue, it worked fine for a few hours, but after some reboots, the same problem.

I think you are not dealing with this in the right way, ignoring threads and only writing to trying to make me feel bad. But it's ok, no problem, I only hope u solve this before microsoft releases SP2 for Vista to windows update, because if you don't, so many resellers are gonna complain about this.

[hclarkjr]

it seems like ESET is not interested in addressing the issue. they have made no comments here or on their website concerning the issue.

[SmackyTheFrog]

Why would you put "we're working on SP2 compatibility" in release notes? New builds take time to go through testing before release, it is clear from moderator comments in other threads that the issues are being worked out, and SP2 hasn't even been released to public yet. Cool it and wait a few weeks.

[CivilTaz]

Originally Posted by hclarkjr

it seems like ESET is not interested in addressing the issue. they have made no comments here or on their website concerning the issue.

And as you can see, Marcos only commented here to complain about my complain.

[CivilTaz]

Originally Posted by SmackyTheFrog

Why would you put "we're working on SP2 compatibility" in release notes?

Maybe because so many people already have installed SP2, so they could know that the problem is with the Eset software, and not with their computers. They should mention that V4 doesn't work with SP2, so people don't get scared when Nod32 starts to fail.

[SmackyTheFrog]

Originally Posted by CivilTaz

Maybe because so many people already have installed SP2, so they could know that the problem is with the Eset software, and not with their computers. They should mention that V4 doesn't work with SP2, so people don't get scared when Nod32 starts to fail.

People have installed SP2 with Nod32 present and have not seen problems, so the issues are isolated and not universal. The lag time between RTM and a public release is to address issues exactly like this one and if you are actively searching out installers for SP2 ahead of the public release, you should expect issues like this to pop up.

[CivilTaz]

Originally Posted by SmackyTheFrog

People have installed SP2 with Nod32 present and have not seen problems, so the issues are isolated and not universal.

I haven't seen any PC with Vista SP2 and Nod32 V4 working well, anyway, V2 and V3 work great.

[siljaline]

Thanks ESET

[Elisa Tese Rotca]

As someone says before, Vista SP2 is RTM.

And the RTM versions are (IMHO) still like a Beta, with bugs and more. So i thing is too soon to says "why do not fix this error".

Is not the final Vista, don't expect perfection. In a GA Vista SP2, say whatever you find.

calm down boys

[hclarkjr]

yes, it is final. RTM mean released to manufactures, that means they have sent it to people like dell and such. plus it has been posted on technet and MSDN as final.