Issue metadata
Sign in to add a comment
|
Relaunch of Chrome only happening via Settings and About
Reported by
dmccullo...@broomfield.org,
Nov 4 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Steps to reproduce the problem: 1. Chrome is not auto updating 2. When looking in help and about it updates 3. Only option is to click on Relaunch What is the expected behavior? I would think a reboot of the PC would at least finish the Chrome update and would relaunch with the newest version. It is not. Every PC in my org is doing this. What went wrong? Our Policy is set to get updates from Google on all Chrome browser but with out click on the Relaunch from help/about it will remain on the old version of Chrome until active click on relaunch. Did this work before? N/A Chrome version: 54.0.2840.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 I have scoured the internet with no way of remotely relaunching the browser or forcing a policy to force relaunch to newest version of Chrome.
,
Nov 9 2016
Hi. You're correct in thinking that a machine reboot (or user logoff/logon) should be enough to cause a pending update to be picked up. We'll need to do a little investigation to understand why updates aren't being applied properly on your machines. Could you attach C:\Windows\Temp\chrome_installer.log and %TEMP%\chrome_installer.log from an affected machine?
,
Nov 9 2016
This sounds like it could be http://crbug.com/606301 . Feel free to undupe if that is not actually the case.
,
Nov 10 2016
If the problem is "chrome://help fetches an update that the machines haven't already automatically received", then this is a dup. Thanks. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sureshkumari@chromium.org
, Nov 8 2016Components: Internals>Installer
Status: Untriaged (was: Unconfirmed)