Issue metadata
Sign in to add a comment
|
Chrome x64 is not auto-updating post switch from x32
Reported by
r...@berkeley.edu,
Mar 28 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.108 Safari/537.36 Steps to reproduce the problem: 1. Install x32 version of Chrome 2. Install x64 version of Chrome 3. Post release of new update to x64 Chrome check status of silent / auto-update What is the expected behavior? Google Update should check for new version of Chrome every 5 hours and then auto-update when new version is available What went wrong? Chrome 49.0.2623.108 was released on Friday to the stable channel. Prior to that we switched from x32 version of 49.0.2623.87 to x64 by deploying the MSI for x64 using our systems management tool. Based on an analysis of systems most are still running 49.0.2623.87 (64) and very few have auto-updated to 49.0.2623.108 (64). Did this work before? Yes x32 versions have silently auto-updated Chrome version: 49.0.2623.108 x64 Channel: stable OS Version: Windows 7, Windows 8.1 Flash Version: Shockwave Flash 21.0 r0
,
Apr 28 2016
I am so far unable to reproduce this. Have your x64 machines updated yet? My guess is that you are witnessing the staged rollout of the update to 108.
,
Apr 28 2016
Thanks for reporting. I believe this was being caused by some update server misconfiguration, which I just fixed. Could you verify that your machines are updating to 49.0.2623.112 (over the course of the next five hours)? (Note that some of them may update to M50.)
,
Apr 28 2016
(oops, meant to say "fixed") |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by brajkumar@chromium.org
, Mar 29 2016