Eset Virus Signature Database Update 5418 may cause issues

[leofelix]

Eset Virus Signature Database Update 5418 may cause issues

Eset Knowledgebase

Virus Signature Database Update 5418, released on September 2, 2010 at 6:00 AM PST may cause an “ekrn.exe” error. Other reported issues include ekrn crashing, systems not responding and threat notifications with blank name fields.

At 8:00 AM PST, Virus Signature Database update 5419 was released In most cases, restarting your computer and updating your ESET security product will resolve the issues you are experiencing.

If the issue persists after restarting and updating your ESET security product, then restart again. If you still experience issues after restarting twice, uninstall and reinstall your ESET security product.

Image courtesy ESET S.R.O

If you continue to receive this error or experience other issues related to this update, and you are currently running virus signature update 5419, download and run this utility: http://download.eset.com/special/eset_update_fix.exe on all workstations.

For customers running virus signature update 5417 or 5418, run the utility and then manually update workstations.

If you continue to experience problems after completing all steps above, contact ESET Customer Care.



Via Certifiedbug blog

[hellnoire]

Missed it thanks to my sleeping in! I knew it would save my ass one day!

[sujay]

Wow thanks for reporting leo...

[Neo]

imp info leo
i got similar error on shutdown before but dont know which av i had then

[leofelix]

this is a common error, usually a sort of mistery.

Click here to know why

@ hellnoire: My sister was also sleeping or I would be in a cold sweat:-)

[johnshaw1917]

Missed it thanks to my sleeping in! I knew it would save my ass one day!

Thats right, your still on vacation, aren't you!

@Leo Thanks for the info!

[INDRANIL]

Thank you leo for the information.

[Ceyfer √]

No such faulty update happened on our ESET business clients inside my dept. Good thing is during the update, all boxes were under regular maintenance.

What is ESET going to do to prevent a repeat of this situation?

• Moving forward, pre-release testing will include more complex ‘future update’ scenarios, as well as improved incremental compatibility testing.
• We will employ the use of our pre-release servers to a greater extent, subjecting updates to extensive testing with several update phases

This error is normal and really happens to any brand, so contingency plan is a must.

[hellnoire]

Thats right, your still on vacation, aren't you!

Today's my last day, I return home tomorrow.

@ hellnoire: My sister was also sleeping or I would be in a cold sweat:-)

Well, thankfully, sleep is a good thing, eh?