I'm sure this is an old problem but... Thunderbird "not responding"

  • 10 February 2017
  • 2 replies
  • 79 views

My computers keep haveing a problem with T-bird - it keeps going into "not responding." This happens when I run junk controls (auto or manually). T-bird suggests adding the email program to the antivirus "approved" programs. Does WR have such a thing, and, if so, how do I add it.
 
Rick

2 replies

Userlevel 7
Badge +62
Hello and Welcome to the Webroot Community, RickinFlorida
 
Please have a look here at these PC User Guide articles that can help you with unblocking and allowing if you are totally sure these programs or sites are not malicious.
 
Controlling active processes
http://live.webrootanywhere.com/content/643/Controlling-Active-Processes
Blocking/Allowing files
http://live.webrootanywhere.com/content/604/Blocking-or-Allowing-Files
Managing protected applications
http://live.webrootanywhere.com/content/610/Managing-Protected-Applications
Managing active connections
http://live.webrootanywhere.com/content/601/Managing-Active-Connections
 
 
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:
 
  1. PC Security > Block/Allow Files
  2. Identity Protection > Application Protection
  3. 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.
 
Hope this info helps. You may also submit a trouble ticket to Webroot support if you would lneed more help.This is a free service with a Webroot subscription.
 
Userlevel 7
Hi RickinFlorida
 
Welcome to the Community Forums.
 
If I may just add here...for context...I use TB as my main email client and have never had the issue that you are reporting or had to configure WSA to allow it to work properly with TB.
 
Having said that the information that Sherry has posted should sort out the issue if it is indeed due to WSA being overprotective of TB.
 
Also, having done a little bit of research (out of interest ;)) I think that it may be useful to take a look at THIS ARTICLE from the Mozilla Wiki, which deals with this subject; lists a whole range of AVs, AMs, etc., that have been reported as conflict/causing the issue yo are reporting...and I am glad to say that WSA is not listed. :D...but something therein may be of assistance generically.
 
Regards, Baldrick

Reply