Chrome keeps crashing

The 9.0.30.72 update worked briefly, but the problem has reappeared. I have upgraded to 9.0.30.75, annoyingly, I had to download the update manually, I thought it was supposed to keep itself up to date, and even more annoyingly, I can’t open Chrome, nor hyperlinks in emails without turning Webroot off. It is not acceptable that Webroot has been preventing such a commonly used app from working and that this has been going  on for so long.

Are you guys sure this is fixed? I have a brand new computer that I installed Webroot SecureAnywhwere 9.0.30.72 on 3/30/2021 and Today I cannot open chrome at all. Everything else is fine. I am going to try and call in here shortly. @coscooper@dstokes1 

That has not fixed it. The only fix I have found is uninstalling Webroot and using Windows Defender.

Correction: uninstalling, restarting, and reinstalling the latest version, 9.0.30.72, seems to have cured it. Thank you TripleHelix!

Here’s a solution that I don’t know why it’s not here yet, but this worked for me and support told me to do it. So it is solved but this forrum isn’t updated
1.Open Webroot on your computer
2. On the right side of the application you will see Identity Protection
3. Just beside my account you will see gear icon
4. Click on the icon
5. It will bring you to a new window
6. On the new window click on Application Protection
7. From the list find Google Chrome and change it to Allow

We Beta testers are testing a new version that has a fix for the Chrome issue but we are not told when it will be release to all at this time.

Thanks,

@dstokes1 

So your only “support” is to disable an important part of your software in order for it to work with the most popular browser on the market.

I expect that we will receive some compensation or the option for a refund as this is just ridiculous.

Hello everyone...we very much understand the frustration to this issue and has been experienced by us at Webroot, as well because of the changes to Chrome development. The next agent release will have a fix for this issue though.

For now and until this next agent release, disabling Identity Shield in the Policy or Policies for the affected Site (business) and Endpoints themselves (Consumer) should resolve the issue. The best course would be to copy the existing Workstation Policy if Best Practice is being followed for Business Consoles, disable Identity Shield in this new Policy and apply to the affected Sites. When the new agent version is released, either re-enable Identity Shield for this new Policy or assign the original Workstation Default Policy. As mentioned by another Community member, creating Overrides for the Chrome EXE can be frustrating as the MD5 hashes change often. We know you want the fix now, but hope the above information is helpful in the meantime.

I am also a IT MSP, and have around 300 managed endpoints.

I have started to see this issue on multiple devices. Started back in september.

I have tried a lot of things and only sollution is to do a complete reinstall, if you want to run with all shields ON.

Only workaround i have found is, as mentioned, to start in incognito mode from a shortcut with this parameter, and then open a “normal window” from there.

You need to FIX THIS NOW!!!!

I have the same issue on both my Windows 10 64-bit computers and several other in our company. Not always but often.
Disabling web shields makes it go away. It also workable to open chrome in incognito and then open a new normal window from the incognito session.

This issue has been around for at least 3 months and needs to be fixed NOW. I for one will not be renewing our companies subscriptions if this is how you handle serious buggs like this one.

Have had this same issue for months (at least since September).  Flagging chrome in Application Protection to allow lets it open but has to be redone almost every day for a new line and protection is filled with chrome_exe’s and old_chrome.exe’s that have been moved to temp directories as the latest one gets added.

Reinstalled Webroot at one point a couple months back without importing old settings and it fixed the issue for about a month and then it went right back to the same behavior.   Incredibly frustrating this has been a problem for so long.

We are also an MSP and  seeing this issue popup for more and more users.  It doesn’t seem to be every machine and we are working around it by disabling features.  I know this is a community thread, and I believe we have opened tickets with webroot and get told to reinstall on every machine… which is not an acceptable solution.  Looking for an actual fix.

@dww  sorry I didn’t know there were issues with the MSP’s as this thread is for Consumers so I would suggest you contact MSP and or Business support. I will ping @coscooper to see if he can add anything?

https://www.webroot.com/us/en/about/contact-us

Thanks,

Hello @alexv 

Note that is only a work around and when you use Chrome you don’t have the full protection of the Identity Shield under Allow but only when it is under Protected.

I have not seen this issue with Chrome and Webroot’s ID Shield. I would suggest you do a clean reinstall of WSA and make sure Chrome is under Protect!

I Protect all of these apps without issues!

Please follow the steps closely!

• Make sure you have a copy of your 20 Character Alphanumeric Keycode! Example: SA69-AAAA-A783-DE78-XXXX
• Be sure you add your Keycode to your Online Console: Webroot SecureAnywhere Online Console
• KEEP the computer online for Uninstall and Reinstall to make sure it works correctly
• Download a Copy Here (Best Buy Geek Squad Subscription PC users click HERE) Let us know if it is the Mac version you need
• Uninstall WSA and Reboot
• Look to see if this folder is gone: C:\ProgramData\WRData and if it’s there delete it. (Hidden Area)
• Install with the new installer, enter your Keycode
• Let it finish it's install scan
• Reboot once again
• DO NOT import any old settings as you can set it up as you like once it's done

Please let us know if that resolves your issue?

Thanks,