Tranquil IT Forum

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

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

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.

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!

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.

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

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

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.

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!