Webroot + Chrome (sigh)

I'm having the same issue. As soon as I disable Webroot, Chrome works fine. I'm currently using Windows 7.

😃 Welcome to the community. We are getting alot of new members here...which is great.
Sorry you are having problems with this but maybe@TripleHelix or @ would be able to help you...
And the most important is not to give up on WSA because you can always open a Support Ticket or yes it doesn't hurt to change browsers until you or the community can advise you with your issue.
 
Also remember to post back if your solution is fiixed s to help others...Keep us posted..
 
Sherry

Hello Caravelle & RustyNutz and Welcome to the Webroot Community Forums!
 
Best to contact Webroot support:
Support Number: 1-866-612-4227
Support Ticket: https://www.webrootanywhere.com/servicewelcome.asp
 
Thank you
Best regard, Petr.

Hello Caravelle and RustyNutz...and you are both Welcome to the Community! :D
 
I believe what you are seeing is due to the pace at which Chrome is being constantly updated. And I believe Webroot are working to eliminate these issues.
 
You have both said that shutting off WSA resolves the issue. Could you both please try just disabling and re-enabling Identity Shield, to narrow down the issue? Webroot Secure Anywhere Context Help
 
The issue may be resolved by a reinstall of Chrome, if you want to try.
 
Or you could contact Support, who'll collect logs and resolve for you. the official Webroot support system
 
Please let us know how you get on.
 

😃 Hello RustryNutz, Great to have you onboard...I'm running the new update of WSAC on my Mac and other W7 pcs. 
So Im not having that problem. Sorry that you have same issues as ous other new member. Hopefully our otther members can help to reslove this since I cant duplicate the senario.
 
Sherry
 
Thanks  for the back up responses. I always learn here too.;)

Hi Caravelle / Hi RustyNutz
 
May I welcome you both to the Community Forums...http://www.forumsextreme.com/images2/sBo_bouncing2.gif
 
Further to @ tag, I have just checked and I am certainly not having any issue with Chrome & WSA.  As Dermot has recommended as an interim measure just disable the Webroot Filtering EXtension via the ToolsExtensions option in the browser, note the version of the Filtering extension that you now have disabled and get a Support Ticket open, with that in formation in it.
 
Whilst not ideal you will be very well protected by WSA's other modules despite the Filtering extension being disabled and hopefully Support will resolve the issue fairly quickly.  Please take time if you would to post back on how the issue is going/when it is resolved as all of this information is useful to future users who may contact the Community with the same or similar problems.
 
Many thanks in anticipation
 
Regards
 
 
Baldrick

Win 7 sp1 x86
 

 
I checked, this problem at me isn't reproduced.

Thanks, Petr ;)
 
Caravelle / RustyNutz...I think that this only reinforces Dermot's recommendation that this is one for the Support Team; usually the case when an issue like this appears to be sporadic, as re. this one.
 
Regards
 
 
Baldrick

Hello Baldrick, love your string of smiley faces by the way. And this forum is pretty peppy on a Sunday. .everyday we learn so much from you all and our new members asking just great questions. .but its not always fun for the ones posting is it?

Hope everone has a great week Monday. ..

I have been reading this thread, as I was having the same problem with chrome not doing anything until I disabled webroot. So I thought that I would create an account to let you know what has worked for me as a temporary fix.
 
However I have just tried turning off the identity shield and opening up chrome again and it seems to have fixed the issue. 
 
So for me at least the problem is with the Identity shield, as I had tried individually turning off the other protection aspects of the webroot with no luck. Not sure if this is the same for everyone else, but worth a try.

@ wrote:
I have been reading this post as I was having the same problem with chrome not doing anything until I disabled webroot. 
 
However I have just tried turning off the identity shield and opening up chrome again and it seems to have fixed the issue. 
 
So for me at least the problem is with the Identity shield, as I had tried individually turning off the other protection aspects of the webroot with no luck. Not sure if this is the same for everyone else, but worth a try.

Hello Zeusius, and Welcome to the Webroot Community! :D
 
Many thanks for reporting your findings.
 

Hi Zeusius
 
Welcome to the Community Fora...http://www.forumsextreme.com/images2/sBo_jumping.gif
 
Thanks for the feedback...much appreciated.  But would you also please Open A Support Ticket to let them know that you too have had the issue and what you have found when disabling the Filtering Extension?  It is important that they get as much feedback as to how many users this is affecting and they may, I stress the may, well contact you to get more information if they require it, etc.
 
As I have said previously, you are well protected by the other WSA modules but I am sure that the Support Team will want to get you back fully up and running with all features as soon as they can nail the cause of this sporadic issue.
 
Many thanks again for pitching in with info.  Much appreciated.
 
Regards
 
 
 
Baldrick 

I have no problem with Chrome can you check your Identity Shield to see if it's under Protect if it's under Deny move it over to Protect also every update I have seen with Chrome there will be 2 listed as old-Chrome & new-Chrome it's fine to remove old-Chrome from the list if it is listed. http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C6_IDProtection/CH6c_ManagingProtectedApps.htm
 
HTH,
 
TH

I looked in the Application protection and all instances of chrome old and new were all checked as protect anyway none were set to deny.
 
My brother also has the exact same problem with chrome and webroot, disabling the identity shield and this also fixed his problem too.

Can you look here when Chrome is running to see if it's being Monitored? http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C10_SystemControl/CH10b_ControllingProcesses.htm also can you tell me what version you are using and if you are using the Developers versions?
 
This is my version:

 
Thanks,
 
Daniel

I have looked and it says there are 8 instances of chrome running and they are set to allow.

Also the version of chrome that I am using is:

33.0.1750.154 m

Can you please do a clean reinstall of WSA? Download a Copy Here and make sure you have a copy of your keycode then Uninstall WSA and Reboot and install with the new installer let it finish it's install scan then Reboot once again and please let us know if that corrects your issue also don't import any settings just set it up the way you like after!
 
Thanks,
 
Daniel

What did I start ? :catwink:
 
I tried disabling Identity Shield, and Chrome is now back to normal.  I re-enabled it, Chrome went back to sleep.  I re-disabled it Chrome woke up again. However, I do not know how to report the information requested.   I see things like "can you tell me what version you are using?"   Where does it say what version of Webroot one is using ?  There is no Help/About that I can see, Webroot is one of these new-fangled programs which expects you to be psychic (rather like Android apps in that respect).  Help just takes you to an online guide (not much use if your browser isn't working !). And as for "note the version of the Filtering extension that you now have disabled", where is that information hidden please ?
 
Thanks
 
Caravelle

Hi Caravelle
 
I know that it can be a little difficult sometimes when reporting issues but best bet is to just explain the issue and what you have done in your own terms and then Support will query anything that they do not understand.
 
In terms of the Webroot Filtering Extension you can disable it/find the information required by clicking on the three horizontal lines icon just under the 'X' in the top righthand corner of the browser.  From the context menu displayed navigate and hover over the 'Tools' entry and that should open up a further context menu on which you click on the Extensions entry to open the browser page showing all your Chrome extensions.
 
Towards the bottom of the list you should see the two Webroot-related extensions, and next the the Web Filtering one you should see the version no. (in the format v1.2.3.45) and to the right of that is a check box to enable/disable the extension itself.
 
HTH?
 
Regards
 
 
Baldrick
 
 
 
 

Disabling the Webroot Filtering Extension did nothing for me. I have since uninstalled Webroot and Re-Installed it but this did nothing and it is still causing problems with chrome. So as of now I have got identity shield disabled and have created a support ticket. So we will see what happens.

Thanks.  I can certainly explain what I do and see on my PC and what I have done in clear terms.
 
I was not aware that the extension thing referred to in this thread is something you find in Chrome, not in Webroot.  And the program version presumably therefore refers to the version of Chrome, which I do know how to find.  I simply disabled the identity protection setting in Webroot itself.
 
Caravelle
 
 

Thanks sorry the reinstall didn't work and the Support Inbox would be the next step so please let us know the outcome as it could help others. Like I said it's working fine here.
 
Thanks,
 
Daniel

@ wrote:
Thanks.  I can certainly explain what I do and see on my PC and what I have done in clear terms.
 
I was not aware that the extension thing referred to in this thread is something you find in Chrome, not in Webroot.  And the program version presumably therefore refers to the version of Chrome, which I do know how to find.  I simply disabled the identity protection setting in Webroot itself.
 
Caravelle
 
 

Here you go:
 

 
HTH,
 
Daniel

The reinstall was worth a try as it usually fixes most things, I was simply stating my findings and not trying to be ungrateful. Sorry if it came across that way. When I hear back from support I will let the forum know of my findings.

@ wrote:
The reinstall was worth a try as it usually fixes most things, I was simply stating my findings and not trying to be ungrateful. Sorry if it came across that way. When I hear back from support I will let the forum know of my findings.

Never we just try a few things and the Support Inbox is the last suggestion!
 
Cheers,
 
Daniel  😉