Again the same problem! Update is not working...Windows 7, 64 bit
Automatic update not working! Win 8.1/x64. :-(
Automatic update is not working on my windows 8.1 64 bit computer and my windows 7 32 bit computer.
I appreciate the need for security updates but 5 updates in 3 weeks - this is not a "stable" channel. Put more effort into making the software correct in the first place, and less into fixing problems after the fact. I for one am considering a change away from Chrome.
no problem with automatic update. win7 / 64bit.
Win7 x64, Chrome told me there is an update, downloaded something and told me it needed to restart. After restart I'm still on .107 and there's no more update waiting.
Thank yous for the updates, but I have a request: would yous consider making a "Business Stable" channel, like how Firefox has "Stable ESR", because the constant updates to the Stable channel is too much. Please at least consider this!
Blogger Frank Rehse said...Win7 x64, Chrome told me there is an update, downloaded something and told me it needed to restart. After restart I'm still on .107 and there's no more update waiting.4:37 PM, July 28, 2015Same here - Win7 x64, Chrome Version 44.0.2403.107 m
Automatic update not working on Mac OSX 10.10.4 (Yosemite). Has been throwing "Update failed (error: 12)". Tried the workaround mentioned in Google Help when faced with that error ( rm -rf com.google.__Keystone.Agent/ etc. but to no avail). The error seems to be back every time it is time to upgrade. I am working around this by tracking the stable channel release posts and downloading the installer every time. Sad!
"Updated" then went back to .107 with no update waiting... Windows 8.1 64 bit
I have not received this update until now.
"DrPixie said...I appreciate the need for security updates but 5 updates in 3 weeks - this is not a "stable" channel. Put more effort into making the software correct in the first place, and less into fixing problems after the fact. I for one am considering a change away from Chrome.3:33 PM, July 28, 2015"Ehm. Ok. Actually, fixing bugs _makes_ software stable, so if you're against fixing them so much that you actually want to change to another software, then good riddance.Don't think your "I'm going to have to go away" makes a single dev lift a finger over your concerns.
No problem updating win7 x32.
Update: The fix is to completely remove then reinstall google chrome. I see the correct version with (64 bit) listed after... Annoying but a fix
Every time there is an update I have to do it manually. Shouldn't a big company like Google fix this issue right out of the box as tons of people seems to be complaining. I really can't understand that.
I am facing the same problem as those above:download something and restart, but after that the version number is the same
For as many fixes as you have done for this build and still not listening to the users, I think it is time for you, Google, to finally listen to your user base. But this will never happen and so I am now finally bidding adieu to Chrome for good.
Automatic update worked fine for me on Win 7 Pro 64-bit.On the other hand, release 44 has brought so many "He's Dead Jim" crashes that Chrome is practically unusable. My PC is a Core i7-4770 with 32 GB of RAM.
Same problem as the earlier V44 releases - .125 is still ignoring the registry key which should disable auto-updates.
Google update fixed nothing. Instead, the new update has made the situation from last week's update -- slow browser, ERR TIME OUT, etc. (see product forum) -- WORSE. If I let the browser sit untouched for any period of time, or I try to use more than three tabs, I have to close everything, re-clear the cache (even if I just cleared it) and then re-open the browser to get it to work and not give me an ERR TIME OUT message. Two of the open web pages in the three tabs also turn white after they've loaded and then the pages are very slow to reappear (I had to learn the hard way not to re-load the page and just wait for Chrome to show it). Please. PLEASE. Give us back Chrome v43 until you fix the problem or, at least, stop with the repeated updates because all they do is interrupt when I'm trying to work. I've lost so much money in the last two weeks because you didn't test v44 enough before releasing to the masses.
Shockwave broken using Windows 10
Auto update loaded a new version on 7/29/15 which is very buggy - slow, Flash failures (with latest), and more than thirty chrome.exe processes going for three tabs (three gmail accounts), two plugins (Norton 360, adobe). App crashed repeatedly, restart wouldn't happen, had to use TM to end process and one (the largest in memory) would not respond to TM commands. Had to restart and then I used RevoUninstaller to remove all Chrome apps. Questioning whether to bother downloading the current build or to wait a week until the issues are dealt with. Any thoughts?
If Chrome is slow for you, check your antivirus program. The Chrome devs appear to have forgotten to take into account real-world use and functionality. I had to do the following to get the browser to speed up and stop freezing as much:Turn off the option to scan opening .exe files so that Chrome would load smoothly without delays.Turn off HTTPS scanning so that pages would load faster without freezing.After I shut those down, Chrome was a LOT better. The only problems that still exist for me: There is slight lag, but I think that's because Chrome appears to have a new memory leak issue (huge differences in CPU usage data between Chrome Task Manager and Windows Task Manager and the Chrome CPU usage increases just by having the browser open and not doing anything in it). Additionally, open tabs that had previously loaded pages are still turning white and then taking forever to show the loaded pages when I flip between them. Is anyone from Google going to answer the question about the update Registry shutoff option spoken about above. I want to shut off the updates, but it sounds like that option isn't working. Anyone?
Post a Comment