webroot blocking ctirix remote session - windows 10 os

  • 17 November 2016
  • 2 replies
  • 409 views

Just loaded webroot on my laptop that I remote into work with using Citrix.  Windows 10 os...webroot is blocking...any suggestions on how to correct?

2 replies

Hi scase28,
 
Welcome to the Webroot Community.
 
You could try seeing if Citrix is being blocked by right-clicking the Webroot icon in your system tray, lower-right, and selecting "Control Active Processes". Check to see if the files associated with Citrix are being blocked and set them to allow.
 
Please let us know if this resolves your issue. :)
BD
Userlevel 7
Hi scase
 
Welcome to the Community Forums.
 
If I may just add to what BD has posted..there are essentially 3 key areas where WSA can be a tad 'over protective' and therefore this can happen/a user can override WSA.  BD has highlighted 1 of them and possibly the most likely...but just in case that does not yeild results the other 2 can also be reached, from the main WSA panel, as follows:
 
  1. PC Security > Block/Allow Files
  2. Identity Protection > Application Protection
 and once there the user usually has the options to:
 
  1. "Allow"
  2. "Protect/Monitor"
  3. "Block/Deny"
In the case of 1. Block/Allow Files
 
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.
 
 
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 will hopefully, in total, help you get to the bottom of what is causing you grief.
 
Do post back with any specific questions that you may have re. the above.
 
Regards, Baldrick

Reply