sp2/nod32 4

[Larry D]

Seems to be a problem!


Warning: don’t use any ESET NOD32 V4.x Antivirus product together with Windows Vista SP2 or Windows Server 2008 SP2 « Smokey’s Security Weblog

 

[wwoods]

Seems to be a problem!


Warning: don’t use any ESET NOD32 V4.x Antivirus product together with Windows Vista SP2 or Windows Server 2008 SP2 « Smokey’s Security Weblog

Hmmm I use nod32 V4 and applied SP2 when it came out and havent had one issue

 

[Larry D]

Have a read here.

ESET Knowledgebase - Why does the icon turn red after installing Service Pack 2 for Microsoft Windows Vista and Windows Server 2008? (4.0)

 

[wwoods]

Have a read here.

ESET Knowledgebase - Why does the icon turn red after installing Service Pack 2 for Microsoft Windows Vista and Windows Server 2008? (4.0)

Read it and this "If you are running version 4.0 of either ESET Smart Security or ESET NOD32 Antivirus and have installed the latest update for Microsoft Windows Vista and Windows Server 2008, which includes Service Pack 2, you may be experiencing issues with your ESET security product."

It says MAY be.....as I stated above, I am not having issues, neither is my wife on her system, both Nod32 and SP2. Not saying its not a problem, just saying I am not having those issues

 

[Larry D]

wwoods, Yea sounds like only a few are having trouble. On my laptop sp2 failed and i am wondering if nod32 4 has anything to do with it?

 

[rive0108]

A few times at restart the AV didnt turn on (red icon), just restarted Windows, and is normal. its a glitch, that will shortly be fixed i suspect.

I have a green icon for "real time file protection" now. The problem only occured twice, and was easiliy resolved with a reboot.

 

[rive0108]

wwoods, Yea sounds like only a few are having trouble. On my laptop sp2 failed and i am wondering if nod32 4 has anything to do with it?

Doubt it. I just installed SP2 on three networked machines all running NOD32. Most likely an incompatable hardware issue.

 

[dinesh]

Something that may help:
I am currently running build (4.0.314), a new build was released may 20th, 2009 (build 4.0.437). Suggest all of you with build 314 update your version to 437 here:
Download Purchased Home NOD32 or Smart Security for 64bit systems

Hi Chris, i m still on build 4.0.314. I updated NOD 32 and the current database version is 4106. How can i get build 4.0.437?

 

[rive0108]

Hi Chris, i m still on build 4.0.314. I updated NOD 32 and the current database version is 4106. How can i get build 4.0.437?

Pick your flavor:

ps- database version is not the build version. The build most be downloaded, and cannot be "upgraded" from another build.

Download Purchased Home NOD32 or Smart Security for 64bit systems
Download Your Purchased Home NOD32 or Smart Security (32-bit)

 

[dinesh]

Thanks mate.

 

[rive0108]

Ill tell you something that weird about all this, This issue is not affecting all NOD32 4 systems with SP2. Aparrently some are having Kernel module interface issues when the computer starts- but apparently not many. Eset had difficulty diagnosing the issue, or reproducing the module startup error as a result because of this Irregular/inconsistant occuring error.

When I installed SP2 I didnt disable or remove NOD32 4 from my PC, And I suspect this caused corruption of the app. It is known that NOD32 causes issues with the SP2 installation. I reinstalled the newest build (without manually uninstalling the old one), and I havent had a reoccurance of the disablement issue.
So I just wonder If the manifestation of the error has some sort of trigger. I read one thread, that talked about the OP having difficultly removing the program because of Permissions issues, and had to boot into safe mode to edit the registry. Sounds like Windows/User corruption issues to me. I simply reinstalled the new build over the old one, then ran sfc /scannow-perhaps that made the difference.

In the end, All I know is that I reinstalled the build, and the problem talked about in the Eset kb, and Wilder Forums no longer seems to be an issue for me.