Communication with ESET NOD32 Antvirus kernel failed!

[Gregor]

Hi,

I just upgraded to NOD32 v3.0 and when selecting a larger number of files (usually 10 or more) within Windows Explorer and then selecting the NOD32 context menu on-demand scan, I sometimes get the following window popping up preventing the scan from running:

Titel of window: ESET NOD32 Antivirus - Shell Extension Error
Message within window: Communication with ESET NOD32 Antvirus kernel failed!
Button: OK

Clicking OK does nothing except for closing the window. No scan is being performed. The strange thing is that it doesn't happen all the time, just sometimes with certain files.

What could cause the problem? Has anyone else experienced this?

[Bubba]

Hello Gregor,

While I have not run across a thread where an Eset rep has commented about this error message, the below thread has a user comment and their suspected and\or factual reason for the message.

This thread---> what the ? "Communication with ESET NOD32 Antivirus kernel failed!" (http://www.wilderssecurity.com/showthread.php?t=195424)

Bubba

[Banger696]

I just tried this with V.621 and scanned the ESET files, 412 of them in 4 seconds with no crash on XP SP2. Strange. Are you running the latest version?

[Gregor]

{QUOTE-> Hello Gregor,

While I have not run across a thread where an Eset rep has commented about this error message, the below thread has a user comment and their suspected and\or factual reason for the message.

This thread---> what the ? "Communication with ESET NOD32 Antivirus kernel failed!" (http://www.wilderssecurity.com/showthread.php?t=195424)
<-QUOTE}

Thanks for the hint. Exactly what I am experiencing.

[Gregor]

{QUOTE-> I just tried this with V.621 and scanned the ESET files, 412 of them in 4 seconds with no crash on XP SP2. Strange. Are you running the latest version? <-QUOTE}

Yes, I am running the latest version. Maybe the depth of the path matters as pointed out in the other thread.

[Banger696]

{QUOTE-> Yes, I am running the latest version. Maybe the depth of the path matters as pointed out in the other thread. <-QUOTE}

Ok I've retried with a very deep path and can't repeat this error. Maybe an uninstall and fresh download/install is in order? That's how I upgraded from the previous build.

[Gregor]

For now, I went back to NOD32 v2.7 where I don't have this error. I will try again in a couple of weeks with a fresh install. Maybe it will work then.