New
#11
Thanks to Corrine for your continued advice.
I have at last got the scheduled scan to run. I thought I had achieved this by removing all the conditions in Task Scheduler (the scan has such a light touch that I am quite content not to specify only when idle and on AC power). As it happens, the computer was idle and on AC power when the scan ran, which is just as well because I've discovered that these options become checked again on reboot! Had it been in use or on battery power, the scan presumably would not have run.
There seem to be an awful lot of hoops to jump through to get the scheduled scan set up, and I do wonder whether it's best just to wait till the icon turns orange and run a manual scan.
Corrine, you may wish to comment on the following:
1. Why are some of the options in Task Scheduler not retained on reboot? For MSE, this means that you cannot choose to have the scan start when the computer is in use, which is what I want to do. To have to remember to leave the computer live and plugged in to get MSE to scan is inconvenient to say the least, and probably unrealistic for many people.
2. When the "start scan only when computer is on but not in use" is checked, MS Antimalware disappears from Task Scheduler. Does that mean that the scan would not run whatever?
3. I understand that a scan cannot run while the computer is asleep, but why doesn't the Task Scheduler obey the instruction to wake it up?
4. I don't understand how the load on the servers can advance or delay the start time of a scan. (I can see that there may be some effect on the running of a scan if you have chosen to check for definition updates, but that's a different matter.)
This may be a bit long-winded for something that I can easily work round. But, while MSE functions way better than any of the several AV packages I've used over the years, this is the first real problem I've had in setting up an automatic scan to run reliably.