Just now my firewall told me Google Update wanted to connect to the internet. Why? Chrome wasn't open so there's really no reason I can see that it wanted to run. I allowed it hoping things would improve. Nope - Chrome still crashes as soon as it starts up.
I don't use Chrome but that's probably a background process checking for updates on a certain interval. Avira has no firewall, has it? Windows firewall default configuration allows all outbound connections.
I think you should take a second look at the 3 links I posted before. There were lots of other advice than to just disable the sandbox.
Chrome is in the process of rolling out their 64 Bit browser, this will eventually replace the 32Bit version on all compatible systems. there are known issues with the 64 bit version and older plug-ins - and I mean old, these are the old Netscape API ones.
It could be that the update you have is the 64 bit version and is not compatible with your system
There are stand alone installers available which I believe are the 32Bit
https://support.google.com/installer...26299?hl=en-GB
The 64 bit offline installer is here - if it's a bad standard download causing your issue
Google Chrome 64-bit
Various versions are also available Here
Official Link to Download Google Chrome Full Standalone Offline Installer - AskVG
Hopefully one of these will get you working again :)
Last edited by Barman58; 06 Sep 2014 at 16:15.
Create a new browser user profile
https://support.google.com/chrome/answer/142059
If that does not work:
Fully uninstall, and delete all app data, reg entries, and user profiles for google chrome. Then reinstall.
Try booting to Safe Mode with Networking and see if Chrome will launch there
Safe Mode
If it launches there, try a clean start to see if there is a conflict
Troubleshoot Application Conflicts by Performing a Clean Startup
I understand this happened after a Chrome update, but something is obviously amiss. Do you have a system restore point from before this began?
System Restore
A Guy
Sadly no restore point - well not from before this started happening anyways. This makes zero sense to me. Something is most certainly wrong here. Could there be some hidden leftover in the registry after uninstalling it? It must have corrupted itself after it updated but how can it still be corrupted if I uninstalled it and reinstalled with new installers?
I haven't tried running it in safe mode so I'll give that a shot in the morning. I have no idea what to try next after that.
I believe Barman described the issue very well here,
Chrome just updated and now all I get is "aw snap"
Possibly make a new administrator user account and test the issue ?
Cheers.
Quote