AV Definition update caused error

Hi Marcos,

May I ask a question about this part:

Just only to avoid confusion about the word "pre-release":

1.
Is ESET here talking about testing a defs update at their end before releasing it into the public (pre-releasing)?
2.
Or has it also to do about the setting on a person's computer to enable pre-release updates (in Advanced setup - Update - advanced update setup - Setup - Update mode - Enable pre-release updates)?


Thanks in advance !

 

after update and restart on server now i get "can not communicate with kernel" and nod shut down? 5425 update

 

Have you already run this fix? It was made to fix the 5417 issue without a computer restart.

 

yes i have... Now i have restarted server AGAIN ,good for now, but it happen after few minutes. will see.

 

Then it must be a completely different issue not connected to the problematic update. Does uninstalling and reinstalling EAV help? Does the problem occur randomly or you can reproduce it an any time?

 

seems that you were wright.... It was an different issue. restart solve it. thx

 

I have a low tolerance for snafus such as this. I consider this as strike one in a two-pitch ballgame.

I realize all AVs have false positive detections, some of them critical. (I recall the AVG fiasco). But Micosoft Security Essentials is looking awfully good these days.

AFAIK, NOD32 has never detected anything other than the rare FP. Increasingly, I ask my self why I pay for this program.

 

We are still dealing with fallout from this at the hospital I am the network administrator for. I will send my detailed official response directly to Eset. For the forum, suffice it to say that at our facility this has been damaging both to myself and Eset.

 

Ok, Let me start by saying I read through most of this thread but it is just to long to read the whole thing.

I have one server that had this issue and this server cannot be rebooted.

I ran 'net start ekrn' and it comes back saying -
The requested service has already been started'

How can I restart the service??

I know a reboot would fix the problem but I know there is still an issue because the Nod interface is missing menus such as 'update' and 'computer scan'

I am running 4.2.40.0

 

Run this fix tool that will fix issues stemming from the problematic update 5417.

 

I ran the eset_update_fix.exe on that server and it did not seem to change anything. There are still menus missing from the AV client interface.

 

Then there's no chance it's related to the 5417 update issue. Is the eicar test file actually detected and blocked? At any rate, I'd suggest uninstalling and reinstalling EAV as soon as possible the next time you perform maintenance.

 

No chance This is the same behavior that I had on every single PC and server at two of the companies that I administer on that day.

I will not be going with NOD32 when licensing is up I can tell you that. It has been nothing but a pain in the ***. I am sure alot of people are with me on this one. I have never had such a disruption of PC's freezing up as that which happened on this day. Not to mention the issues I have had with your product on my servers.

Did anyone even test this before it was pushed out? I think not.

Uninstall and reinstall seems to be your only solution ever.

******************
I did have a chance to reboot the server in question this morning and that did resolve the issue.

 

Have ESET come out with an official response on how they will avoid this from happening ever again?
And is there any changes ESET RAC adminitrator can do to avert this and have feature like 'virus defenition rollback' introduced.