Chrome not updating
Reported by
t...@anoebis.be,
Jul 27 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: Machine-installations of Chrome is not updating fast enough. Please look at issue 606301 and read all the comments after May 12th... What is the expected behavior? What went wrong? I still have version 51.0.2704.103 on my computer, which was released 40 days ago. After that, version 51.0.2704.106 was released (33 days ago), and 52.0.2743.82 too (6 days ago)... I understand that (and why) updates are rolled out gradually, but I believe that in a few days everyone should be updated to the latest version. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Jul 28 2016
We stay on stable-version 51.0.2704.103. OS Version 7x64 We found out, when we delete the regkeys under HKLM\Software\wow6432node\google\update\clientstate ... and HKLM\Software\wow6432node\google\update\clientstatemedium that then after a few hours within 1 Day automatically the update to 52.0.2743.82 was installed. But this is surely not the right way for an automatically Update.
,
Jul 28 2016
I have the same issue with the same version on Win7 x64. I created the GoogleUpdate.ini file to enable logging and every time the machine checks in, it is told "noupdate". Log entries & other relevant info here: https://groups.google.com/a/googleproductforums.com/d/msgid/chrome/66d5d435-a2cf-47fd-a97f-5f9ac861f332%40googleproductforums.com?utm_medium=email&utm_source=footer
,
Jul 28 2016
Here, a Chromium tech suggest that updating to .106 is not happening because of "internal deployment decisions", and that the clients will update in time. I believe that since v52 is out now, and includes an important security fix, that this should probably be auto-updating now. https://bugs.chromium.org/p/chromium/issues/detail?id=625669
,
Aug 10 2016
Most of our clients are now running 52.0.2743.116. It took about 3 weeks for Google Update to update most of our clients from a version that had "high risk" security flaws to one that didn't. We will be investigating alternate patching/deployment methods for Chrome within our organization.
,
Sep 30 2016
Currently stable version is 53.0.2785.143. wondering if still you are seeing this issue? Thank you.
,
Oct 3 2016
On my PC it's still version 53.0.2785.116. I don't know what kind of delay is used to release version .143, but I didn't receive it yet.
,
Oct 10 2016
Thank you for providing more feedback. Adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 10 2016
I am currently on 54.0.2840.71 (released 20 days ago). A stable version was released 8 days ago (54.0.2840.87), and earlier today (54.0.2840.99). Why am I still on the version from 3 weeks ago?? I think I'm not the only one who wants an explanation about these "internal deployment decisions"!
,
Nov 14 2016
georgesak@- Gentle Ping...!! Could you please have a look into this issue and help us in triaging further. Thanks...!!
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Mar 15 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tnagel@chromium.org
, Jul 27 2016Owner: georgesak@chromium.org