Chrome is failing to fully update
Reported by
deflorvi...@gmail.com,
Apr 1 2016
|
||||||||||||||
Issue descriptionVersion of Google Chrome (Wrench-> About Google Chrome):49.0.2623.110 m & 49.0.2623.87 m Version of MSI (if applicable): Using group policy settings? No Chrome is failing to fully update it seems. The enterprise users are left with new_chrome.exe and old_Chrome.exe on their computers, and the shortcuts on the desktop and elsewhere are broken. One fix we have found is renaming new_chrome.exe to just chrome.exe and creating a new shortcut.This has happened to close to 100 users and has happened three times over the past two weeks. It initially happened around 3/14 and 3/15 and again on 3/30 and 3/31. Has anyone else reported this issue? It's bringing lots of help tickets into the system and we have yet to find the root cause.
,
Apr 4 2016
Saswat/David/Royans - have we heard other reports of this?
,
Apr 4 2016
+Brian +Greg. Not sure if this relates to the last MSI updates.
,
Apr 4 2016
Could you check for C:\Windows\Temp\chrome_installer.log and attach it? I will try to repro this in the meantime.
,
Apr 4 2016
I'm so far unable to reproduce this by installing 49.0.2623.87 from the .msi and then updating it with the 49.0.2623.110 .msi while Chrome was running. Is there anything else about the impacted machines you can share?
,
Apr 4 2016
Attached is the log from the machine in the screenshot. There really is nothing else to share that comes to mind. It's happening with different models, and is happening at locations from Beverly Hills, to Nashville, NYC, London and Sydney. Initially we thought it might be related to SCCM, but upon checking with the person who manages that, he has told me there are no Google Chrome policies being pushed out.
,
Apr 4 2016
Looks like the attachment didn't make it through. Could you send it directly to me: grt at chromium dot org. Thanks.
,
Apr 4 2016
One thing to note is that we do forced nightly reboots of the users' computers. I'm not sure if this plays into it at all since this is a new corporate issue, but I thought it was worth mentioning to you.
,
Apr 4 2016
Thanks for the log. It appears that the impacted machine received Chrome 49 on March 14. I surmise that Chrome was in-use when this happened, and that chrome.exe was already missing when Chrome was shut down. There's no hint there as to how chrome.exe disappeared, though. I'll continue digging to see what I can find. Are these machines being updated by Google Update, or do you manually push out new Google Chrome .MSIs periodically?
,
Apr 4 2016
They're being updated via Google Update.
,
Apr 6 2016
This sounds very similar to issue 596636 , for which a fix shipped in today's Canary. I still haven't been able to repro, and the log I looked at doesn't contain enough detail to know what's going on. If you're able to reproduce this happening on a machine, a ProcMon log should tell all. It could be that the Chrome in-use update succeeds, but that chrome.exe is being lost when Chrome is shut down.
,
Apr 12 2016
Hey everyone this happened yet again to numerous people at our company. We really need to get this figured out. I'm attaching a couple more images, but there are no chrome installer logs in the temp folder for whatever reason. Any updates on your end?
,
Apr 12 2016
I've landed a change in Chrome 50 that I hope will prevent this from happening in the future. Please check for chrome_installer.log in C:\Windows\Temp (IFasst Temp Folder.JPG appears to be C:\Temp). If you are able, I believe that pushing the latest .msi to these machines will recover them.
,
Apr 12 2016
Here are the logs
,
Apr 13 2016
What is the estimate release date from Chrome 50?
,
Apr 13 2016
I too am seeing this issue for about 30% of my users for every update since 49.0.2623.95 I did file a bug on that one. Additionally, I am able to update CHROME but UNABLE to INSTALL Chrome using the latest googleenterprisesetup.msi update 49.0.2623.112 and the previous one 49.0.2623.110( i have not checked any others since 47.0.2526.80 which works)
,
Apr 13 2016
Chrome 50 was just released on the stable channel: http://googlechromereleases.blogspot.ca/2016/04/stable-channel-update_13.html. Please give it a try. In case of failure, please provide the log from C:\Windows\Temp\chrome_installer.log. Thanks.
,
Apr 14 2016
Same issue with install with ver 50 install log attached
,
Apr 14 2016
rw: Are you able to reproduce this reliably? What are your steps to repro? Could you please attach C:\Windows\Temp\chrome_installer.log? Are you willing/able to capture a trace with Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) of the operation that results in chrome.exe going missing? Thanks for your help in tracking this down.
,
Apr 14 2016
The chrome.exe being gone and new_chrome.exe in its place issue occurs randomly in 25 - 35 % of my 14,600 chrome users. It began happening with 49.0.2623.95 and continued throu 49.0.2623.112. I do not know if is happeing with v 50 yet. I have been proactively fixing once i saw it starting to occur by pushing out a sccm task sequence to force the update (by running the updated enterprise msi) and then ensuring the exe was named correctly.
,
Apr 14 2016
The second issue i referenced here ( I can open a seperate incident on it if you like) is inability to actually perform an install of chrome on a device that has no chrome on it already with the last few version of the published enterprise msi. This continues to occur with the stable update 50.0.2661.75 I can upgrade an existing install but not install on a clean build. I can install v 47 and then run the upgrade (which i have in place for a temporary workaround) the two logs i attached with comment 19 show that. the install failure and the successful update.
,
Apr 14 2016
For the second issue, could you attach C:\Windows\Temp\chrome_installer.log? This should have more useful info than the log from msiexec. Thanks.
,
Apr 14 2016
As mentioned in comment 20, it would be extremely helpful if you could capture a trace with ProcMon. For the life of me, I can't get the .msi to fail to install or update on any machine I've tried. Thanks for your help in tracking this down.
,
Apr 14 2016
When i try to install the latest googlechromestandaloneenterprise.msi by doubleclicking the msi... I get the attached error and no log is generated in c:\windows\temp or %temp%. If I pass parameters to the msi to gen a log it generates what is attached with comment 19. I downloaded the file multiple times from https://www.google.com/work/chrome/browser/thankyou.html?platform=win&msi=true If I install v47 first and then install it updates fine. Im wondering if we are using different msi's... I will try to capture a procmon trace and upload it and then will install 47 and then 50 to get the installer log
,
Apr 14 2016
procmon trace (filtered on msiexec for size)
,
Apr 15 2016
,
Apr 15 2016
Thanks very much for the procmon trace. Unfortunately, the failure isn't in msiexec, but in one of the child processes. Since installing M50 when M47 is already there works, I'm going to take a wild guess and say that perhaps the error is in Google Update's new install path. Could you follow the instructions here: https://support.google.com/chrome/contact/unknown_error to capture a verbose log from Google Update? When you get to the "Configure Providers" step, please set both "Omaha" and "Chrome Setup" to "Verbose." If you try again with the procmon log, please include all processes created by msiexec. If you search for "Process Create" events, you can see the child PID. For example, you'll find in the log you provided that msiexec wrote some payload to disk in the file C:\WINDOWS\Installer\MSI8AA2.tmp and then executed that with a bunch of command-line args. That should have eventually run Chrome's installer. Since you say this step didn't produce a chrome_installer.log, I'm guessing that the failure occurred before Google Update got to that step.
,
Apr 15 2016
captured msiexec with procmon again. had to use 7zip ultra compression to make small enough to attach here
,
Apr 18 2016
rw: Thanks for the log. I've opened issue 604386 for the "can't install on a clean machine" failure. Please continue the discussion for that particular failure on that issue, and let's keep this one open for the "chrome.exe disappears after an update" problem. Thanks.
,
Apr 18 2016
will do thanks
,
Apr 21 2016
OP and rw: Has Chrome 50 resolved the "chrome.exe missing after update" problem for you? If you're able to reproduce this at-will, I would appreciate your help in diagnosing it further. If you have some sort of security or anti-virus software on your fleet, could you check to see if chrome.exe is being quarantined?
,
Apr 21 2016
Chrome 50 appears to have resolved the chrome missing after update problem as i have had no reported issues of this issue since it was released to the stable channel. I got many reports of this issue with each of the last several updates prior to 50.
,
Apr 21 2016
Thank you for the confirmation. I will keep this issue open a bit longer to be safe. Also, FYI, Sawbuck is now available for download at https://github.com/google/sawbuck/releases/latest. I am in the process of having the link in our help center article updated. I apologize for the inconvenience.
,
May 5 2016
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by deflorvi...@gmail.com
, Apr 1 201655.1 KB
55.1 KB View Download