Unable to reproduce this issue on Windows 10 with chrome #62.0.3202.94 

Steps Followed:
1. Downloaded #62.0.3202.94 .msi installer
2. Launched the window terminal and navigated to downloaded package
3. Installed package with command "msiexec /i desktop-5c0tch%F62.0.3202.94%2Fwin64-pgo%2FGoogleChromeStandaloneEnterprise.msi NOGOOGLEUPDATEPING=1 /l*v log.txt"

Observations:
Installation was successful and didn't see any errors while installing the chrome msi


mjgrothoff@ Could you retry the same scenario and different machine and let us know your observations.

I tried the switch above on the msi indicated and msi threw back the error "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package." I didn't think it would work since there is no msi named with what you have placed in front of the msi. Ideas?

Thank you for providing more feedback. Adding requester "kkaluri@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

As per Google-Search the Error code: 0x80004002 is related to Windows machine, which can be caused by multiple reasons include:

1. Problems running programs that once worked
2. Slow response time of your computer to commands entered with the keyboard or mouse
3. Trouble shutting down or starting up your machine
4. Error message regarding your registry, updates, or response time.

Could someone from installation team look into this issue and update accordingly 

Re comment 2: please use the path to the Chrome .msi you are using. For example:

msiexec /i googlechromestandaloneenterprise64.msi /l*vx log.txt

I am already using this command to install 62 and getting the error. Need some direction on how to move forward. Need to update machines but cannot if when I remove a previous version I cannot install the new version because of this ridiculous error. Need some tech help...please. 

Hi. Could you please attach the log.txt file generated from that command? It might have some useful info.

+ganesh to comment on possible sources of the Egads! errors.

Attached is the GoogleUpdate. ini file. Let me know if you need the msi file. 

Deleted: omaha_review.log 18.0 KB

omaha_review.log 18.0 KB View Download

Thank you for the log. I see:

[11/21/17 09:36:26.168][GoogleUpdate:goopdate][6108:10880][Failed to install apps][0x80004002][Egads! Installation failed. Error code: 0x80004002.]

0x80004002 is E_NOINTERFACE. The "Egads!" message is IDS_SETUP_FAILED and is probably being logged here: https://github.com/google/omaha/blob/master/omaha/client/install_apps.cc#L457.

It looks like Google Update in the installer is trying to handoff to the one installed in C:\Program Files (x86)\Google\Update\GoogleUpdate.exe. My guess is that the COM registrations for the one there have been deleted.

Try this from an elevated cmd prompt to have the installed Google Update re-register itself:

"C:\Program Files (x86)\Google\Update\1.3.30.3\GoogleUpdate.exe" /regserver

Then try the MSI again.

I will try this re-register but this directory does not exist so I have a feeling I know what will happen. 

The directory you mention only gets created during the install and when this fails, during the backout, it removes this directory and only leaves behind an empty directory called  C:\Program Files (x86)\Google\CrashReport

I do a complete cleanup and remove the Google directory, so it does not exist anymore. Plus when you uninstall the previous Chrome version, the Google directory is deleted so it does not exist during this process also. 

Is there a way to get the msi to run the re-register when it creates the directory?

Thank you for providing more feedback. Adding requester "grt@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

Ganesh: would you please take a look at this? It looks like I was mistaken in thinking that there was a partial registration of Google Update on the machine. Thakns.

Update to the regserver switch. 

I ran the msi and during the install, I was able to grab the Update folder and copy it off. The install failed, of course, then I copied the Update folder to the Google dir and ran /regserver successfully. I then deleted the google folder and registry keys pertaining to GoogleUpdate and ran the msi again with the switches and it failed. 

I captured another GoogleUpdate.ini log and attached it. Please let me know what the next technical move is to get this installed. 

Deleted: omaha_after_regserver.log 17.9 KB

omaha_after_regserver.log 17.9 KB View Download

I think this is what is happening: for some reason the proxy/stub is not getting registered. In addition to that, due to a possible race condition, the service is not shutting down fast enough for a fallback local instance to instantiate and install Chrome. 

Is this happening on multiple machines? Or just on one specific machine? 

It is a sporadic issue, but yes it happens on multiple machines. In some cases, if we try again it installs, but in some cases we cannot get it to work at all. It is hit and miss. 

When we get it to work, I delete the leftover Google folder and then the registry left behind under HKLM\Software\WOW6432Node and it installs on the 2nd try. 

We will see if we can fix this with the next release of Google Update. 

Could you please try this, as an experiment? Under:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\UpdateDev

create a new DWORD value UseInProcCOMServer and set it to 1. Then try the install. My expectation is that this should succeed 100%. 

So I went in and deleted the leftover directory and leftover keys then added this key and still received this error. Should I leave the leftovers in place and add this key?

Hmm, this could be a different issue than what I described above in comment 14. Could you please confirm that you got the same error code, 0x80004002? The machines are Windows 10 64-bit, correct?

No, this is a Windows 7 SP2 64 bit machine(s)

Is there a way I can open a case where I pay for support to have this fixed? This issue is just not happening on version 62 but other chrome versions and we need to be able to role this out to a large audience. 

Could you please download the following and see if you can repro the issue? This is a debug build of Google Update that will give us much better logging and may help pinpoint what is going wrong with your setup:

https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7BD1358532-CBB9-B48E-9BBE-DB16A7E42652%7D%26lang%3Den%26browser%3D4%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers%26ap%3Dx64-stable-statsdef_1%26installdataindex%3Ddefaultbrowser/update2/installers/dbg/GoogleUpdateSetup.exe

To get verbose logging, please create a text file called C:\GoogleUpdate.ini (please save the file on the root of the C Drive). With the following content:  
     [LoggingLevel] 
     LC_UTIL=6 
     LC_SERVICE=6 
     LC_CORE=6 
     LC_NET=6 
     LC_OPT=6 
     [LoggingSettings] 
     EnableLogging=1 
     ShowTime=1 
     LogToFile=1 
     AppendToFile=1 
     LogToStdOut=1 
     LogToOutputDebug=1 
     LogFilePath=GoogleUpdate.log 

You should see a log file created in C:\ProgramData\Google\Update\Log\GoogleUpdate.log with details about the install attempts. 

Thank you!

I ran this update on a machine we have been unable to get chrome installed and it installed it. I enclosed the log to take a look but I did notice during the install it went to the internet to pull down most of the installation. I will need a version which does not do this and is self contained. Also one that does not force the Default Browser switch. We turn this off via GPO but still need a clean install. Thanks Marty

Deleted: GoogleUpdate_reviewed.log 3.7 MB

GoogleUpdate_reviewed.log 3.7 MB View Download

Hi Marty, this issue should manifest on the online version as well, it may take a few tries/machines to repro. We do not currently have a self-contained dbg version. 

Here is the URL that turns off default browser:

https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7BD1358532-CBB9-B48E-9BBE-DB16A7E42652%7D%26lang%3Den%26browser%3D4%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers%26ap%3Dx64-stable-statsdef_1/update2/installers/dbg/GoogleUpdateSetup.exe

I will try to make the problem occur, but so far each machine where we could not get the msi installed, this setup installs without issue. 

I do have another request, I need to speak to someone about setting up paid business support for chrome, who do I talk to about it?  

mjgrothoff@gmail.com

Can you fill out the form here (https://enterprise.google.com/chrome/contact/) with an interest in "Chrome Browser Enterprise Support" and you will be contacted about business support for Chrome.

Quick update, I am still not able to reproduce the issue with this new bugger tool but still trying.

Question, what is the turn around normally when you fill out the form for enterprise support? We filled out the form last week and no one has yet to reach out to us about it.

mjgrothoff@gmail.com

I apologize for the delay, someone from customer outreach team will contact you shortly.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.