How do I permanently disable features?

How do I permanently turn off the web filter? I find it gets hyperactive at times, and I keep turning it off. Somehow it keeps re-enabling itself. How do I keep it off permanently?

 

Do you have your My Webroot online console setup? If not set it up and go in there and Go To PC Security and check the PC that is having the issue with is set to User Configuration and then in the WSA GUI go to PC security Tab and click on Shields and click the Web Threat Shield to turn it off and save. Notice the Tray Icon will go to Gray with an Exclamation mark. Also Joe said that the Web Threat Shield it being rebuilt for the 2014 product line.

HTH,

TH

 

So I have to create a account on the website to change the programs settings? No thanks! (but thanks for your help)

 

No, I think TH was just referring to the fact that if you had the console centrally managed, it would prevent the local agent from taking configuration changes.

You should be able to turn off the web filtering by disabling the main shield, then shutting down WSA and restarting it (as an administrator if you're using UAC).

Let me know your results!

 

Not sure I follow. By main shield, do you mean 'Realtime shield"? I have tried disabling that three times and it crashed the program each time.

 

No, just the "web threat shield" toggle button.

 

Ok, it is disabled again. I'll see if it stays this time. thanks

 

What just triggered to me is "I tried disabling something and it crashed the program". That is not normal, not-right, and not-common, so something has to be occurring on your system that is causing that symptom.

If you change settings and it does not shut down cleanly, the settings will not necessarily be saved. They save eventually without a shutdown, but it takes a while, and they are held in memory until then. So if yours has been crashing for some reason, it won't save the settings and you'll see them revert.

As a quick fix, turn off the specific item you want to disable, then shut down as recommended. As a long term fix, it's best to figure out why it's crashing so easily (especially with a reproducible crash) on your computer when millions of other users don't encounter such a problem. Then it can at least be fixed for you and also be fixed if there are any other people experiencing the problem without having reported it.

Remember: Webroot doesn't generally say "Sorry, it's normal for <something bad> to happen, so you'll just have to deal with it." If it's crashing, it's REALLY not supposed to be, and they will want to fix it.

From a troubleshooting standpoint and from what I know the folks who troubleshoot would best work with, I'd recommend grabbing wsalogs and getting a set of logs, but don't auto-send them. That way you have a record of the crashing state. Then do an uninstall, reboot, check that the driver is out and the stuff is gone, then reinstall and reboot. If for some reason, the driver or other stuff is not out after uninstall and reboot, that's an indication that something went wonky, so reinstall, reboot, uninstall, reboot, and see if it is clean. If it's not clear then, reinstall, reboot, Uninstall, run wsalogs, reboot, hope it's clean, and if it's not, you've got a cool set of wsalogs that will help diagnose a very rare and hard-to-diagnose problem.

Chances are that it will go: wsalogs, uninstall, reboot, it will be clear, reinstall, reboot, it will work fine and not crash when changing settings. But if it does encounter any odd issues, you have wsalogs from the history of the problem and you have done basic troubleshooting that support would request that would likely fix it, so you skip that support step and can move forward swiftly. Then support will look at it, get the data, find out what's up, if necessary send it to The Joe, and whether it's something obvious (RAM failure) or something that can be programmatically corrected, it will be fixed.

 

If something is crashing at any point, we definitely want to be aware of it as this could even be the cause for the odd web threat shield problems.

Thanks!

 

Regarding the crashes, I think I just needed a reboot.

 

Yes your right Joe I forgot that part, sorry to confuse you clocks.

Daniel