MSI Installation Failure (error 1722)
Reported by
tristanp...@gmail.com,
Sep 15 2017
|
||||
Issue descriptionChrome Version: 61.0.3163.79 (32-bit) and 61.0.3163.91 (32-bit) OS Version: Windows 10 (x64) and Windows 7 (x64) Other browsers tested: N/A What steps will reproduce the problem? 1. Attempting to install either the 61.0.3163.79 or 61.0.3163.91 MSI (32-bit) results in failure (error 1722) on any Windows 10 and Windows 7 machines in my organization/environment. What is the expected result? I expect these MSIs to install successfully as previous versions have. What happens instead of that? The MSIs fail and pop-up the following error: "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." This MSI failure also ends up deleting the HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall Chrome key, which causes issues with any existing Chrome installation. Please provide any additional information below. Attach a screenshot if possible. Last month, I deployed 60.0.3112.101 (32-bit) to my organization, and it worked just fine. In the past, I've never had an issue deploying Chrome. I do so once per month. However, a few days ago, I started testing 61.0.3163.79, but I get the error/issue described above on every Windows 10 and Windows 7 machine that I've tried. I also started testing the 61.0.3163.91 MSI (32-bit) this morning, and, unfortunately, I'm getting the same results. I've attached the both the MSI log and the Event Viewer Application log for this failure. For what it's worth, I'm able to reinstall 60.0.3112.101 on my machines, and it corrects any registry/Chrome issues. UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
,
Sep 15 2017
Tried on two different machines and was successfully able to install Chrome MSI without any errors. tristanpinkham@ by any chance do you have GPO policy set, I suspect which might be causing the failure, if not can you please provide chrome_installer.log which should be stored in C:\Windows\Temp or in %TEMP%.
,
Sep 18 2017
Hi. Would you please collect a log from msiexec.exe with the following: msiexec.exe /l*xv msilog.txt /i GoogleChromeStandaloneEnterprise.msi and submit both that log and any log found at C:\Windows\Temp\chrome_installer.log? Thank you.
,
Sep 18 2017
Good morning. We just determined that the MSI failure was actually caused by some of our anti-intrusion software (Cylance). We didn't suspect Cylance at first because older Chrome MSIs were working correctly. Anyway, thank you for taking the time to help. This ticket can be closed.
,
Sep 18 2017
Thank you for providing more feedback. Adding requester "pbommana@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 19 2017
As per comment #4, closing the issue as wontFix. Thanks...!!
,
Sep 19 2017
Great! Sorry I missed that you'd already attached the logs. :-| |
||||
►
Sign in to add a comment |
||||
Comment 1 by gov...@chromium.org
, Sep 15 2017Components: Internals>Installer
Labels: Needs-Triage-M61 M-61