Jump to content

Experimental Build with Webroot and Chrome


puff_m_d

Recommended Posts

Hello,

 

I just changed AV here to Webroot Secure Anywhere. I have had two other AV installed and not seen any conflicts. Since installing Webroot, Chrome will not launch unless I deactivate the Chrome shield in MBAE. No pop-ups, warnings, or anything showing in the Logs tab of MBAE when this happens. If you need any further information, just ask and I will get it to you at my earliest convenience. So far, this is the only issue that I have encountered.

Link to post
Share on other sites

Hello,

 

I did a bit more troubleshooting as I know the Identity Shield of Webroot can sometimes cause problems. Deactivating it did not help. I also tried shutting down Webroot but Chrome would still not launch. The only way to launch Chrome is to deactivate the Chrome shield in MBAE. It is just strange that I did not have this issue before I installed Webroot...

Link to post
Share on other sites

  • Staff

There used to be a conflict with Webroot's IdentifyShield in the past, but it was for IE and Firefox. Maybe lately they added it also to Chrome? Try contacting Webroot (maybe through Wilders) to see if they can exclude MBAE from their IdentityShield again.

Link to post
Share on other sites

Hello Pedro,

 

I may have found the issue but need another day or two to know for sure.

Whenever I test Webroot, I usually install and run a little program from PcWinTech called CleanMem. Webroot has this issue of causing some programs to use more RAM than normal, so when testing I use CleanMem to trim the RAM usage. I tried everything from uninstalling all other security apps except MBAE and getting rid of all extensions in Chrome. Nothing worked until I remembered I installed CleanMem at the same time. Possible CleanMem is doing something that caused my shields for Chrome and WinRAR to not let them launch. Give me another couple days to be sure the issue does not come back. If the issue does not reappear, then I would say it is safe to assume that somehow CleanMem caused the issue.

Link to post
Share on other sites

  • 1 month later...

Hello Pedro,

 

Sorry for my late response. I ended up restoring my system to an earlier snapshot and in doing so I am not using either Webroot or CleanMem. In the foreseeable future I do not plan on installing either of these. Since no one else has posted with same issues here and this setup no longer applies to me, you may close this thread if you wish.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.