![]() ![]() It’s useless though, if this feature prevents Chrome from functioning. Disappointing, as I’d like to keep Chrome protected. ![]() It seems a shame, as this feature had been working for quite a while in “protect” mode, but apparently has a hairball today if I don’t explicitly allow the exe in the Chrome\Application directory. I changed this one setting to “allow” and Chrome immediately started working normally again. So.I searched, found this thread and lit up, as I’ve been WebRoot user for several years and thought this might be an answer. I canceled all Chrome processes, including the crash handler. ![]() I checked Task Manager, and sure enough each time I tried, another process would be spawned, but no visible would open. Today it opened a few times then refused to. Yesterday, and for the last several weeks, Chrome has opened with no problem. SO glad I found this thread (thanks, Google!). It seems this issue has come up once again. Update came out it blocked Chrome on the first box but tried to install theįiltering extension on the second box. The first box, but not on the second, and when the webroot secureanywhere I'm guessing that the Webroot Filtering Extension was already installed on Confirm your email by clicking the link sent to your inbox. Create a security question and click Register Now. Create a security code using a combination of six letters, numbers, and special characters. On the other windows 7 box, when I started Chrome I got the messageĪsking if I wanted to install the Webroot Filtering Extension. Visit my. or click Access Web Console via your Webroot software. Which I suspect is related to me trying to reinstall Chrome. It was also "Deny" on setup.exe in c:usersxxxappdatalocaltempcr_53580.tmp In my case, besides two (slightly different) chrome.dll files and the chrome_child.dll, Need to do a full Windows 7 reinstall to clean up the machine. I tried removing it and reinstalling a few times but it just never came up. On one of my windows 7 boxes last night, Chrome just stopped working. I have not installed a new Chrome for many months. Just pushed out sometime between Saturday (Feb 1, 2014) and Monday night. The problem is not related to a new version of Chrome, it is something Webroot
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |