Solved

after Chrome update never ending circles

  • 8 October 2014
  • 37 replies
  • 1548 views

Userlevel 2
  • Frequent Voice
  • 29 replies
Today after updating Chrome, if doing a search in Google I now get a spinning circle  instead of Webroot's check mark.  I see the check marks in IE whether using Bing or Google for searches.  In Chrome doing a Googe search I get the spinning wheels, but using Bing's search in Chrome I get the WR checkmarks.   WOT's ratings were not affected. 
 
Seems everytime there is a Chrome update Webroot has some kind of problem.  Any idea how long till WR resolves this?
icon

Best answer by nic 16 October 2014, 18:09

Just got an update - we are making progress on fixing this issue.  Devs think they have it figured out, so if that bears fruit then we'll need to get it implemented and QA'd and out to you guys.
View original

37 replies

Userlevel 7
Hi rd52That is exactly how I have to do it sometimes and I am running as an admin on my system...but then again sometimes it works fine just like with this last update which occurred silently...so go figure. Anyway, the main thing is that the underlying is is fixed..Yay!Baldrick
Userlevel 7
Chrome is notorious for being stubborn with extensions once you have manually removed one.  It is actually intentional on Google's part.  With the number of garbage toolbar extentsions out there, and the problem of once you get rid of Ask.com for example the next time you do an update to Adobe or Java that toolbar can come right back, Google has put in security to attempt to block extenions from being re-installed once they have been manually removed.
 
It is a good thing in general, but it does cause some hassles and headaches at times as well.
Userlevel 2
Got an Email informing of the fix.  So while I was in my normal std user account in Chrome I went to extensions deleted the old WR filtering extension and enabled the new version.  The WR checks and spinning circles totally disappeared, couldn't get them to work at all.  I checked in my Administrator account and strangely everything worked, but not in my Windows std acct.    I ended up deleting and reinstalling Chrome and reinstalling the WR ext.  still a no go, it would not work.  
I was finally able to get it to work by opening Chrome in my Windows std. user acct., opening a tab with the WR extension, another tab with the WR extension web site page.  I then threw the old WR extension in the trash and enabled the new version in the other tab.  It worked, now everything is back to normal.
Userlevel 2
I use Chrome for all my sufing.  I feel it is one of the more secure browsers as it is constantly updated.  The reviews seem to suggest that it is quite a secure browser and after using it for so long I am very used to it.  So if I am doing a search for an 'unknown site' I use Bing search.  Using Bing search in the Chrome browser, the Webroot check marks work fine.  I don't know how other search engines are reacting in Chrome as I don't use any of the others.
Userlevel 7
Any time Eklan!  Any time you have a question, problem, etc drop by and let us know.  We have a lot of good people here, and if you have looked around a bit you can see we chat about more than just WSA too 🙂
Thanks David
Userlevel 7
@ wrote:
Home user with spinners here as well, win 7, 64 bit. Is this related to the Chrome shield for unauthenticated script I have on all https sites, including this one?


Hello eklan, welcome to the Webroot Community!
 
Yes it is actually.  However, I urge NOT to allow the scripts to run.  The problem here is that the message does not say WHICH scripts can be allowed.  By allowing, you may be not only dealing with the WSA Web Threat Shield, but also any other unknown script which could contain malware.
 
Google has recently released an update to the browser that is disrupting parts of the Web Threat Shield.  The shield itself appears to be working and blocking unsafe sites, but as you may have noticed the 'reputation' check on search engine results are not: all we see on Chrome when doing a search is the constant circle at each result instead of the usual reputation indicator.
 
Webroot is fully aware of the issue, and they are hard at work on it.  The last update I have had is that a fix is or is close to being ready for Quality testing, and so hopefully we will have a fix in place soon.
 
Until the fix has been completed you might want to use IE or FireFox, at least when using search engines.
 
Please see THIS THREAD for more information as well as comments and updates from Webroot regarding this issue.
Home user with spinners here as well, win 7, 64 bit. Is this related to the Chrome shield for unauthenticated script I have on all https sites, including this one?

Userlevel 7
Badge +55
It means Web Of Trust but it's users make the sites good or bad so I don't find it really trust worthy IMHO but some do.
 

"Add WOT to your browser to protect yourself from online threats that anti-virus software can’t spot

Web safety is not just about viruses and malware. WOT’s ratings are powered by a global community of millions of users who rate websites based on their own experiences. Add WOT to you browser for protection against online threats that only real life experience can detect, such as scams, untrustworthy links, and rogue web stores."
 
Thanks,
 
Daniel 😉
Userlevel 2
What is WOT?..thanks
"
"Hmmmm, rd52...I used to use WOT but stopped after reading/having seen mixed reviews as to it's efficacity."
Userlevel 7
Hmmmm, rd52...I used to use WOT but stopped after reading/having seen mixed reviews as to it's efficacity.
Userlevel 2
I use Chrome whenever possible, even though Google searches has no checks from Webroot, Bing searches in Chrome have the Webroot checks.  I also use WOT which is another indicator of safety no matter which browser I am using.
Userlevel 7
@ wrote:
Thanks I have the same problem..:D
Me too, well, we all do really.  I have just been using IE or Firefox for searches.  At least it lools like a fix will soon be on the way for us 🙂
Userlevel 2
Thanks I have the same problem..:D
Userlevel 7
Awesome!  Thanks Nic and good work to the Dev's!
Userlevel 7
Badge +56
Just got an update - we are making progress on fixing this issue.  Devs think they have it figured out, so if that bears fruit then we'll need to get it implemented and QA'd and out to you guys.
Userlevel 7
Badge +56
Yeah not sure I'd advise changing that setting.  While it might fix the problem, it opens you up to other malware.
Userlevel 7
@ wrote:
"While that does indeed work, I strongly hesitate to advise using it."
 
I understand that and I wouldn't advise to do this without hesitation as well. In this case the unsafe script seems to be from Webroot though, as the checkmarks load successfully after allowing the unsafe script. I didn't intent this to be general advise but rather a possible hint for Webroot staff that might help tracking down the source of the problem and its solution.
 
Kind regards
Just checking, and THANKS!  (I had not actually tried it myself until you brought it up... and it did indeed work like a charm 🙂  )
"While that does indeed work, I strongly hesitate to advise using it."
 
I understand that and I wouldn't advise to do this without hesitation as well. In this case the unsafe script seems to be from Webroot though, as the checkmarks load successfully after allowing the unsafe script. I didn't intent this to be general advise but rather a possible hint for Webroot staff that might help tracking down the source of the problem and its solution.
 
Kind regards
Userlevel 7
@ wrote:
A temporary workaround would be to allow "load unsafe script" option for the page with the search results. The checkmarks should appear then.
 
http://www.brockport.edu/lits/documentation/_media/angel/chrome_unsafe_script.png
 
 
While that does indeed work, I strongly hesitate to advise using it.  The reason is that there is no listing as to which unsafe script is to be loaded.  In the event of both the Webroot Extension AND another really unsafe script being present... what would the result be?  Would that not open the possibility of unwanted results as well?
 
@ @ What do you both think about this?
A temporary workaround would be to allow "load unsafe script" option for the page with the search results. The checkmarks should appear then.
 
http://www.brockport.edu/lits/documentation/_media/angel/chrome_unsafe_script.png
 
 
Userlevel 7
@ wrote:
Well there has been a Chrome update since I first reported it and the spin just keeps on spinning!
Yes, but it's the fact that Chrome keeps Autoupdating in the background which is giving WSA a problem to handle, so it requires a change in Webroot to accommodate how Chrome functions in this respect.
TripleHelix said:
"I or someone else will let you know when the fix is in place it could be a Program Update or an Extension Update"
 
Userlevel 2
Well there has been a Chrome update since I first reported it and the spin just keeps on spinning!
Userlevel 7
Badge +56
We're working on getting this fixed right now.  I'll let you know when we have a solution!
Userlevel 7
Badge +18
Oops! please ignore my previous post I've found out why it works for me, I was still using version 37 xx, now I've just updated to version 38 xx and I'm seeing the same problem as others. doh!

Reply