Signature updates failing

For the last two days my updates have failed, using XP.

I am not aware of anything being changed, and my user name and password are OK.

Would welcome suggestions as to solving the problem.

Thanks.

 

The error message is ?

 

Sorry,

Virus signature database update failed

 

Hello!

Read this KB article (http://kb.eset.com/esetkb/index?pag...earch&viewlocale=en_US&searchid=1253025272367) and follow the instructions .

It should help you provided that your license is active

 

Hello aptisman,

I would also try this article:

http://kb.eset.com/esetkb/index?page=content&id=SOLN98

The part about clearing your update cache may help resolve the update issue that you are experiencing.

 

I've worked through all that, although I was not able to delete the emo files, and finally uninstalled and reinstalled, to no avail.

 

Your computer could be infected by malicious software that prevents NOD32 from updaing . There are many threats known to do that .

I'd suggest you make sure your computer is not infected . If you are unsure , please , post in a forum that provides malware cleaning services . There are numerous on the Net . You could try to register in AumHa

 

check your hosts file for blockage ? what kind of firewall do you use ? virus infiltration ? run malwarebytes..

 

Do you have a firewall installed that might be blocking communication for ekrn.exe?

 

Since he said he reinstalled and still has the same problem, your probably right.Or communication is being blocked by something somewhere else.


would it work to try and ping an eset update server from his computer ?

 

No, my firewall (LooknStop) was not blocking eset. I am free of malware, nothing reported by Spyware Terminator or Malwarebytes, so I guess it was a conflict somewhere.

Not having done so for some time I wiped the drive and reinstalled XP and everything else, and all is now fine.

My only remaining question, should NOD32 start early in the boot sequence, it seems to be one of the last?

 

NOD32 has two processes - ekrn.exe and egui.exe

ekrn.exe represents the ESET Service (the kernel) . It works as a service and it loads early in the boot process.

What you see as last is the egui.exe - it is the graphical user interface which starts with two parameters - hide and waitservice. The wait service means that it will wait for the other processes to load and then it will show and minimize in the systray.

The protection is performed by the kernel (ekrn.exe) . In v4 ESET Helper (a driver) helps removing active malware found by the kernel

 

False, the only thing from NOD32 that is " supposed " to load early is Eamon, the real time protection driver.

ekrn is started after the logon process.it's a type 272 which means it can interact with the desktop.if it was a system service it would be type 1, type 2 is a file system driver that binds with the file system, which is what Eamon is supposed to be, but the INF's are set up wrong and windows changes it to type 1.

 

I am sorry about the confusion , you are right about this.

I am aware it is not acting as system service , just wrote it like that while in a hurry.

Thank you for correcting my words

 

I have been experiencing thw same problem for the past 5 days. Eventually Nod 32 does get through and updates. When it fails it updates 1 of 2 and then fails.

Could it possibly be a problem with EST's servers? If not why is this problem not there all the time and why is more than one person experiencing the same problem?

Thanks

 

As an after thought I am located on the coast in CT. Is it possible we could both be using the same mirror for updates and only that mirror is experiencing problems?