Nagging problem where Chrome won’t load at all until we do the following
- shutdown protection
- launch chrome
- reboot / enable protection
Now Chrome works fine, this is a great bandaid but I’d appreciate an understanding of whats going on and a more permanant solution.
Best answer by dspigelmView original
Okay, there's news on this front. The newest version of the Webroot agent - 184.108.40.206 - fixes the issue. I know because I'm now running that version, and Chrome now works properly. But, at this time, there's a little bit of an issue. Now if you're talking about adding a new computer, it will now get the new version. But existing computers will not, for now. They're trying to manage the rollout, which doesn't help people who are having the problem. To fix the problem, you can use the MD5 signature to permit the specific version of Chrome that is having the problem, as noted above. If a newer version comes out that doesn’t fix the problem, though, it will have a different MD5 signature, and the problem will return.
The alternative solution is a little bit more labor intensive, but offers a long-term fix:
If you don’t remove the WRData folder, apparently, it won’t work. But I now have it working properly.
May I suggest that you do a clean reinstall of WSA.
Please follow the steps closely!
Please let us know if that resolves your issue?
What version of Chrome do you use? I have no issues with the current release.
Generic install, Windows 10, Office, Chrome - nothing special. No sandbox