AV Definition update caused error

5419 appears to be out now, any official word?

 

After restart mine are working again.

 

having same problems with 5418 defs. phone ringing off hook with error messages popping up....................

 

Ditto here...

This is really bad... so far rebooting seems to work, but its only been about half an hour since I rebooted the first one, so it may happen again...

I agree that ESET should have a simple way to roll back to a previous state whenever something like this happens...

 

Same here. Practically all machines lock up after 5418 update (windows xp sp3). After reboot, things run ok, for now.

 

They just pushed 5419...trying it now. 120 seats of unhappy users here.

 

5419 on its way here too... will keep you posted.

 

just got the 5419 defs, does anyone know if this is the fix, or should i unplug the ethernet cable to the eset admin server now before it makes things worse?

 

Updated to 5419. Had to restart my computer. Seems stable for now.
Windows XP PRO/SP3.

 

5419 has been released

 

Just got this back from support:

Thank you for contacting ESET Customer Care. Yes, we are aware of this issue and we are currently investigating it. The issue is related to update v5417.

If possible, please restart the affected machines, this should solve the problem.

As soon as there is any update, we will contact you again.

We apologize for the inconveniences.

Thank you,
ESET Customer Care

 

We've got 250 seats and one by one they are locking up. If we manually reboot shortly after the update then everything seems fine.

 

We were seeing the same behavior on 5418. 5419 came out so we immediately pushed it out to folks, now we're having the same issue all over again....avoid 5419

 

Saw this posted by Marcos earlier but can't find it anymore: (maybe its still broken?)

Hello,
after update to v. 5418, you might have encountered a problem with any of the following symptoms:
- ekrn crashed
- system stopped responding
- administrators might have received threat notifications with a blank threat name field

The problem was discovered in update 5417 and exhibited after an update to a newer version. To protect our users, we stopped the update as soon as the problems were reported to us.

A newer update 5419, which fixes the problems, has just been released. Note that ekrn may crash once more during update to the latest version due to the problem present in the previous versions 5417/5418.

SOLUTION FOR USERS:
Update to v. 5419 and restart the computer. Ekrn.exe will start and function properly then.

SOLUTION FOR SERVER SYSTEMS:
Update to v. 5419 and run "net start ekrn" to start ekrn.exe after a crash.

 

Still experiencing the same thing with 4719, as with 4718 update.

 

I just received 5419 and got the same type of memory reference error right after it was installed. Have just now rebooted an am sitting with my fingers crossed for this not to happen again.

 

This error is caused by Def Update 5418

Think Eset need to get there act together, as I have about 7 servers which need rebooting.

 

Yadnom,

I saw the same thing and can't find it either. Must still be an issue.

 

For Business users this is a joke

 

Got at least 10 servers that need rebooting and about 100 clients. At least...

Got a lot of customers that are not to happy. 5419 doesn't fix it. I updated and started all over again..

 

5419 is doing the same thing. This is absolutely unacceptable!

Is there a quick fix to disable auto-updates?

 

I have stopped the update server for now and will re-enable when eset get thier act together.

Does anyone know if any of my clients are still on 5417 and are rebooted will they still crash when I enable the updates again?

 

I'm lucky - my public computers are running disk protection software. I killed the ERA box they check into so they will run an old update after a reboot and can't download the new one. All of my staff computers and servers on the other hand...

 

Going the same way as Mcafee's problem update afew months ago

 

Seeing the same problems with 5419 update not completeing also trying to reboot our seats. WTG Eset. Quality procedures didnt work this time.