ERROR: Uninstall Key ... is not in Windows Registry.

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
realynot
Messages: 9
Registration: Oct 09, 2018 - 4:55 p.m.

February 8, 2019 - 11:41

Good morning,

We deploy the different versions of Mozilla Firefox in V52 without any problems using WAPT ETS.
But ever since we wanted to switch to V60 we've had some problems.
We have always used the packages made available on the official repositories.

The apparent error at the packet level of a workstation:

Code: Select all

ERROR: Uninstall Key Mozilla Firefox 52.9.0 ESR (x86 fr) is not in Windows Registry.
firefox.png
firefox.png (3.42 KB) Viewed 5962 times

We tried completely removing the Firefox V52 package from our repository, leaving only V60, and forcing the installation, but nothing worked. It seems some machines have received their V60 update, but it's not happening everywhere, and WAPT never indicates it; we only notice it in the software inventory.



If you have any ideas...
Thanks in advance
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

February 10, 2019 - 1:18 PM

The package you're referring to in your image is package 52.

Could you do the same screenshot with the V60 version of the package,

Simon?
High
realynot
Messages: 9
Registration: Oct 09, 2018 - 4:55 p.m.

February 12, 2019 - 12:03

Yes, that's right, but in my private repository I only have my V60 package...

On the general tab of my hosts, it only displays the old V52 package... and never updates...
Most of the hosts are green with V52.
Can we get a TIShelp?

Thanks
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

February 12, 2019 - 5:05 PM

What architecture is the Firefox version in your repository using?
High
realynot
Messages: 9
Registration: Oct 09, 2018 - 4:55 p.m.

February 14, 2019 - 3:09 PM

In my x86 repository for v60. Before, we used v52 in all.

In the v60 setup.py,

I tried editing the package by forcing the x86 package to be all for v60 at the control file:

architecture: all

, but no better, on the contrary.
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT