2.000.9 doesn't fix mine

Still get message that system (XP Home) has recovered from serious error on boot. Error reporting still points finger at NOD32. I have applied the fix by the book and update now reports I am up to date:

NOD32 Antivirus System information
Virus signature database version:   1.585 (20031222)
Dated:   22 December 2003
Virus signature database build:   4120

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Internet filter version:   1.001 (20031104)
Internet filter build:   1012
Archive support module version:   1.008 (20031127)
Archive support module build version:   1078

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version:   2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version:   2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version:   2.000.9

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   512 MB
Processor:   Intel(R) Pentium(R) 4 CPU 1.80GHz (1799 MHz)

 

ESET is currently testing the new build.

 

Is it usual to have MS error reporting refer to a fix that is still being tested?

 

Eset are working on the problem, I have multiple machines with the EXACT same error message, and looping reboot, even though you have chose "Shut Down" and not reboot.

Be patient, they are working on a fix. The problem is out of 1000 PC's all EXACTLY the same: XP SP1 all up-to-date, you may only have 30 or so that are affected this way, and why they are affected is being looked in to.

Rest assured, they are working on a fix

Cheers

 

Let me ask rheumatoid's question again:

Why post an update that MS error reporting points to if the "fix" is still under testing?

Nowhere does the fix info say it's a "test fix", it says it's a "fix". Yet, users here keep saying it's being worked on.

If it's not a fix, take it down.

 

NewNod I believe it is a fix for some and not for the other XP users. That is why Eset is still working on it.


But like was posted be patient they are working on it.


Randy

I do not know this for a fact, but IMHO MS and Eset are trying to work this out even though for some reason it only affects a few XP machines and not all of them. The fix as it is called is a fix that only worked for some machines and not others. So now it is back to the board trying to find out what went wrong and sometimes this can take a little time and with Christmas here it may take a little longer than usual.
Believe me I know how you feel when things on your computer is not working right.
So Patience is a must.

Take care and Enjoy your Christmas.


Give Eset a chance to make changes and test the fix before releasing.

 

Hi all,

>Still get message that system (XP Home) has recovered from serious error on boot. Error reporting still points finger at NOD32. I have applied the fix by the book and update now reports I am up to date

If you have this problem and having the following data in the NOD System Information (NOD32 Control Center> NOD32 System Tools> Infromation):

----

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.000.9

----

Pls. cotact your local Eset support site at:

http://www.nod32.com/support/support.htm

They have a fix available that should help you.

Thanks and have a very happy New Year!

jan