A too frequent error message !!!

Discussion in 'ESET NOD32 Antivirus' started by Philippe_FR22, Mar 11, 2009.

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

    Philippe_FR22 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    249
    Hello,
    Since release 3, I noticed when virus database just updated the following message (in french).

    In english, that means :
    During kernel execution on computer "name of the computer", following warning occured : virus analyser initialisation failed. Antivirus protection will not run correctly...


    Well, now it's time to think about future...

    I have to renew my ESET licence during september... If I analyse ESET behaviour since release 2.7 :

    -> Release 2.7 : very good, never had any problems
    -> Release 3 : too many problems like this one, my pc was too often "not protected" due to virus database update that caused KERNEL initialization failed
    -> Release 4 : interesting release but same problems as release 3. Too often, I have same messages due to threat sense release corrupted or something like that !!!

    This is a major security hole !


    So this is a message to eset team : if i encounter one more time such a problem due to corrupted virus database that causes kernel initialization failed, this will be my last eset experience...

    Despite I love eset concept, ergonomy and design, I will have to take the good (best) decision based on "security"....


    Regards:thumbd:
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Why don't you contact customer care? This message would also occur if you have insufficient free RAM so that the resident protection driver could not load and you were alerted about this by email, too.
     
  3. Philippe_FR22

    Philippe_FR22 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    249
    Hello Marcos,

    This problem is not due to lack of RAM. My PC are both on XP with 1GB RAM and very few applications launched at startup... This occure generaly just after having received virus sig udpdate... Engine have to reinitialize and fail the job (some times)...

    Regards
     
  4. Philippe_FR22

    Philippe_FR22 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    249
    Hello,

    In fact, I'm continuing thinking about this kind of error...
    After analysing this particular PC behaviour, I noticed that sometimes, when this error occure (and when I'm not behind the PC to force update cache to be renew), after an undetermined delay (several minutes), virus analyser engine could, although, start successfully... I suppose that there are several retry...

    What I'm sure is that is not a memory problem (memory size is 1GB and few applications are loaded)...

    What is under investigation is timeout expiracy.... I explain myself : this PC is a old vintage AMD Athlon 800 over a KT7 motherboard. Even if windows XP is perfectly installed and functionnal, even if the PC is quite conforable, it could be possible that updating virus database/reloading virus scanner engine take too long time and causes timer expiracy... May be some more informations from eset support could be appreciated for analyse this point....


    Regards
     
Thread Status:
Not open for further replies.