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
I haven't yet heard of this happening to others and I'm not able to reproduce the issue on my machine. Is this happening even after clicking "Save All" on the settings screen? Also does this only seem to occur when a new version is installed?
Thanks for the response. It is happening even after clicking "Save All" on the settings screen...and I have done this each day for a week.
I have .193 installed and will certainly check as and when a new version comes out to see if there is any change but I have had .193 for a while and so am not sure what you mean by 'new version'?
Thanks for the info! Please open up a support ticket so that we can gather logs and look further into this. Makes me wonder how many other people might have this same issue but just haven't noticed yet. And please keep us posted.
I just wanted to follow up and see how everything is going. Are you still experiencing that issue? I looked at your support ticket and noticed that you are in the process of arranging a call back time with our Support Team. We are located in the Mountain Time Zone, so 1pm our time will be 7pm your time (British Summer Time or GMT +1). Please let us know what we can do to help get that call back set up at a convenient time for you.
Have been postingre. this issue over at Wilders and someone who shall remain nameless came up with an idea of "...possibly the system not shutting down correctly and it losing the configuration change".
So this is what I posted over there and the results of the initial tests (based on that theory):
Unchecked "Scan on boot up if...." & 'Save All', then closed the WSA GUI only and restarted.
RESULT: Checking after restart shows the "Scan on boot up if...." CHECKED.
Unchecked "Scan on boot up if...." & 'Save All', then closed the WSA down completely using the "Shut down Webroot Protection" option by right clicking the sys tray icon and restarted.
RESULT: Checking after restart shows the "Scan on boot up if...." NOT CHECKED.
Checked the "Scan on boot up if...." AND the "Perform a scheduled Quick Scan..." options & 'Save All', then closed the WSA GUI only and restarted.
RESULT: Checking after restart shows the "Scan on boot up if...." NOT CHECKED BUT the "Perform a scheduled Quick Scan..." WAS STILL CHECKED.
Unchecked "Scan on boot up if...." option, left the the "Perform a scheduled Quick Scan..." option unchecked & 'Save All', then closed the WSA down completely using the "Shut down Webroot Protection" option by right clicking the sys tray icon and restarted.
RESULT: Checking after restart shows the "Scan on boot up if...." AND the "Perform a scheduled Quick Scan..." options were NOT CHECKED.
So, unless I am mistaken or got confused that the "Scan on boot up if...." is affected by system not shutting down correctly and it losing the configuration change BUT this does not affect the "Perform a scheduled Quick Scan..." option.
Not what I had expected but perhaps someone from Support can make some sense of it?
I have updated your support ticket, so we can continue troubleshooting there. This way we can gather logs once again so we can get the most up to date WSA logs. You should be receiving an email from Webroot support shortly.
Thanks so much for your cooperation and patience!!
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?
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.
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 🙂
Have not noticed any further issues re. this problem so am happy for this to be marked as solved.
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.
Also, do you have scheduled scans enabled?
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.
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.
maybe a note in the user guide would be enough
pegas is presently on his phone 🙂
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
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.