Issue metadata
Sign in to add a comment
|
Chrome not updating past version 51.0.2704.103
Reported by
john.b...@gmail.com,
Jul 4 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586 Steps to reproduce the problem: 1. Configure Google update GPO, setting chrome and chrome binaries to "Automatic silent updates only" 2. Install Chrome version 51.0.2704.63 via the 32bit MSI installer. 3a. Force the Google Chrome update scheduled task to run 3b. Wait for the Google Chrome update scheduled task to run 4. Chrome will update but will only update to version 51.0.2704.103 What is the expected behavior? I would expect chrome to update to the latest version of chrome currently available to the stable channel, version 51.0.2704.106 What went wrong? I believe the auto updater is failing to recognize the correct version of chrome to install Did this work before? Yes I would say it was working back in the 40.* versions of chrome Chrome version: 51.0.2704.103m Channel: stable OS Version: 6.1 Flash Version:
,
Jul 5 2016
,
Jul 5 2016
No
,
Jul 6 2016
Thank you for providing more feedback. Adding requester "dskaram@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 6 2016
,
Jul 6 2016
,
Jul 13 2016
Everything is working as expected. Your clients have not received the update because of internal deployment decisions. They will update in time. We are working on better ways to communicate things like this to enterprise users. Apologies for the confusion.
,
Aug 2 2016
We are now having the same issue with v 52 of google chrome ... is this still by design ? Why is the updating so slow for such a critical update ? Thanks John
,
Aug 2 2016
Hello GRT, what does "because of internal deployment decisions" actually mean? Is this why our workstations are slowly getting v52 as well ? Is there a document that explains these internal deployment decisions ? thanks John
,
Aug 3 2016
We've started a conversation internally to see how we can better communicate the release rollout process. I hear that things are confusing now when we announce a new stable release, yet it takes a long time for your machines to update to it. I hope we can do something better in the future. Thanks for your feedback.
,
Aug 5 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by john.b...@gmail.com
, Jul 4 201633.9 KB
33.9 KB View Download