Hi djcPH

 

Welcome to the Community Forums.

 

The short answer is 'NO'...not that I am aware of or that I have ever come across.  May I ask as to why you are asking this question?  Are you seeing or do yo believe that yo have some issues?

 

Regards, Baldrick

---

AT this point I'm grasping at straws to be perfectly honest.  Chrome hangs upon launching, becomes unresponsive, and I'm wondering if I need to enable/allow something within WebRoot.  (WR installed 01/12/2015)

---

Hi djcPH

 

I understand...there are a number of places in WSA where a file/app can be flagged as 'Allow', 'Block' & 'Monitor' all of which can affect how that app/file then responds...so would you plese review this KB Article that details those places, what to look for and how to adjust the settings, etc., and see if that helps in anyway in relation to the chrome executable.

 

Do post back whether that helps or not to let us know how you got on.

 

Regards, Baldrick

---

Yo Baldrick,

 

I see all installed browers' .exe's in "PROTECT" status under the 'Application Protection' tab.  And there are no entries under the 'PC Security' tabs.

---

Hi djcPH

 

OK, well what you could try is to add the chrome executable under the 'Block/Allow Files' tab with a status of 'Allow', and see if that helps?  You should not have to do that but I have found on accassion that it does.

 

One further question though...did this issue start for you after installing WSA...or have you had it installed for a while before?  The reason I ask is because further options would be to either (i) uninstall/reinstall Chrome and/or, depending on whether that helps or not (ii) uninstall/cleas reinstall WSA (for which I can provide you with instructions to follow...and is very quick and easy to do).

 

Anyway, see how the above goes and let us know what transpires.  We can then see what may be the next best course of action as a result.

 

Regards, Baldrick

---

Hi Baldrick,  I apologize for the delay.  I don't believe WR is any way involved with this issue.  But I did add 'chrome.exe' to the 'Block/Allow files' list, and set to allow.  Looking back over my handwritten log, I installed WRC on Jan 12th, 2015, and there were no problems until I updated Adobe Flash Player to V16.0.0.287 on Jan. 23rd.  **bleep**, I know better than to respond to Adobe updates;  I always go out to the Adobe site manually and compare V's.  I'll blame it on aging, and my poor memory.

 

There's a 'Google Products forum' that I've been using to try to resolve the issue:  (no luck yet)

 

https://productforums.google.com/forum/#!forum/chrome/chrome/Ok8FQycs1h8



http://www.itechfever.com/google-chrome-wont-open-error-fix/

 

So Thank You for your support, and especially your prompt response;  you're far better than most.

 

Feel free to share with your supv.

 

dj cornier

---

Hello and Welcome to the Webroot Community!

 

Just to let you know there is a new Flash Update Adobe Flash Player 16.0.0.296 see here: https://community.webroot.com/t5/Security-Industry-News/Adobe-Flash-Player-16-0-0-287-and-as-of-Jan-25-2015-the-build-is/m-p/183257#M12051 and another Google Chrome Update 40.0.2214.93 https://community.webroot.com/t5/Techie/Google-Chrome-40-0-2214-93-Released/td-p/183575 also most of us are Volunteers such as Baldrick and myself and many others. Come by often to visit.

 

Thanks,

 

Daniel 😉

---

Hi dj

 

No worries...good to know that it is not in your opinion anything to do with WSA, and I see that Daniel has chipped in with something very useful...as usual.

 

And as he has said...hope tomsee you around in The Community.

 

Regards, Baldrick

---