kernel communication error

Discussion in 'ESET NOD32 Antivirus' started by howardg, Apr 4, 2009.

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

    howardg Registered Member

    Joined:
    Oct 13, 2008
    Posts:
    6
    Today, I turned on the computer (Vista Home Premium 64-bit) and for the first time since I've been using ESET NOD32 (about 8 months) the Vista boot up process stalls at the ESET splash screen for about 3-5 minutes and then gives the error: "ESET NOD32 Antivirus: Error communicating with kernel." Thereafter the whole system is very unstable, and the network window shows completely blank -- I have no LAN access. I managed to revert to an earlier disk image of two days earlier (using Acronis True Image) and everything seems to be back to normal. What caused this glitch? How do I prevent it from happening again? I have read the other posts and they don't shed any light for me. Thanks.

    Howard
     
  2. pain4gain

    pain4gain Registered Member

    Joined:
    Feb 8, 2007
    Posts:
    54
    When I come across that issue an uninstall then reinstall will almost always fix it.

    No idea what causes it though.
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    For some reason, the kernel service is not running. Does reinstalling EAV help?
     
  4. howardg

    howardg Registered Member

    Joined:
    Oct 13, 2008
    Posts:
    6
    What is the kernel process? I just checked process explorer and the only thing I could see from ESET was the "egui" process, even though ESET AV is running fine at the moment.
     
  5. howardg

    howardg Registered Member

    Joined:
    Oct 13, 2008
    Posts:
    6
    I just checked services.msc and found ESET Service, set to automatic, and ESET HTTP Server, set to manual. Is this the way it is supposed to be?
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Yes. Is ESET Service started? If not, are you able to start it manually?
     
  7. howardg

    howardg Registered Member

    Joined:
    Oct 13, 2008
    Posts:
    6
    yes, the eset service is started
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Once the ESET service is started, you should be able to run the GUI (egui.exe) fine.
     
  9. SanDiegan11

    SanDiegan11 Registered Member

    Joined:
    Apr 22, 2009
    Posts:
    9
    My NOD 4.0 was downloaded and installed about 5 hours ago. The situation is exactly the same as described by howardg's original post. Except the eset service is not started.

    Attempt to uninstall 4.0 (as suggested in some posts to uninstall and reinstall) failed too. NOD32 complained ESET's My Profile need sufficient access to delete the key, whatever that means. (All applications shown in systrays had been closed already.)

    I wonder whether I should try to see a restoring point is available to go back to the 3.0

    Checked services.msc and found ESET Service, set to automatic, and ESET HTTP Server, set to manual.

    Any suggestions?
     
Thread Status:
Not open for further replies.