Uncheck the 'Scan on boot up if computer....' option under the Scan Schedule tabs in Settings, and then check on it after a reboot or the following morning (when you would usually have rebooted if you switch your PC off overnight).
Does anybody find that the option has somehow gotten itself rechecked, ie, it is ON again?
Have just noticed this (but to be fair have had some issues with this option before & uninstalled completely and reinstalled to try to resolve it.)
Be interested to see if this is happening to anyone. Am running latest build .193.
Best answer by BaldrickView original
oh and thanks for the frozen scan KB article 🙂
I just finished up the sd card corruption one you had suggested as well. :)
Thanks again 🙂
How about we make a knowledgebase article out of the question and answer? That would provide an easily searchable answer for the question, if others happen to have it as well.
Jim, look what is described in the user guide:
I am of opinion that it could be corrected in the sense that there are instances where a scan is triggered anyway even if this option is disabled.
Sorry but I have an educative mood today :D
maybe a note in the user guide would be enough
pegas is presently on his phone 🙂
However, please consider changing of wording "Scan on boot up if the computer is off at the scheduled time" because even if this option is unchecked (i.e. disabled), it means that users don't count with scans on boot up at all, yet there are cases where scans run on boot up anyway.
As for your questions, 17 items initiate on boot up, nothing special (wireless, VAIO things, ATI things, audio and video services and a few others). Yes, I do have scheduled a routine scan daily at 12:00 p.m.
If the scheduled scan is missed (PC is turned off) let's say twice or three times, a scan runs during the next boot up. I don't se anything bad in this behaviour as long as the option is enabled. However if the option is disabled I would expect literally no scans during boot up regardless how many scans were missed.
Nevertheless it's probably coded in WSA that if a couple of scans is missed, it triggers a scan anyway, sometimes during boot up, sometimes later after boot up.
EDIT: Just noticed that a scan has run cca 30 mins after I booted up my PC today. So my above last sentence is confirmed.
Also, do you have scheduled scans enabled?
While I don't have a problem with keeping settings I wonder why boot up scans are running from time to time even if this option is disabled. I always disable this option after installation of WSA but sometimes, it seems randomly, the boot up scan runs anyway. I thought that a sense of disabling this option is to avoid boot up scans completely.
Have not noticed any further issues re. this problem so am happy for this to be marked as solved.
It's been about three weeks since Joe S. took a look at the system and reset the settings. Have you encountered the issue again since then? I'm wondering if it's ok to mark this conversation as solved or not. I wouldn't want to do that prematurely. Thanks 🙂
No it did not but then I was contacted by Joe S from Support who connected by LogMeIn and did some resetting. Currently, reviewing what the result of that is and will look to get back to him shortly with an update.
I'm reviewing support tickets, and I came across this one. Did the uninstall and reinstall end up taking care of the problem, or did it ever occur again?