Change priority of avast! scheduled scan?

Hi,

Is there any way to raise the priority of an avast! scheduled scan? (I’d like to configure my shutdown software to shutdown the computer on idle cpu, after a scheduled avast scan, but currently there doesn’t seem to be much difference between when its scanning and when its not, so hard for the shutdown software to shutdown the comp on idle).

Hope that makes sense, thanks!

If you’re scheduling with the avast Pro version, on the arquive menu there is an option to shutdown the computer after scanning.

Sorry, what do you mean by the “arquive menu”? Do you mean the “Shutdown computer after scan” option under the “File” menu in Enhanced Mode? I find that I can only select that option while the scan is on-going, and not before a scheduled scan.

Thanks again.

Sorry, my fault. In my language, file is translated as archive and I mess the words.
You’re right. We miss a setting into the scheduler and not only on-going. Hope they improve this on avast 5.

That sucks…hopefully that feature will be in avast 5

But in the meantime, do you know of a way to change the priority of a scheduled scan (reasons above)?

Thanks again.

It’s not necessary. On-demand scanning run at top most priority available. Only if you send the scanning “to background” it would have a lower priority.

Would a scheduled on-demand scan still have same priority?

Thanks again.

I think so.

Thanks…and one last thing: Do you know if the user account has to be logged in in order for a scan schedule to take place?

I think the user must be logged. avast scheduler does not run at system account (i.e., without the user logged).

OK…well hopefully those features will be included into future versions of avast

Thanks for your help!

We already suggested a lot of improvements for the scheduler…

  1. Turn off the computer.
  2. Priority.
  3. More time schedule options.
  4. Run while not logged.

:stuck_out_tongue:

Well, did they listen ? >:( Evidently not lol

Hope they do on avast 5…

Scheduled tasks are running inside of the ashServ.exe service - so certainly nobody has to be logged on for the scheduled task to be started (as can be easily revealed by a small experiment - schedule a task two minutes ahead and log off ;)).

Thanks for the correction… don’t forget the other wishes :wink: