E_NOINTERFACE == 0x80004002. The log is not verbose unfortunately. rw, do you get a failure if you install from www.chrome.com? Thank you.

I am unable to install from Chrome.com either. (although that isn't really an option for my enterprise users)  I get the same egads error 0x80004002 and no log is generated.

is there a separate google update installer that I can try prior to installing the enterprise msi.  That would be a more preferred workaround than installing the v 47 enterprise msi then the current one (v50)

Any word on this?  Are you able to recreate?
Is there a google update installer?

bueler...

Hello, the one other thing that may get us some useful logs is to use the dbg installer from here:

https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7BD0A08BA6-2E11-5261-2A99-A9F14731BFF3%7D%26lang%3Den%26browser%3D4%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers/update2/installers/dbg/googleupdatesetup.exe

Please report back on what you get. Thank you.

[Egads! Installation failed. Error code: 0x80004002.]

C:\Program Files (x86)\Google\Update\GoogleUpdate.exe (pid=7440)
goopdate\worker.cc:243

!lock_count_

no logs generated that i can find.  If I choose abort instead of continue I get a second error but it is likely expected die to the first error.

It is listed below:

C:\Program Files (x86)\GUMCBBA.tmp\GoogleUpdate.exe (pid=7476)
client\install.cc:220

(((HRESULT)(exit_code)) < 0)

Could persons having this issue please update us with:

1) Windows version (Windows 7, 8.1, 10, Server 2008r2, etc)
2) 64-bit or 32-bit OS
3) 64-bit or 32-bit Chrome MSI

Unable to reproduce the issue with 49.0.2623.112 and clean install of Windows 2008r2.

Current MSI version being hosted is 50.0.2661.87. Can someone who has had this problem test with this new 50 build?

Systems affected (win7 32 bit, win7 64-bit )  Haven't tried any others as that is 98% of my environment.

32-bit chrome-msi. 

Same issue with latest googlechromestandaloneenterprise.msi

downloaded from https://www.google.com/work/chrome/browser/

version 50.0.2661.87

spoke too soon

still having same issue with VMware devices but physical devices seem ok with latest installer

Regarding comment 8, could you please create file c:\googleupdate.ini with these contents (on win7, run the editor as administrator):

[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=0
LogToOutputDebug=1
LogFilePath=GoogleUpdate.log
[DebugSettings]
SkipServerReport=1
NoSendDumpToServer=1
NoSendStackToServer=1


The debug log will be written here:

Windows 7, Windows 8: C:\ProgramData\Google\Update\Log

C:\Program Files (x86)\Google\Update\GoogleUpdate.exe (pid=3776)
goopdate\worker.cc:243

!lock_count_

Deleted: GoogleUpdate.log 314 KB

GoogleUpdate.log 314 KB View Download

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 install. 

We will attempt to fix this in the next release. Thank you.

[05/02/16 07:36:53.656][GoogleUpdate:goopdate][3776:8276][CoCreate GoogleUpdate3ServiceClass failed][0x80004002]
[05/02/16 07:36:53.656][GoogleUpdate:goopdate][3776:8276][CreateGoogleUpdate3LocalClass]
...
[05/02/16 07:36:53.657][GoogleUpdate:goopdate][3776:8276][Another Worker instance already running]
[05/02/16 07:36:53.657][GoogleUpdate:goopdate][3776:8276][InitializeWorker failed][0x80040707]

This bug should be fixed with the next release of Google Update which will ship in July or August.

What version is this expected to be fixed in? 

Do we have any firmer dates yet

GoogleUpdate version 1.3.31.5, shipping within the next 2 weeks.

Hi team, 

Is there any ETA of the new GoogleUpdate version?. We just confirmed that version 1.3.31.5 is not live yet.

Thanks for bringing that to our attention. It should be serving now (since 15:06 PDT).

I still do not see the updated version of google update  i see 1.3.30.3 being installed with the latest ver of chromestandaloneenterpriseinstaller.

I Still have to install v 47 first (which install chromeupdate 1.3.28.15) in order to install the latest chrome ver on a device.

I thought this was going to be resolved in the latest stable channel release.

Can I get a date when this will be resolved?

Michael, do the new binaries get automatically picked up for the chromestandaloneenterpriseinstaller? The Omaha team has checked in the 1.3.31.5 binaries into Perforce/Piper on Friday. Thanks.

Chrome uses the Omaha code on trunk, so yeah, it should pick it up automatically, but I don't think there has been a stable push since your changes on Friday. chrome-pmo@ should be able to tell you if they have one planned.