Google Chrome problem

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Answer
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

March 12, 2024 - 10:44

Good morning,

WAPT user > Windows in 2.5.2
WAPT server > Debian in 2.5.2.15207

I'm experiencing Chrome package update issues on many PCs across the network. I installed the latest versions a few weeks ago and I'm encountering these kinds of problems:

Code: Select all

CalledProcessErrorOutput: Command 'msiexec /norestart /q /i "googlechromestandaloneenterprise64.msi" NOGOOGLEUPDATING=1 NOGOOGLEUPDATEPING=1' returned non-zero exit status 1603.
Output:
So when I go on my PC, I see that I can't uninstall Chrome from the Control Panel because during the uninstallation process, it asks me for the google executable googlechromestandaloneenterprise64.msi... This isn't the correct procedure, but to try and resolve the issue, I delete the Program Files > Google > Chrome folder and the User > AppData > Local > Google > Chrome folder. Then I restart the installation from WAPT, and it works.

However, I have just noticed that the error (above) returns, despite the resolution (above), following the latest versions of Chrome.

Is there a way to truly clean up all past traces of Chrome in order to "start fresh"?

Thank you in advance, best regards.
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

March 12, 2024 - 2:32 PM

Hello Thomas,

the WAPT package performs a system-wide installation, not a profile-based one. If any users have installed it in their home directory (which should be blocked if possible), you'll need to check for the removal of the appdata installations before the global installation.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

March 15, 2024 - 09:39

Hello,

thank you for your reply. I was able to check one of the computers in question and it didn't have any Chrome installations or files in the appdata folders of other users who had logged in. Do you have any other suggestions?

Thank you in advance, best regards.
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

March 15, 2024 - 12:44

Good morning
I sometimes encounter this problem, but not only with Chrome
The infamous error 1603...

The solution I found is a bit of a pain, but here it is:
  • Open the PC registry, go to HKEY_CLASSES_ROOT\Installer\Products (or HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products if it is remote).
  • Find the key that corresponds to the program and delete it
  • Restart the installation
It works every time!
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

March 18, 2024 - 5:18 PM

Hello,

thank you for this new tip, but it didn't work because I couldn't find the Chrome uninstallation key in the registry of the computer in question.

Regards.
thirst_for_knowledge
Messages: 14
Registration: December 5, 2024 - 3:33 PM

January 2, 2025 - 2:11 PM

Good morning,

I'm reviving this thread because I'm having the same problem when launching the tis-chrome package (131.0.6778.205-45). The error is infamous 1603...

Code: Select all

raise CalledProcessErrorOutput(proc.returncode, cmd, \'\'.join(output))\nwaptutils.CalledProcessErrorOutput: Command \'msiexec /norestart /q /i "googlechromestandaloneenterprise64.msi" NOGOOGLEUPDATING=1 NOGOOGLEUPDATEPING=1\' returned non-zero exit status 1603.\nOutput:\n']]
Given that the target PC is running Windows 10, and has never installed Google Chrome, there are no registry keys lingering in the registry.

I've searched the forum but there's no solution yet. Do you have any ideas on how to solve this problem?

Thank you and Happy New Year!
- Installed WAPT version: 2.6.0.16714
- Server OS: Ubuntu
- Administration machine OS: Windows Server 2019
User avatar
blemoigne
Messages: 178
Registration: July 17, 2020 - 11:29

January 3, 2025 - 10:20

Hello,
In the latest version of the WAPT agent, the source error is retrieved from the event log, which simplifies diagnosis.
Have a good day,
Bertrand
thirst_for_knowledge
Messages: 14
Registration: December 5, 2024 - 3:33 PM

January 6, 2025 - 11:27

blemoigne wrote: January 3, 2025 - 10:20 AM Hello,
In the latest version of the WAPT agent, the source error is retrieved from the event log, which simplifies diagnosis.
Have a good day,
Bertrand
Good morning,

Thank you for your feedback. I eagerly await your new version.
- Installed WAPT version: 2.6.0.16714
- Server OS: Ubuntu
- Administration machine OS: Windows Server 2019
thirst_for_knowledge
Messages: 14
Registration: December 5, 2024 - 3:33 PM

January 10, 2025 - 2:18 PM

Hello,

I think I've found something to help you identify the problem.

When I manually install Google Chrome using the installer file from the official Google website: https://www.google.com/chrome/ or from the Offline Installer file for a user, error 0x12524 appears, and this is exactly the same behavior I get with the tis-chrome package.
So, I followed this guide (https://support.google.com/webdesigner/...2524?hl=en) to get the supposedly "real" Offline Installer file, and this time, the installation goes without any problems:
- Using 7-Zip, extract the "ChromeStandaloneSetup64.exe" file
- Extract the "updater" file
- Run "ChromeStandaloneSetup64\updater\bin\Offline\{

Yours sincerely!
- Installed WAPT version: 2.6.0.16714
- Server OS: Ubuntu
- Administration machine OS: Windows Server 2019
Answer