Issue metadata
Sign in to add a comment
|
Uninstall does not work for any 64-bit MSI installer after adding -arch switch to candle.exe
Reported by
asot...@gmail.com,
Nov 10 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Steps to reproduce the problem: 1. Install Google Chrome 64-Bit MSI installer on 64-Bit Endpoint 2. Navigate to "Programs and Features" 3. Select Google Chrome and Uninstall What is the expected behavior? You get a return message stating: "There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor." What went wrong? It fails in the Uninstallation process and does not end up removing chrome. Leaves all of its components on the endpoint so that there is no way to be able to remove that version of chrome. Did this work before? Yes 54.0.2840.87 Chrome version: 54.0.2840.99 Channel: stable OS Version: 7.0 Flash Version:
,
Nov 10 2016
Hello, Wanted to let you know that I'm seeing this too. I just mistakenly submitted a duplicate issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=664266 We're sticking with the previous release for now, hopefully this issue doesn't prevent newer versions from installing over-top of the .99 release!
,
Nov 10 2016
Also got the same thing in our environment with 54.0.2840.99. 54.0.2840.59 worked fine.
,
Nov 10 2016
Issue 664266 has been merged into this issue.
,
Nov 10 2016
I am also able to reproduce this issue in latest chrome version-54.0.2840.99 1. Downloaded and installed chrome from : https://enterprise.google.com/chrome/chrome-browser/ 2 Launched successfully. 3. Exited 4 Tried uninstalling from control panel. Observed: Was not able to uninstall, see the attachment. We encountered similar problem in canary, Issue 663703 , hence looping to grt@
,
Nov 10 2016
This is latest regression since this is working fine with previous Chrome Stable i.e., 54.0.2840.87. Change log : https://chromium.googlesource.com/chromium/src/+log/54.0.2840.87..54.0.2840.99?pretty=fuller&n=10000 I don't see any suspected cl which would have caused this and the behavior is similar across all Windows versions i.e., Windows 7, 10.
,
Nov 10 2016
Micheal, are you aware of any packaging change on Windows?The bug is reported only in latest stable - 54.0.2840.99.
,
Nov 10 2016
The only recent change I can think of was the fix for Issue 658728 , but that landed Oct 26, which was before 54.0.2840.87 on Oct 31, so if it was a problem, I suspect it would have have broken that release too.
,
Nov 10 2016
Also the Issue 658728 change would apply to all channels. Are we seeing uninstall problems in any other versions?
,
Nov 10 2016
From the testing that i have done on all of your recent releases, this is the first time that uninstall has failed.
,
Nov 10 2016
I am seeing similar error with latest Chrome Beta MSI i.e., 55.0.2883.44 as well.
,
Nov 10 2016
,
Nov 10 2016
What about dev? That might help narrowing down exactly when it broke.
,
Nov 11 2016
Chrome 64bit MSI is failing on all Chrome channels i.e., Stable(54.0.2840.99), Beta(55.0.2883.44) and Dev( 56.0.2914.3), Where in Chrome 32bit msi I am able to uninstall correctly. Note : There is no way we can uninstall Chrome in this case i.e., from Control panel or CMD line, Since all Chrome versions has this error there is no way we can uninstall this from machines until we fix the issue.
,
Nov 11 2016
Ugh, I forgot that my change for Issue 658728 wasn't the last change there, so it didn't actually go into effect until grt made another fix in cl/138164721, which was on 11/4. I now strongly suspect that is the problem, though I have no idea why. I can revert that change, which should unbreak this issue, but will break Issue 658728 again.
,
Nov 11 2016
,
Nov 11 2016
,
Nov 11 2016
This shouldn't have any impact on future updates based on my testing(grt@ please correct me if I was wrong).
,
Nov 11 2016
,
Nov 11 2016
I see the problem. We need to revert the -arch x64 change for now until we can fix things.
,
Nov 11 2016
I believe that running a fixed MSI without first attempting to uninstall the broken one will succeed and repair the state of the world so that uninstall will once again work. We'll update this issue as we have new info.
,
Nov 11 2016
Can someone confirm whether this issue is a blocker for Stable AU which is scheduled today(11/11)?
,
Nov 11 2016
AFAIK this wouldn't block our regular updates, Greg please correct me if I am wrong.
,
Nov 14 2016
**** Bulk edit - please ignore if not applicable **** A friendly reminder that M55 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you! Also due to Thanksgiving holidays in US, please make sure fix is ready and merged to M55 latest by 5:00 PM PT Friday, 11/18/16 (sooner the better).
,
Nov 14 2016
Regular (non-MSI) installs are unaffected.
,
Nov 16 2016
grt@, could you please provide an update here as we're getting close to M55 Stable launch?
,
Nov 17 2016
We've backed off the change that caused this. All currently-building MSIs should be good (although they still look like 32-bit installers as before). I will mark this as fixed since I don't think there's anything that needs to be done before M55 hits stable.
,
Nov 17 2016
[Auto-generated comment by a script] We noticed that this issue is targeted for M-55; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-55 label, otherwise remove Merge-TBD label. Thanks.
,
Nov 17 2016
Checked the issue on Latest Beta# 55.0.2883.52 on Windows 7 / 8.1 & 10 and below are the observations -- Observation 1: (i) Installed Google Chrome 64-Bit MSI installer and was able to install successfully. (ii) Un-installed from Control panel and was able to uninstall successfully. Observation 2: (i) Installed Google Chrome 64-Bit MSI installer and was able to install successfully. (ii) Un-installed from Registry Editor and was able to uninstall partially. Chrome was removed from Desktop but Chrome was still seen in Control Panel. Have to remove Google Chrome from control panel by deleting manually. Note: Same behavior is seen from Chrome 32-Bit MSI Installer. Please let me know if any more information is required. Thank You.
,
Nov 17 2016
By "Un-installed from Registry Editor", do you mean that you manually ran Chrome's setup.exe with --uninstall (and other arguments)? This is expected to leave behind the control panel item since it bypasses Windows Installer. If that's it, then I think we're in good shape. Thanks for the confirmation.
,
Nov 17 2016
@grt -- Yes, that was what i meant. Google Chrome is left behind in Control Panel when uninstalled from Registry Editor using the arguments. Please let me know if any more information is required. Thank You.
,
Nov 17 2016
,
Nov 28 2016
Issue 669111 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by asot...@gmail.com
, Nov 10 201644.8 KB
44.8 KB View Download