how to speed up filtering extension
since downloading Webroot my operations have slowed considerably. I notice the message at the bottom of the page that reads "waiting for extension Webroot filterning extension". How can I speed up this process. It makes the process getting into trusted sites very, very slow and even to parts of sites once in them.
Userlevel 7
+34
Hi bchilds and welcome to the community.
There have been many problems with the filtering extension slowing down browsers. The best solution for now is to disable it and your browser should be back up to speed.
Webroot still has your back if you wander onto a suspicious site so you are not at a disadvantage.
Nemo
There have been many problems with the filtering extension slowing down browsers. The best solution for now is to disable it and your browser should be back up to speed.
Webroot still has your back if you wander onto a suspicious site so you are not at a disadvantage.
Nemo
Userlevel 7
Hi bchilds
Welcome to the Community Forums.
You are not alone in this as we have had a number of users reprotiing this 'issue' today.
There are a number of things that you can try as a temporary measure, one of which is to disable the Webroot Filtering extension/addon in the browswer that you are using, and seeing if that helps. That should not markedly affect your level of protection which is in the main provided by the WSA Client.
Also, if you are running the latest version you should be able to go to Advanced Settings > Firewall/Web Shield and look to uncheck the 'Enable Web Filtering Driver' option (if that option is available to you) and see if that helps at all.
But most importantly you should Open a Support Ticket to let the Support Team know of this issue; the more information they get on this the better the decision on escalation of the issue will be.
Regards, Baldrick
Welcome to the Community Forums.
You are not alone in this as we have had a number of users reprotiing this 'issue' today.
There are a number of things that you can try as a temporary measure, one of which is to disable the Webroot Filtering extension/addon in the browswer that you are using, and seeing if that helps. That should not markedly affect your level of protection which is in the main provided by the WSA Client.
Also, if you are running the latest version you should be able to go to Advanced Settings > Firewall/Web Shield and look to uncheck the 'Enable Web Filtering Driver' option (if that option is available to you) and see if that helps at all.
But most importantly you should Open a Support Ticket to let the Support Team know of this issue; the more information they get on this the better the decision on escalation of the issue will be.
Regards, Baldrick
Userlevel 7
Hi bchilds
We have just heard from one of the Webroot Staff that they are indeed having backend or serverside issues today...they are working on it and hope to have it sorted by the end of the day.
Regards, Baldrick
We have just heard from one of the Webroot Staff that they are indeed having backend or serverside issues today...they are working on it and hope to have it sorted by the end of the day.
Regards, Baldrick
Hi all
rather than start a new thread I'll ask my question on this thread.
regrding web filtering driver..what is the intended purpose of this function anyway? reason I ask is I have been having an issue with Rhapsody's desktop application where the search function would take a very long time to complete. I contacted their helpdesk and the first thing they asked me was if I was using webroot or not. Short of the story apaprently this is a know issue elsewhere and disabling the web filtering driver it resolved my issue.
Thanks-
rather than start a new thread I'll ask my question on this thread.
regrding web filtering driver..what is the intended purpose of this function anyway? reason I ask is I have been having an issue with Rhapsody's desktop application where the search function would take a very long time to complete. I contacted their helpdesk and the first thing they asked me was if I was using webroot or not. Short of the story apaprently this is a know issue elsewhere and disabling the web filtering driver it resolved my issue.
Thanks-
Userlevel 7
+62
Hello BillR,
Please have a look here at these PC User Guide articles that can help you with unblocking and allowing
Controlling active processes
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C10_SystemControl/CH10b_ControllingPr...
Blocking/Allowing files
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C5_Quarantine/CH5b_BlockingAllowingFi...
Managing protected applications
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C6_IDProtection/CH6c_ManagingProtecte...
You can also submit a Support Ticket if you need files whitelisted.
Lets try to put into English the essence of the areas where a user can tailor what WSA does to protect the system
There are essentially 3 key areas where this can happen/a user can override WSA. These are essentially reached, from the main WSA panel, as follows:
and once there the user usually has the options to:
A. "Allow"
B. "Protect/Monitor"
C. "Block/Deny"
In the case of 1. Detection Configuration
If an item is set to:
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts. Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware. It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status. This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed. You could set it to Monitor and have Webroot check it again.
- "Block", then WSA will treat the items as it would detected malware. It will not be executed, and it will not be written to your hard drive. Detected infections are automatically set to a Block status.
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
In this case:
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
And finally, in the case of 3. Control Active Processes
If a process is set to:
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity. Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
- "Block" means just that...iWSA does not allow it to run on the syste. Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process. Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so wil help you get to the bottom of what is causing you grief.
Please have a look here at these PC User Guide articles that can help you with unblocking and allowing
Controlling active processes
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C10_SystemControl/CH10b_ControllingPr...
Blocking/Allowing files
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C5_Quarantine/CH5b_BlockingAllowingFi...
Managing protected applications
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C6_IDProtection/CH6c_ManagingProtecte...
You can also submit a Support Ticket if you need files whitelisted.
Lets try to put into English the essence of the areas where a user can tailor what WSA does to protect the system
There are essentially 3 key areas where this can happen/a user can override WSA. These are essentially reached, from the main WSA panel, as follows:
- PC Security > Block/Allow Files
- Identity Protection > Application Protection
- Utilities > System Control > Control Active Processes
and once there the user usually has the options to:
A. "Allow"
B. "Protect/Monitor"
C. "Block/Deny"
In the case of 1. Detection Configuration
If an item is set to:
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts. Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware. It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status. This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed. You could set it to Monitor and have Webroot check it again.
- "Block", then WSA will treat the items as it would detected malware. It will not be executed, and it will not be written to your hard drive. Detected infections are automatically set to a Block status.
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
In this case:
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
And finally, in the case of 3. Control Active Processes
If a process is set to:
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity. Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
- "Block" means just that...iWSA does not allow it to run on the syste. Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process. Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so wil help you get to the bottom of what is causing you grief.
Reply
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.