Chrome keeps crashing

Whoever marked a “best answer” in this thread, this is not the “best answer”.  We anxiously updated to 9.0.30.72, and then to 9.0.30.75.  Yet the issue persists.  Google Chrome will just randomly stop opening on random people’s machines.  Webroot’s answer has only been “they are investigating” and to “send them logs”.  Well, it’s tough to send logs (even though I’ve done it a few times) when your users are spread across the country and want to get back to working *right away*, they don’t have time to faff about with a remote support session while I gather their logs and screw around on their computers.

Hopefully Webroot will come out with a real fix for this at some point.  In the meantime, our only option has been to disable Identity Shield domain-wide.  Nobody has time to deal with “my Google suddenly stopped opening” and the damage users can cause trying to “fix it” themselves.  😣

We have also continued to experience this issue, even with the most updated version of Webroot. One of the things I have noticed is that Chrome DOES start, but it only loads into the Background Processes of the Task Manager and never fully activates into the active apps section. I’ve had to disable sometimes dozens of running processes before fixing it because people keep trying to open the browser over an over again before asking for assistance.

Here is the method I have found that works so the user can continue to click links in emails and local files and will activate the browser. It may seem like a lot of steps, but I have gotten the process down to about a minute.

1. Open the Windows Registry Editor by hitting Win+R and typing regedit.
2. Navigate to HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command
3. Edit the string value in this folder by double-clicking on it and changing the name of the executable file (chrome.exe) to match the modified executable you will be making in step 5.

"C:\Program Files (x86)\Google\Chrome\Application\chrome1.exe" --single-argument %1

4. Close the Registry Editor.
5. Open Windows Explorer to Chrome’s executable (usually C:\Program Files (x86)\Google\Chrome\Application)
6. Create a copy of the chrome.exe file and rename it (I’ve been using chrome1.exe, but anything is viable)

The main issue with this workaround is that the registry entry resets to default when Chrome has an update. Could be once every couple of weeks, could be twice in only a few days. You will have to do the entire process again in that case. Fortunately for me I only have 20 or so machines in a single building to maintain, so anyone with a few hundred or multiple buildings may not want to deal with it the way I have.

I freaking love you. It’s midnight and now I can go to bed. No idea why this worked, but continued to work when I pinned that newly created shortcut.

I literally right clicked on my desktop, new, shortcut, browsed to chrome… and we’re back. Deleted the other shortcuts, and pinned the new one…. Thanks again!