Undocumented serious error (0x101a)

Discussion in 'ESET NOD32 Antivirus' started by Lithium, Dec 3, 2008.

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

    Lithium Registered Member

    Joined:
    May 22, 2008
    Posts:
    5
    Hi,

    I've noticed this morning that when NOD attempts to update the virus signatures after they download it just fails with the warning "Undocumented serious error (0x101a)". The last signatures to install correctly is 3657 (20081202). I'm running NOD 3.0.669.0 on WinXP Pro SP3 32bit. Any ideas? Thanks.

    Cheers,

    Lithium.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Just to make sure, does this problem persist even after a computer restart?
     
  3. jeremyf

    jeremyf Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    61
    I manage about 16 workstations with NOD32 Business Edition, and this error pops up at times on all of them, seemingly at random.

    Manually attempting to update produces the same error message, but the solution *IS* a reboot of the affected system, as Marcos suggests. I was wondering why this is happening at all? Is this a known bug or what?

    Thanks for any feedback...
     
  4. Lithium

    Lithium Registered Member

    Joined:
    May 22, 2008
    Posts:
    5
    Macros,

    Rebooting seems to have fixed this error from appearing.
     
  5. jeremyf

    jeremyf Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    61
    Can anyone provide any input as to why NOD32 needs to be rebooted to solve this issue every few days (maybe even a week)...

    Any wisdom would be appreciated...
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    The issue is still being investigated.
     
  7. BeanCounter

    BeanCounter Registered Member

    Joined:
    Apr 8, 2006
    Posts:
    66
    Location:
    Melbourne, Australia
    I get this problem occasionally. It happened on one of my PCs a day or so back. The only solution that I have found is to reboot the PC.
     
  8. edwin3333

    edwin3333 Registered Member

    Joined:
    Aug 29, 2007
    Posts:
    244
    Reboot resolves it. Sometimes I can't reboot for ~ a week until maintenance window, but that does solve it. Pattern files refuse to update until the reboot.
     
  9. nonoise

    nonoise Registered Member

    Joined:
    Jun 6, 2008
    Posts:
    322
    did u try to restart only the ekrn.exe process? it worked for me a few times in such case
     
  10. edwin3333

    edwin3333 Registered Member

    Joined:
    Aug 29, 2007
    Posts:
    244
    How do you do that? In services, the option to stop/restart it are not there and if I try to kill/pskill et al it says access denied.
     
  11. anotherjack

    anotherjack Registered Member

    Joined:
    Jun 13, 2003
    Posts:
    224
    Location:
    Louisiana
    Just FYI, I got it for the first time this morning on my test server running v3.0.669.0:

    Last db received - 3669
    Update module: 1024 (20080514)
    Antivirus and antispyware scanner module: 1164 (20081204)
    Advanced heuristics module: 1084 (20081202)
    Archive support module: 1085 (20081106)
    Cleaner module: 1036 (20081124)
    Anti-Stealth support module: 1002 (20080723)

    Reboot fixed it...
     
  12. dvking6

    dvking6 Registered Member

    Joined:
    Feb 27, 2009
    Posts:
    1
    Hi all! Nice to meet you all.

    Regarding the 0x101a error, I have the following conclusions.
    The cause of the problem could be:
    1. corrupted %TEMP% and %TMP%
    2. C:\Windows\TEMP disappeared
    3. NOD32 version is too old

    Cure to the problem:
    1. Download the latest installer from eset.com (Version 3.0.684) and reinstall
    2. Make sure that C:\Windows\TEMP exists. If disappeared, rebuild it.

    If the problem still persists after completing the above steps, please change the path of the TEMP and TMP variable as well (as the attached image).
     

    Attached Files:

    • TEMP.jpg
      TEMP.jpg
      File size:
      38.3 KB
      Views:
      1,565
Thread Status:
Not open for further replies.