Tranquil IT Forum

Hello and a big THANK YOU for this fantastic tool, WAPT!

After copying the tis-chrome 58.0.3029.96 package to my private repository and running an update, I'm getting the following error on all machines: `

installing tis-chrome
EWaptSetupException: Fatal error:
MSI googlechromestandaloneenterprise64-fr.msi has been installed
and the uninstall key {A4690197-328E-3732-A460-124D6900D9C5} found
but version is not good`.

Do you have a solution to resolve this error?

Thank you in advance for your replies.

The Chrome installer is a bit unusual.

Its version number is something like 66.30.49251.
At the end of the installation, the version will indeed be 66.30.49251.

But during the first Chrome startup, the uninstallkey changes version again and uses the actual Chrome version: 58.0.3029.96. In short, comparing versions becomes a bit of a headache. Furthermore, Chrome can update itself.

We would need to completely rewrite the package without using the install_msi_if_needed function.

On my end, I created a package without the MSI, which extracts the executable from within the MSI to revert to an installation similar to Chromium.

The package is here:
https://wapt.lesfourmisduweb.org/tous-l ... gle-chrome.

So I need to take the time to rewrite the Chrome package differently. Either with the MSI file or, like on my repository, with the EXE file. I don't know yet,

Simon.

I just rebuilt the chrome package from tis.

The package still uses install_msi_if_needed but now uses the get_version argument.

More information:
https://www.wapt.fr/fr/doc/Frequent-pro ... -if-needed

To see the package's setup.py file:
https://wapt.tranquil.it/package_detail ... 2_all.wapt


The update_package() function is not used during installation.

It is only used if you press CTRL-F9 in PyScript while editing.
This allows you to update the Wapt Chrome package with one click!

The need_install and install_msi_if_needed functions were added solely to make the package compatible even with older versions of Wapt prior to 1.3.12.13.

Thank you very much, Simon!

The same problem is present again.

This might not be the same problem; the manifest.sha1 file is incorrect. Looking at the archive, it's a manifest.sha256 file

I just tested with wapt-starter, same problem.

To add to that, on wapt-starter, it does that on all packages...

You'll be seeing more and more manifest.sha256 files.
This is related to the upcoming version of wapt, which is in development; we're switching from sha1 to sha256.
Hence the presence of a manifest.sha256 file. But this isn't a problem for your version.

Could you please provide the exact error returned by the wapt package?

Could you also provide the version of the file located in "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" on the problematic machine?

Simon