update failing at 4833

Discussion in 'ESET NOD32 Antivirus' started by Computer Answers, Feb 5, 2010.

Thread Status:
Not open for further replies.
  1. Computer Answers

    Computer Answers Registered Member

    Joined:
    Jun 16, 2003
    Posts:
    19
    My server (Win 2003) at work will not upadate past v4832. At home I'm up to 4839 with no problems so I assume it is not an eset issue. I have re-entered the password and we don't use a proxy so there are no problems there. The update process runs and at the end I get the message "virus signature database could not be updated. undocumented serious error (0x101a)."
    Any ideas?
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Is EAV on the computer in question installed in C:\Program Files\ESET\"? Some localized versions of Windows have that folder name localized as well. Even though it shouldn't cause problems, one never knows.

    Can you confirm or deny that the problem persist after a system restart?
     
  3. Computer Answers

    Computer Answers Registered Member

    Joined:
    Jun 16, 2003
    Posts:
    19
    Thanks for the reply Marcos. The installation is in c:/program files/eset/eset smart security and I doubt that would be a problem. Updates have been working fine up until 3 days ago. I will try a restart in a couple of hours when the network is quiet.
     
  4. dannyboy

    dannyboy Registered Member

    Joined:
    Jul 21, 2005
    Posts:
    113
    Location:
    UK
    I had this on one of my machines, I had to boot into safe mode and delete all the em*.dat files in the Eset program folder, then boot back into normal mode and run an update.
     
  5. Computer Answers

    Computer Answers Registered Member

    Joined:
    Jun 16, 2003
    Posts:
    19
    A restart fixed the problem. Thanks for the assistance.
     
  6. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    I see that the problem seems to have been solved, however, the ESET solution for Error 0x101a is here.
     
Thread Status:
Not open for further replies.