AV Definition update caused error

Blocked eset domains in DNS/firewall. This might work.

It's crazy, does ESET actually test their updates?

 

Has anyone compiled a list of OS's which the issue appears on? I have users calling in about their computers freezing (XP SP3) and I'm not sure if it's just their desktops that have the issue, or if servers are effected as well. Mix of 2003 & 2008 servers.

 

5418 caused us a huge amount of problems. Machines locking up all over the place. 5419 doesn't seem to be much better. I've got servers going down all over the place.

Nightmare.

 

Same here. ESET has basically brought down my network.

 

Working fine here after 5419...

 

Only our terminal server really suffered at 5418, though performance may have been a problem on File and Exchange, however 5419 has definately knackered them all, a hard reboot is the only option... and praying to almighty they come back up again.

Just darn workstations to sort out now...

PS. anyone getting "AUTHORIZATION_FAILED" in their ERA ?

 

Fortunately one of our servers has survived - the other 2003 server not so lucky.

As for our XP SP3 workstations, the ones that already had 5417 on needed a reboot after both 5418 and 5419 but once rebooted after 5419 everything seems fine.

I think this is running as :

5417 had the bug
5418 triggered the bug
5419 triggered the bug but fixed after reboot

cheers

Darren

 

Affected operating systems in our network server 2003, windows xp through to windows 7.

 

Same Here
Windows 2000 Server
Windows 2003 Server
Windows 2000 Pro
Windows XP Pro SP3

 

Server 2003 R2
XP SP3
Vista and Win7 seem fine.

 

Sorry Im Bad, you are correct

 

we have 000s of pcs and servers affected by this, Eset seem to have 5419 out now but sorting the servers is a real pain and some PCs will not restart
Have taken phone off hook, could be a late finish tonight
Thanks Eset

 

It's now just taken down our mail and file servers. Joy!

 

Seems that a second reboot is required for servers that have the 5419 update. So far all servers that I have rebooted twice seem to be OK.

 

XP 32bit & 64bit
Server 2003

has ruined my afternoon, 100's of machines down - this is seriously unimpressive

 

Update 5419 and a reboot (sometimes two) has resolved most of our issues. I still have a few problematic workstations, I'm holding off for 5420 before I send out another request for users to restart their machines.

 

I'm starting to wonder about that based on the past couple of years...this update REALLY hurt. 2 of us here remoting into clients networks all over the country...ensuring the RAS/RAC mirrors are updated, and important servers. And on a few servers already, I've had to restore databases from system lockups that corrupted them, from the bad definition files.

Great way to spend my day volunteering this repair work instead of out there making money.

 

Reparations ESET! This is bad. I've spent all morning on 35 servers and 300+ workstations having problems. Wow. Not happy.

 

Leaving for 5 mins seems to cure the problem of freezing on 5419 on one XP SP3 machine I have seen. Rebooting our seats as a precaution.

 

This is a joke. I've had to reboot two servers and 80% of my workstations so far. I'm on holiday in 25 minutes and have no confidence in ESET or whether the servers are going to need further reboots tomorrow when I'm NOT HERE!

I'm seriously unhappy right now!

 

For the complainers.

We all know this sucks, but unless you just started in IS/IT today, you should realize this stuff happens. If technology worked flawlessly, YOU WOULD NOT HAVE A JOB. So, roll up your sleeves and do some work instead of crying like a child with a skinned knee.

 

/Claps... well said

 

XP SP3 32bit here...

When I got 5418 I jammed up hard, couldn't even get Task Manager, had to reboot and I was fine. That's when I came here and learned about the problems.

Since my update was about 2hrs old and ESET saying they were working on it, I forced an update and 5419 came in, same problem, hard jam, had to reboot. Of course after the reboot everything works fine.

My Win7 desktop has been sitting idle, running 5415, I won't be forcing an update, I'll let it happen naturally.

 

Just called ESET and the official line is to reboot twice. Apparently it should hang updating from 5417 to 5418 (reboot), then from 5418 to 5419 (reboot).

That's not what we're seeing though. We still have multiple systems hanging even on 5419 after 2 reboots.

 

Indeed. This is what we do, y'all.