There is one snag, however-the MD5 is different for each version of Chrome. Copy the MD5 into that pop up and then have the users right-click on the webroot symbol in their notifications and refresh the configuration. In that log there will be a line that includes both the SHA256 and MD5 hashes. When the scan finishes there will be a button to "Save Scan Log" which creates a text file of the log. The easiest way to generate an MD5 for Chrome is to browse to the application (chrome.exe), right-click it, and select Scan with Webroot. That will bring you to a popup that needs the MD5 for the program. To do that one selects the computer or computers in their organization to apply the exclusion, then select Agent Commands::Identity Shield::Allow Application. The solution is to manually exclude chrome.exe from that protection from within the Webroot management console. The issue is in their Identity Protection. They reported that the issue is not uniformly appearing-that it pops up seemingly randomly-but that they are working to find a solution and have a working work-around. I called Webroot support today and learned that Webroot has known about this issue for a couple of months but still doesn't have a solution for it. He and I compared configs and found only one common denominator: Webroot (anti-virus). Then, after a couple of weeks, users reported that Chrome suddenly worked again. After struggling with it for a while he gave up and moved his users to a different browser. I spoke to a colleague the other day who told me that a couple of months back he had a similar issue. To answer your question-no Chrome related GPOs. Is anyone else having this problem? Anyone know why this is occurring? Anyone know how to fix it more elegantly than what I've come up with? The problem with that fix is, while I can point the icon for the shortcut to the changed program, when the program loads a blank icon appears on the task bar. The only thing I've found that will fix things (though not an elegant solution) is browsing to the installation (C:\Program Files\Google\Chrome\Application) and renaming the application and pointing shortcuts to the new name and then rebooting. Uninstalling and reinstalling doesn't fix things. Ending task on each instance in Task Manager doesn't fix things. Closing Chrome from the notification bar doesn't have any impact. When looking at Task Manager Chrome is running and each time the user attempts to open it another instance appears in task manager. Beginning yesterday and spreading today, Windows 10 Pro users on our network are suddenly unable to launch Google Chrome.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |