Updating issue (Relaunch but never update)
Reported by
pakitsup...@basecampdata.com,
Sep 25 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Open About Google Chrome page 2. If there are updates, wait for them to finish 3. Click on "Nearly up-to-date! Relaunch Google Chrome to finish updating." button What is the expected behavior? When the "Nearly up-to-date! Relaunch Google Chrome to finish updating." button is clicked, Google Chrome should restart and the page should show "Google chrome is up to date" What went wrong? When the "Nearly up-to-date! Relaunch Google Chrome to finish updating." button is clicked, Google Chrome will restart, but the message does not go away, even if I restart multiple times Did this work before? N/A Chrome version: 59.0.3071.115 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I have tried restarting about a dozen times. - I have tried uninstalling and reinstalling Google Chrome. The issue occurs every time when an update is available. - The issue does not occur on any other machines I use. - Windows 7 64 bit. Solid state drive.
,
Sep 26 2017
,
Sep 26 2017
Unable to reproduce this issue on reported version 59.0.3071.115 , latest stable 61.0.3163.100 and on latest canary 63.0.3223.8 using Window 7 and is not reproducible with steps mentioned below. Installed 59.0.3071.115 and waited for updates and clicked on "Nearly up-to-date! Relaunch Google Chrome to finish updating." button and observed successful upgradation of chrome. @Reporter: Could you please check this issue by uninstalling current Chrome and installing latest Chrome Stable or Canary. Please navigate to below link to download the latest Chrome Builds https://www.chromium.org/getting-involved/dev-channel.
,
Sep 26 2017
Greg, any ideas about debugging the installer? My first thought was that Chrome didn't fully exit (running a background process, etc) so the handover could not complete, but the report states that they tried restarting the computer, which would certainly result in a fresh start of Chrome.
,
Sep 27 2017
Hi. Could you confirm that chrome://version shows that Chrome is installed in C:\Program Files (x86)\Google\Chrome (look for the "Executable Path" row)? In this case, Chrome asks Google Update (via COM) to run the command to complete the update. Perhaps Google Update has been disabled on your computer. Joshua: is it worth checking the COM registration of the GU components?
,
Sep 27 2017
I assumed because the client discovers the update, and ultimately makes it to the "restart to update" state, it must be able to communicate to Omaha and successfully run the update installer, but I admit I don't know the details of how that works.
,
Oct 8 2017
"Nearly up to date" could mean that a new_chrome.exe is present on disk from an in-use update initiated by GU's scheduled task. Is it possible that the task would run, but that the ProcessLauncherClass is broken?
,
May 17 2018
Unable to reproduce this issue reported version 59.0.3071.115 and latest stable on windows 10. @Reporter:Does this repro for you in latest build as well? If not please check the issue on latest build and report us back the behavior. You can download latest build from https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Nov 9
As there is no update from the reporter since a long time, marking this issue as WontFix. Please feel free to raise a new bug if any issues are observed on the latest Chrome builds. Thanks.. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by manoranj...@chromium.org
, Sep 25 2017