As from today, Google Chrome will not display any web-pages on my Vista 32 PC, unless I turn Webroot completely off, when it miraculously works perfectly again. It was fine before but something has changed overnight (UK time) and the fault started on start-up this morning. Chrome works fine on other machines which do not have Webroot.
Other posts on the Google Chrome Forum confirm I am not the only one.
Does anyone have an answer please, apart from the obvious ones of looking elsewhere for my virus protection or using another browser ?
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
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 !
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.
When I clicked the button "Check for Software Updates" a box popped up saying that I was currently using the newest SecureAnywhere software.
So I ignored that and followed the link provided in the message before last, downloaded and installed version 220.127.116.11 anyway (mercifully, no reboot required) and everything seems to work.
Thanks to all who have helped resolve this issue. It's much appreciated. Don't get me wrong when I say I hope I won't be back here for a long time :catvery-happy:
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 v18.104.22.168 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.
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.
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.
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.
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?
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.
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 !
Best regard, Petr.
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?
I've been having the same problem as the other folks here and when I try to reinstall Chrome, it doesn't give me any options as to where to install; it simply installs into Appdata. Any ideas here?
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
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."
Best regard, Petr.
if you see any Chrome files set to "Deny" here, set them to "Allow".
As my settings were all on "Protect" I replied asking what I should do. The next reply said:
The issue occurred with the new Chrome update. The updated files since then have been white listed, and you should no longer be experiencing this problem. If you are, please run a scan and Webroot should be notified of the change automatically, without changes to the ID shield. But setting these files from Deny to Allow should resolve this issue completely. If everything is set to Protect, you should not have issues running Chrome.
I can't find anything in the online Help on this Application Protection function which explains what "Protect", "Allow" and "Deny" are supposed to do, but if the idea of Webroot is to protect me, then "Protect" sounds like the one I should be using. Can anyone explain in plain English what the difference is ?
I have run a scan twice. Chrome does not work with the settings on Protect. It does if the settings are "Allow".
Back to Support again...