Task Scheduler bug 4.0.424 - Scheduled Scan

I just submitted this to support, but has anyone else noticed this?

I have a weekly scan on all our clients (1700) to do a full system scan at 4am every Tuesday. If the task is not completed, they will scan ASAP.

My own system scanned this morning, and completed.. I rebooted when I came in, and sure enough.. full system scan task started up...:

* Time of completion: 4:40:08 AM Total scanning time: 2379 sec (00:39:39)

* Time of completion: 10:18:47 AM Total scanning time: 2723 sec (00:45:23)

 

Just rebooted -- did another scan (aborted it this time tho).

* Time of completion: 10:37:38 AM Total scanning time: 808 sec (00:13:2

I'm going to have to turn off this task now for all our clients, ugh.

 

Yes, it is a known defect. Support will not fix it, just tells me not to do that.

Set your scans to "Not run if scan is missed" and it will not repeat the scan. Of course, if the PC is powered off at the scheduled time it will never scan.

 

How much more rubbish can one take from ESET? I am beginning to think that I made a serious mistake purchasing NOD32 for our servers. I haven't chimed in lately but let me just say, I am annoyed over the number of major problems with NOD32 v4. I expect some bugs in newly released software, but really, ESET should have beta tested this a little longer before letting it out the door. The drive to get this *wonderful* piece of work onto the market was greater than the work put into ensuring it performed *reasonably* well. Live and learn, I guess. If problems such as the many that are already well documented and reported are not addressed soon I am dumping NOD32 right into the rubbish bin. This is in spite of the 2 year license I already paid for. It simply isn't worth the headaches any more. My question is "How many times do you have to reinstall the software before it works?".

P_Head

 

An after thought to my previous post. Has anyone ever requested and gotten a refund for any ESET products?

P_Head

 

I just heard back from them, after they suggested adding the option to 'not run the task immediately if the time since its last execution exceeds specified interval'.. which didn't work:

An ESET Customer Care Representative has updated this case with the following information:

Hello,

I was able to replicate this behavior and have to agree with you. I have reported it to our developers and it will be addressed in a future version of our software.

Thank you for bringing it to our attention.

ESET Technical Support

 

Hi Pecker Head,

Refunds must occur within 30 days of purchase. I tried getting a refund from a non-paying client and was SOL

Overall ESET 3.0 or higher on servers is not recommend, I have had far too many headaches and 2.7 is the thinnest and leanest AV on the market and may I say tried tested and true on the server environment. 4.0 is TOO FRESH off the shelves in my opinion for servers albeit better than 3.0 was at first.

The first build of 4.0 gave Vista systems a Black Screen of Death. While I do like the return on the File Monitoring in 4.0 and have have installed it cleanly on a couple of servers myself without issue.

At the first sign of trouble I always found myself downgrading (especially true with 3.0). Another point to make is that upgrades don't fare so nicely, always do a complete removal of the previous version before upgrading to the latest build. I wish ESET would allow me to specify via configuration editor that I don't want an AMBER ALERT for all my 4.0 clients if I dont have the latest updates installed.

Overall I still find ESET the best and have tried other alternatives which are a lot thicker and complex to manage. Stick with 2.7!