Undocumented serious error

Discussion in 'ESET NOD32 Antivirus' started by BeanCounter, Apr 23, 2008.

Thread Status:
Not open for further replies.
  1. BeanCounter

    BeanCounter Registered Member

    Joined:
    Apr 8, 2006
    Posts:
    66
    Location:
    Melbourne, Australia
    Version 3.0.650 failed with an "Undocumented serious error (0x%04x) in Update. After I rebooted the PC, the update worked OK and everything returned to normal. The PC is running XP SP2 with Office 2007.

    I have 3.0.650 installed on two other PCs and they have not exhibited this problem.
     
  2. marcuri

    marcuri Registered Member

    Joined:
    May 12, 2005
    Posts:
    14
    I'm experiencing this same issue, however its on build 642.

    Windows XP SP3.. yea the RTM... not RC2.

    Going to upgrade to build 650 and if that doesn't work restart.
     
  3. marcuri

    marcuri Registered Member

    Joined:
    May 12, 2005
    Posts:
    14
    Upgrading to build 650 fixed it.

    For future reference, this works well with sp3.. both 642 and 650. I hadn't had the problem with 642 until a good 18 hours with sp3.
     
  4. BeanCounter

    BeanCounter Registered Member

    Joined:
    Apr 8, 2006
    Posts:
    66
    Location:
    Melbourne, Australia
    I just had this problem again on one of my computers running 3.0.669. Update failed until I rebooted the PC. The other computers running 669 have not exhibited this failure.
     
  5. Capp

    Capp Registered Member

    Joined:
    Oct 16, 2004
    Posts:
    2,125
    Location:
    United States
    Ran into this problem myself.

    Try deleting everyting in your temp folders and rebooting. That is what I did and haven't had the problem since.

    hth
     
  6. BeanCounter

    BeanCounter Registered Member

    Joined:
    Apr 8, 2006
    Posts:
    66
    Location:
    Melbourne, Australia
    Each time it has happened, I merely restarted the affected PC and it hasn't yet happened again on either PC. It is a bit of a concern that the update process was inhibited until the reboot.
     
  7. BeanCounter

    BeanCounter Registered Member

    Joined:
    Apr 8, 2006
    Posts:
    66
    Location:
    Melbourne, Australia
    OK. This happened again on one of my computers. The workaround is to reboot. Does anyone at ESET have any idea about the cause of this problem?
     
Thread Status:
Not open for further replies.