Anyone else been having fun with ESET today?

Vertigo · 2 Sep 2010 at 21:11

Seems ESET pushed out a very b0rked update this afternoon. Took out several of my servers and most desktops. There's quite a bit of chat and anger about this on the support forums.

For anyone who's not yet realised or is fighting issues and doesn't realise it's ESET, it appears the 5417/5418 updates were badly broken. It's been fixed in 5419 but it might require a couple of reboots after this update is install for normality to return.

I'm rather less than impressed atm.

DRZ · 2 Sep 2010 at 21:17

I'm on holiday at the moment but we're an ESET partner and there was certainly stress in the office today from what I heard...

whitecrook · 2 Sep 2010 at 21:22

tfti.

we run eset but have't seen any issues - will check tommorrow.

CrimsonAvenger · 3 Sep 2010 at 09:47

Long thread over at Wilders. Doesn't seem anywhere near as bad as McAfee tbh. Couple of reboots in most cases. Not so good for servers but not really a problem with workstations.

janesssssy · 3 Sep 2010 at 11:01

Took down 18 of our customer servers... Ive taken a day off today

My colleuge NOT impressed!

janesssssy · 3 Sep 2010 at 11:15

My day off is now over

svbooga · 3 Sep 2010 at 11:25

Had issues yesterday with random lockups on a couple of workstations and a server, fixed with a reboot. I wondered if a nasty had got in somehow, looks like it might have been the AV

awaybreaktoday · 3 Sep 2010 at 12:04

This is why everyone should be using AVG, its the best out there..

PR. · 3 Sep 2010 at 13:05

Haha, was on my own yesterday, first the Job Management server killed itself and I spent most of the day reviving that, then ESET released a bunch of dodgy signature files that crashed half the desktop machines, fortunately the servers didn't have any issues. Great fun.

Luckily I had day off today!

whitecrook · 3 Sep 2010 at 18:01

yep a few issues, but had updated to the fixed issue just rebooted a couple of times and seems to have sorted.

Some of the client machines borked, pulled the av off and pushed it back out seems fine now.

Ev0 · 3 Sep 2010 at 18:39

Must have missed the problems on the few machines I have running with ESET, had a peek today (as I hardly ever check these machines) and they were all happily running 5419.

Westyfield2 · 3 Sep 2010 at 20:30

I run NOD32 at home, none of the machines had any issues.

Out of interest, would the problem prevent the machine from booting? Or was it just causing problems once booted?

PR. · 3 Sep 2010 at 23:32

From what I saw 5417 started picking up false positives so they released 5418 which just caused machines to grind to a halt and freeze up, once rebooted they would go slow/crash again until they updated to 5419.