I have 32bit and 64bit at work and upgrade to version 37 brings the same error.Glad others out there know where to look to fix this. Thanks all.Could someone with the problem (And on 64-bit Chrome 39 dev or canary) please attach a net-internals dump of this happening.If there is a fix, Google should update their software rather than rely on the user community to find it in a board like this.Uninstalling and reinstalling Chrome has not helped in my case.
Note: Past private message conversations will not move to the new site design.So, this could explain the blacklist being enabled even after changing channels.And, when reverting to 32-bit, they might still block them because why not.
No clue what happened but my chrome quit working two days ago as well.After a tiny hiccup (old non-responsive screen displayed) I was prompted to sign in to Chrome - everything back to normal for 8 hours.I then uninstalled with the intention of rebooting and trying a fresh download.
Removed Chromium and installed Chrome 39.0.2171.71, the issue remains unchanged.I have been having the same problem as everyone else here, tried the same long list of fixes.It could also be some other setup-specific thing triggering this.I started using Chrome when it was first released because I needed a fast, simple, easy to use browser.When i try to open a web address, chrome give a an error stating that the it cannot connect to the internet.Same issue under Win64 with DNS resolves up to 90 seconds but averaging around 15 seconds to resolve.
There will be probably a lot of DLLS, check if any of them appear listed inside this file.What is the exact error message that you get when you try to open Google Chrome and Internet. CCM.Have created a new user profile and have disabled hardware acceleration.The security softwares I am using there: Microsoft EMET, Microsoft Security Essentials, Windows Defender and the Windows Firewall.