Solved

Webroot + Chrome (sigh)



Show first post

64 replies

Userlevel 7
Badge +51
@ wrote:
I have a pretty stupid question for you then: How do I install Chrome in Program Files?
 
After you've download the installer file you need, open the file and follow the instructions on the screen to complete your installation. For additional help, please visit the Chrome Help Center.
 
Thank you
Best regard, Petr.
Userlevel 1
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
 
 
What I don't understand is, why do we need to install chrome somewhere else on our pc when up until this point there has been no problem. There is obviously an issue with the webroot software and there needs to be some sort of fix from their end.

Caravelle I would set chrome to allow for now as that is what I was told to do by customer support, because that fixes the problem temporarily and we will have to wait until an official fix is released.
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.
I was a denied application under WSA>Identity Protection>Application Protection. libpeerconnection.dll was set to deny. I changed that to protect and chrome is working again. Got this helpful hint from Jeff P on the Google Chrome site. It worked.
Userlevel 7
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 didn't set it to "allow" I switched "deny" to "protect"
Userlevel 7
I was just saying it in a general sense and wasnt implying you did set it to allow 🙂
thanks for your help
Userlevel 1
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
Userlevel 7
Hi Caravelle
 
I believe that Rakanisheu was referring to WSA rather than Chrome...but I also take the point that you make when you state "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." :D
 
So, to check if the issue could be, in your case, due to where Chrome is installed would yo ube able to check that out and let us know...and then perhaps we can ask Nic to raise this more directly with the Development Team?
 
Await your further input on this point.
 
Many thanks in anticipation.
 
Regards
 
 
 
Baldrick
Userlevel 1
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
Userlevel 7
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
Userlevel 1
I'm being realistic.  All I know about Webroot is in this thread.  I have nothing to contribute and no interest in Webroot per se.  It's simply a necessary tool that I purchased in the hope that it wouldn't cause me as much trouble and grief as previous rather more well-known products have.   Well done, Webroot, so far just the one glitch, it didn't foul up my PC and support didn't try to claim it was someone else's fault or keep trying to convince me against all evidence to the contrary that rebooting the PC and router would solve everything.
 
I'm afraid I just don't have time to develop an interest in this sort of thing, my other interests are full-time.  Doctors and nurses may find visiting a surgery fun, but I only do it when I have to !
 
Caravelle 

Reply