https://bugs.winehq.org/show_bug.cgi?id=25918
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://dl.google.com/updat | |e2/installers/ChromeStandal | |oneSetup.exe CC| |focht@gmx.net Summary|Google Chrome Standalone |Google Chrome Standalone |Installer fails, "Unknown |(offline) installer fails |Installer Error" |with "Unknown Installer | |Error"
--- Comment #14 from Anastasius Focht focht@gmx.net --- Hello folks,
adding info for documentation purpose.
In short: it's by design.
Untagged Google installers must be supplied command line arguments otherwise it's expected to fail with 'Unknown Installer Error' message (hr = GOOPDATE_E_UNTAGGED_METAINSTALLER).
See: https://code.google.com/p/omaha/source/browse/trunk/mi_exe_stub/mi.cc#146
Yes, it's stupid to put the reason in an assert (not included in release build) and go with generic error message ('GOOPDATE_E_UNTAGGED_METAINSTALLER' -> 'IDS_GENERIC_ERROR').
Regards