Eset5 and windows7 sleep/wake

I ran the below questions by eset support and got the helpful response of "contact the computer manufacturer". I'm hoping to get more from the forums here; in the least is anyone else seeing this so I know that I'm not alone?

I run a nightly scan against my entire collection of hard drives a few times a week (this is windows7 64 bit w/ eset v5). There's some functionality which looks either missing or I'm not setting it up properly.

1) There's no way to "wake" the computer via the built in scheduler. So I have to schedule something else (another program/job) to wake up the computer just to run my nightly scan. That doesn't seem right... I've seen this issue posted on the forums under prior editions of eset and am wondering if there's anything new in v5 that I can use?

2) More often than not it looks like the scan is not preventing the computer from going to sleep. So looking at the log it shows that it does a bunch of work, but doesn't show any indication of pausing or going to sleep. Then when I wake the computer the next day it resumes the scan from last night. So the total time in the computer scan log shows 22 hours or something crazy, but in reality it's only a few hours of scanning with computer sleep time added in. I guess my question here is how do I stop the computer from going to sleep while the scan is running. Why does window think it's idle while a major scan is going on? Is anyone else seeing this?!?!

 

Back in the XP days, your system would stop itself from going to sleep if there was a certain level of disk or cpu activity going on. That appears to be replaced on Vista/Win7 with individual applications making API calls to the OS to stay up even if it has exceeded it's idle window before sleeping. I agree that the ability to wake from sleep to perform a scheduled task along with the option to keep the system awake during a scheduled scan would be useful features for a situation like this.

Since that isn't possible for you at the moment, this script should do the job you are describing.

Code:

powercfg /x -standby-timeout-ac 0

cd "%programfiles%\ESET\ESET NOD32 Antivirus"

ecls /auto

powercfg /x -standby-timeout-ac [old value]

rundll32 powrprof.dll,SetSuspendState

Then throw that in to a scheduled task that runs under the system account with the schedule you want and set it to wake the system from sleep to execute.

 

Elegant. Thanks Smacky.
However it looks like command line Eset /auto doesn't automatically take all the settings of my Eset profile; things like ignore certain files, only look at certain folders, nor does it even log the scan in the eset logger.

I think I'll use your idea of a wake up batch file that resets the standby timeout to 0, then have the eset scheduler kick in and run the normal profile, and have a later batch file come in to clean up the standby timers.

Yeesh, what a wonky work around. I'm going to give Eset the benefit of the doubt and assume for them to put this functionality into their product is very hard and that's why they haven't done it yet.