Webroot + Chrome (sigh)

Hi Caravelle
 
Completely understand your position...and hope that I was not out of turn by trying to interest you in participation?http://www.forumsextreme.com/images2/sEm_blush8.gif
 
Well, you know where we are if you need us/have an issue or a question in the future (hopefully not the latter).
 
All the best
 
 
Baldrick

Hi Caravelle
 
Again, many thanks for sharing your experiences and glad that your issue is sorted out.  We get there in the end through a combined team effort...you , the Community, Support, etc.
 
I do hope that you are not serious when you say "...I hope I won't be back here for a long time"...http://www.forumsextreme.com/images2/sCo_huhsign.gif as this Community is about so much more than it's primary mission (supporting the user community).  It is also a place to learn, have fun and share experiences.  I am sure that from what you have just experienced you would be able to help fellow users in the same or similar circumstances http://www.forumsextreme.com/images2/sHa_comfort.gif...so please do drop by from time to time and contribute as best you can.
 
Most of us are volunteers who get a buzz by helping others...so why not join in?
 
See you around...I hope.
 
Regards
 
 
Baldrick

Hi Caravelle
 
Yes, for a number of things running a scan does seem to initiate a refresh or at least a transmission of other elements apart from scan information.  If you issue commands from your Web Console  then you will most likely find that they are executed quicker as a result of a scan.
 
But as Petr stated in his post there should have been a silent update of WSA to v8.0.4.68 which includes what looks like a fix for this issue (see this thread for details...if you have not already).  Check that you have this version and if not then initial a manual 'Check for Updates' to get it...but I suspect that you already have.
 
Thanks for posting back with your information...it is much appreicated and most useful to the Community as a whole.
 
Regards
 
 
Baldrick

This is what I told support earlier:
 
Chrome continues to work with all of them [the settings] set to Protect apart from "new_chrome.exe in c:usersmichaelappdatalocalgooglechromeapplication". Setting that to "Protect" stops Chrome from going to any websites. Searching my C: drive for the word "Chrome" produces a screen full of files all in the same appdata path, apart from the shortcut on the desktop. I'm afraid it will be a while before I can do much more.  This PC runs 24 hours a day collecting data, and messing about installing and uninstalling things risks losing data (particularly if the PC has to be restarted).  So jobs like that tend to get done in the wee small hours when there is not much data coming in - if I can stay awake that long.  A Windows update is a major pain !
 
HOWEVER, just for the hell of it, I reset the file mentioned above to "Protect", ran a Webroot scan (I gather from what support said earlier that this effectively reboots settings), opened a new instance of Chrome and it worked.   Obviously I need to double-check and try closing down and re-opening Webroot and all instances of Chrome, and see what happens after a PC reboot later on tonight, but all I can say so far is that something appears to have happened invisibly.  Does running a scan cause Webroot to update itself ?  if so maybe they have fixed the problem.
 
Thanks
 
Caravelle

I'm still waiting for a further response from Support.
 
Rakanisheu wrote 
If you can do a quick uninstall/reinstall and see if it helps.Is that uninstall/reinstall Chrome or Webroot or both ?
 
I agree on the point that we should not be tinkering with where Chrome installs.  Vast numbers of users have no idea how to take control of the process - they rely on it to happen automatically.  Webroot has to cater for them too, and they are paying customers.
 
Caravelle

I was just saying it in a general sense and wasnt implying you did set it to allow 🙂

If you can do a quick uninstall/reinstall and see if it helps. Please note that there are multple layers of protection so even if you set Chrome to allow your leaving your PC vunerable.

I've had this issue since Saturday. The only way I've been able to get on the net is Internet Explorer, which I don't care for. I prefer to use Google. While checking into to this problem, I recently found on a Google Chrome site that the problem is not just occurring with Webroot, it is also occurring with McFee. I've read through all these posts and I'm still not exactly sure how to fix it.
 
There appears to be some correlation between a Microsoft Critical Update that got automatically downloaded to my machine on Thursday and others have reported that also.
 
I don't want to take off the Webroot protection for Google, that sounds self distructive. I've read some people are going to Chrome to fix problem, and some are turning off the Webroot protection and I don't want to do that.
 
So how "exactly" step by step do I fix this problem?
 
Thank you.

The odd thing is, Support don't seem to be giving any advice to install Chrome other than where it installs itself.
 
Having told them precisely which file is causing the problem on my system and where it is, this is the latest response I have had:
 
Thank you for this information, we will forward it to the development team. Using Allow for these files shouldn't cause any issues. Thank you for your patience as we work to resolve this issue. Let us know if you need further assistance.  But then they don't seem to be reading what I say.  It's using "Protect" that causes the issue !
 
Caravelle
 
 

Hi Blackacre
 
Welcome to the Community Fora...http://www.forumsextreme.com/images2/sBo_bounce2.gifhttp://www.forumsextreme.com/images2/sBo_bounce2.gifhttp://www.forumsextreme.com/images2/sBo_bounce2.gifhttp://www.forumsextreme.com/images2/sBo_bounce2.gifhttp://www.forumsextreme.com/images2/sBo_bounce2.gifhttp://www.forumsextreme.com/images2/sBo_bounce2.gifhttp://www.forumsextreme.com/images2/sBo_bounce2.gif
 
I have found the following article that should assist you, but it just one of many available on the Web.
 
Hope that helps?
 
Regards
 
 
Baldrick

@ wrote:
Thank you, but what is the definition of "protected data" ?  I am not being awkward, I am simply trying to get to the bottom of what is being protected here and how Webroot knows what data I want to protect and where it is.  And under "Allow" why would anyone NOT want an application secured against malware ?  I do not know enough about <any> application to trust it, and even if I decided to trust it that would not stop it from being infected after my decision was made.  It just makes no sense to me.
 
I have done some time-consuming experimenting and this is the text of my latest approach to Support:
 
I have gone through the Chrome files set to "Allow", switching them back to "Protect". Chrome continues to work with all of them set to Protect apart from "new_chrome.exe in c:usersmichaelappdatalocalgooglechromeapplication". Setting that to "Protect" stops Chrome from going to any websites.  Caravelle
 
 

Chrome should be installed in Program Files not in Appdata and some files will be in Appdata but not the Program itself and protected data http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C6_IDProtection/CH6a_ManagingID.htm
 
HTH,
 
Daniel 

Hi Caravelle
 

• Protect. “Protected applications” are secured against information-stealing malware, but also have full access to data on the system. You might want to add financial management software to the category. When you run a protected application, the Webroot icon in the system tray displays a padlock: [img]http://www.webroot.com/En_US/SecureAnywhere/PC/Content/Resources/Images/Icon_lock.png[/img]
• Allow. “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.”
• Deny. “Denied applications” cannot view or capture protected data on the system, but can otherwise run normally.

Read more:
 http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C6_IDProtection/CH6c_ManagingProtectedApps.htm
 
 
From WSA support:
"The issue you are reporting is one we are aware of and we are working to resolve it as quickly as possible."
 
Thank you
Best regard, Petr.
 

Hello, Zeusisus,..Welcome to the community...where we all are here to support each other with just about anything! Look around join in anytime...

Sherry