Chrome Update 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
Locked
Theo
Messages: 1
Registration: January 20, 2020 - 3:43 PM

January 20, 2020 - 5:36 PM

WAPT console in version 1.7.4
Server running Windows Server 2016
Windows 10 Clients

Good morning,

I need to update Chrome to version 79.0.3945.130-2 on all PCs in my infrastructure, so I downloaded this package: https://store.wapt.fr/store/tis-chrome
However, when installing on some PCs (not all, only a small minority), I get the following error message:

Code: Select all

Installing dep-chrome
Exception: Erreur lors de l'installation de dep-chrome (=79.0.3945.130-2): erreurs dans les paquets [[u'dep-chrome (=79.0.3945.130-2)', PackageEntry('dep-chrome','79.0.3945.130-2') architecture=x64]]
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\waptservice\waptservice.py", line 1151, in run
    self.running_task.run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 405, in pwrapper
    return func(*arg, **kwargs)
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 464, in run
    self._run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 884, in _run
    self.result.get('errors',[])))
Exception: Erreur lors de l'installation de dep-chrome (=79.0.3945.130-2): erreurs dans les paquets [[u'dep-chrome (=79.0.3945.130-2)', PackageEntry('dep-chrome','79.0.3945.130-2') architecture=x64]]
And when I go to the list of packages installed on the PC and click on the Chrome package that's causing the error, the following message appears below:

Code: Select all

installing dep-chrome (=79.0.3945.130-2)
File C:\Program Files (x86)\Google\Chrome\Application\chrome.exe version is : 79.0.3945.130 
Paquet version is : 79.0.3945.130 
NameError: global name 'force' is not defined
On other PCs (again, only a few), I get this error:

Code: Select all

installing dep-chrome(=79.0.3945.130-2)
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 3851, in install_wapt
    exitstatus = setup.install()
  File "c:\windows\temp\waptiffwaa\setup.py", line 37, in install
  File "C:\Program Files (x86)\wapt\common.py", line 3807, in new_func
    return func(*args,**kwargs)
  File "C:\Program Files (x86)\wapt\setuphelpers.py", line 4255, in install_msi_if_needed
    error('MSI %s has been installed and the uninstall key %s found but version is not good' % (msi,key))
  File "C:\Program Files (x86)\wapt\setuphelpers.py", line 4676, in error
    raise EWaptSetupException(u'Fatal error : %s' % reason)
EWaptSetupException: Fatal error : MSI googlechromestandaloneenterprise64.msi has been installed and the uninstall key {0F488B35-59E5-3DA0-80FA-55F3BE746A68} found but version is not good
EWaptSetupException: Fatal error : MSI googlechromestandaloneenterprise64.msi has been installed and the uninstall key {0F488B35-59E5-3DA0-80FA-55F3BE746A68} found but version is not good

Could you help me deal with these two problems?

Thanks in advance
User avatar
Mathieu
Messages: 91
Registration: August 18, 2016 - 10:24

December 2, 2020 - 6:25 PM

Currently, I'm also getting the error

EWaptSetupException: Fatal error: MSI googlechromestandaloneenterprise64_87.0.4280.66.msi has been installed and the uninstall key {27AC56BA-489B-3BDF-98B8-AA1CE49ABB9F} was found, but the version is not good,

but not on all machines.
- WAPT 2.2.3.12463 Enterprise
- Debian 9.9
- Windows 10 21H2 & Windows 11 22h2
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

December 3, 2020 - 10:07 AM

Hello,

We are not experiencing any similar issues with this version across our entire network.
Could you please provide more details about the affected workstations?

Sincerely,
Jimmy
User avatar
Mathieu
Messages: 91
Registration: August 18, 2016 - 10:24

December 3, 2020 - 10:24 AM

It's affecting machines running Windows 10 version 1909 and it impacts any type of desktop or laptop computer

When I look at a post where the problem is present, the registry is fine.
Reg_mathieu
Reg_mathieu
2020-12-03_10h22_57.png (31.97 KB) Viewed 10552 times
- WAPT 2.2.3.12463 Enterprise
- Debian 9.9
- Windows 10 21H2 & Windows 11 22h2
avondra
Messages: 35
Registration: Nov 9, 2016 - 12:02

January 18, 2021 - 1:22 PM

Hello,
have you found a solution? I'm also experiencing this kind of problem on some computers, with no real hardware or software differences, about ten out of 120 computers.
Thank you.
MathieuL
Messages: 14
Registration: January 12, 2021 - 1:14 PM
Location: Normandy

January 18, 2021 - 1:28 PM

Hello,
judging from the error message in the first post, it seems that the posts with the errors are 32-bit and not 64-bit...
could that be the reason?
Wapt 1.8.7334 Enterprise - Windows Server 2016 Datacenter
Admin Console on the server itself
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

January 19, 2021 - 2:10 PM

Hello everyone,

Could you please try a complete uninstallation, manually verifying on an affected machine that Chrome is indeed uninstalled, followed by an installation via WAPT?

I look forward to your feedback,

Best regards,
Jimmy
User avatar
Mathieu
Messages: 91
Registration: August 18, 2016 - 10:24

March 10, 2021 - 08:49

Sorry for the delay.

I just uninstalled manually and then reinstalled via WAPT; the error is gone.
- WAPT 2.2.3.12463 Enterprise
- Debian 9.9
- Windows 10 21H2 & Windows 11 22h2
User avatar
Mathieu
Messages: 91
Registration: August 18, 2016 - 10:24

June 1, 2021 - 12:07

Hello,

I'm still having the same problem. What's happening is that during installation, it keeps traces of the old executable.

Picture

As a result, I keep getting the error in the console

: EWaptSetupException: Fatal error: MSI googlechromestandaloneenterprise64_91.0.4472.77.msi has been installed and the uninstall key {B6E20433-9CA8-39D7-93CD-7191D79C0A6C} found but version is not good.

Regardless of the version, I get this error, whether I force the installation or reboot.

In Windows, the latest version is installed, but since the executable hasn't changed, it's still using the old one.

Am I the only one experiencing this?
- WAPT 2.2.3.12463 Enterprise
- Debian 9.9
- Windows 10 21H2 & Windows 11 22h2
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 1, 2021 - 5:41 PM

Hi Mathieu,
there's a new_chrome.exe file nearby. It seems to be a replacement for an .exe file on reboot. If the .exe is launched during package installation, the installer might create a separate .exe and update the registry to swap the .exe files on the next reboot.
If the computer has rebooted and the .exe files haven't swapped, that's quite odd. Could you try installing the MSI manually to see if the same problem occurs?
Best 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
Locked