Windows 2000 computer crippled by 3435 update

Why would they tell you that the ones programming this were reading a manual at the time?

And yes the 3436 update resolves the problems we had thanks for that.

I dont understand why it is so important releasing new definitions several times / day.
That causes more deadlines and more stress for the programmers - meaning they will rush things..

Have a maximum of one / day and check your facts before releasing these things in the future.

Also a note: Every time you report an issue to see if others have got the same problems in the forum You get a quick reply from a reseller that everything is fine and never have been better. Yeah right what do you know!! Just keep on selling your stuff or go write some invoices keep away from technical issues.

I havent seen any great active response from the dev team they should be the one's here replying.

 

New viruses don't wait till the next day to propagate.

I realize that Eset obviously has some internal QC problems, but that can be fixed (if they'd hire the right people).

 

Simply...if they ignore (left without answer) problem for a long time then problem became forgotten or internal. In best case, you will receive generic answer.
There are many concrete questions on this forum without honest and concrete answer from moderators and developers.

cheers

 

Any idea if the below is related?

When 3435 was identified as a problem, my NOD32 console showed the server version as "unknown." A few minutes after it was posted on the boards here that 3436 was released, my console picked it up and distributed it. Apparently I got 3437 overnight as well. Now, this morning, my console again shows "unknown" for the signature version.

It seems rather odd that I would start having a console problem at the same time as the signature issue, especially as I got the 3436 update as soon as it came out.

Thoughts?

Thanks,
James

 

Still no official explanation from ESET? I would feel much better if they addressed the problem.

https://www.wilderssecurity.com/showthread.php?t=220228 isn't a good enough response for me, but oh, well.

 

VERY lame explanation there. Let's hope that was just a quick "go update your PCs" post, to be followed by something more appropriate.

 

I have 750 PC's Im using ERAS and ERAC 2.0.110 and i have two servers.... One stoping to update clients definitions at 3435 and the other at 3431 but the server says that has downloaded 3438 definitions...

What i have to do..? Well Marcos (Eset Moderator) or any Eset Moderator what you have to say..?? We need a SOLUTION please....

 

Sigh...I was back to an Unknown DB version. A manual Update brought me up to 3438. This is getting annoying. Some communication from ESET would be nice.

 

I hate to sound like a complete idiot but I just started using NOD32 and suggested my client switch to it. Oh well.

While waiting on a fix I actually rebooted into Safe Mode, disabled the two services and the GUI in haste on most of the machines. This morning most of my XP machines still had the NOD32 icon in the running task bar and had already updated itself. Not sure why or how.

The problem I'm having is that a few XP and all 2000/2000 Srvr's don't have access to ESET User Interface to update it and if I try to start the ESET service, the 3435 update immediately cripples the machine again. I have to go back and boot into safe mode, blah blah blah.

I'm not running a management console (not that many machines). How do i update ESET to >3435 without starting the service?

Thanks!

 

Well I hate to say it. but after years of using Eset for personal use and now business I'm officially pulling it off my systems. The man hour loss and the amount of downtime is just unacceptable.

Thanks.

 

Startup the service and restart the machine. ESET will update after the restart.

 

I'll give it another shot.

Thanks for the reply

 

Install over with freshly downloaded .msi for your systems?

Cheers