There was a post in the UPDATES thread for a new Chrome and the stable releases page also says it has been released. However, my Chrome will not update and says that the previous version number is the latest one. Chrome is also now VERY slow from a cold start to my homepage.
… I saw the post in the update section, then I checked, and the exact version number suggested in the post was immediately offered … and it worked. There’s some latency sometimes with Google servers, may be it’s just that in your case.
ps: just for info http://googlechromereleases.blogspot.com/2012/03/chrome-stable-update.html
I click on the “About Google Chrome” and it comes up with the .56 version, says “Checking for updates”, and after a few seconds says I have the latest version and gives the .56 one. The new one is supposed to be .65 according to the stable thread from Google.
Same here… I’m waiting to see chrome will detect the new update later on today or not. 8)
No problem updating my Google Chrome to 17.0.963.65
I tried going to google.com/chrome and installing the new version from the installer… but it didn’t help… the installer closed and opened the version on my computer and what would you guess? the old version still on my computer… (This sort of made me laugh )
Many hours later and it still won’t update.
I’m still new to google chrome so I am a bit confused on how it updates…
It either does it automatically if you have it enabled to do so. It enables that function by default. Or you can click on the wrench icon and then on About Google Chrome. It will then search for updates and , until this time, download and apply them. Maybe this is another effect of the Chrome problems others have experienced when updating to Avast 7. Chrome is not my default browser, IE9 is and I only use Chrome once in a blue moon. It should still work though.
Yes. That’s the release page I referred to and the one I checked to make sure there actually was an update. I can’t get it though.
I think you should uninstall Chrome (careful not to delete your profile, ie the User Data folder), and do a re-install from the web.
Okay, I just uninstalled Chrome and did the download and reinstall. It still is at the same version and will not update.
then there are issues on Google servers, you should report this with a comment on their blog page:
same link again http://googlechromereleases.blogspot.com/2012/03/chrome-stable-update.html
this sort of issue has happened already in the past with Chrome.
edit: read the comments already posted, many people have the same issue
Mine just updated - but to 17.0.963.66.
Perhaps there was an issue with 17.0.963.65?
Yes–I disabled AIS completely and Chrome updated without a hitch. I was about to post that the issue was with avast! but then I checked the Google blogspot site again and it said they had suspended the 17.0.963.65 update because of a “minor” issue and would have a new version shortly. I checked my version and it’s 17.0.963.66 so now I don’t know if the problem was with avast or just a coincidence that they pushed out the newer version at the same time I decided to try it with AIS disabled.
That’s about as clear as mud to me and doesn’t say anything about the updating problems so now I still don’t know if avast was preventing it or not. I strongly suspect that it was.
come on that all happened on Google side … they probably retained an update shortly after releasing it, due to a technical issue … now it’s solved and everyone can update to the new version, no big deal, and nothing to do with AIS. Again, read comments from others on Google blog, they experienced the same issue as yours.
I just got on my computer and I opened chrome and went to the about chrome thing. and it installed the new version.
come on that all happened on Google side … they probably retained an update shortly after releasing it, due to a technical issue … now it’s solved and everyone can update to the new version, no big deal, and nothing to do with AIS. Again, read comments from others on Google blog, they experienced the same issue as yours.
+1
Edit: I just noticed something the update we was talking about was something .65 but the updated version i have says .66