[SOLVED] tis-vmwaretools

Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is provided 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 (1.8.2 / 2.0 / 2.1 / 2.2 / etc.) AS WELL AS the Enterprise / Discovery edition.
* Specify the server OS (Linux / Windows) and version (Debian Stretch/Buster - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine (Windows 7 / 10)
. * As with any community forum, support is provided voluntarily by members. If you require sales support, you can contact the Tranquil IT sales department at 02.40.97.57.55
Locked
jsdmc
Messages: 8
Registration: Nov. 30, 2018 - 3:56 p.m.

June 10, 2026 - 4:45 PM

Hello,

there's a version recognition problem after installation in tis-vmwaretools.

The package installs the application, but when verifying the installation key in the registry, the package expects vmwaretools-version-build, while the key returns vmwaretools-version.

Therefore, the package remains in error despite the application installing correctly.
User avatar
dcardon
WAPT Expert
Messages: 1970
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 10, 2026 - 5:56 PM

Hi Julien,

thanks for the update.

Just so you know, the WAPT packages for Windows x64 are being tested on a Proxmox farm, and the VMware Tools installation setup.exe won't launch if the VM's BIOS isn't a VMware BIOS, so the installation test must have been bypassed. Normally, the LUTI farm tests the uninstallation keys, but in this case, it couldn't be tested and it was missed.

We'll look into fixing it quickly.

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
kcherel
Messages: 7
Registration: January 12, 2026 - 10:01

June 11, 2026 - 3:08 PM

Hello Julien,

Indeed, there is an inconsistency between the version present on the name of the recovered binary and the one corresponding to the version referenced on the binary.

The problem has just been resolved.
Here is the fix applied to the setup.py file:

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *

def is_vmware_host():
    wmi = wmi_info(keys=['Win32_ComputerSystem'])
    computer_system = wmi['Win32_ComputerSystem']

    if isinstance(computer_system, dict):
        if 'VMware, Inc.' in computer_system['Manufacturer']:
            return True

    if isinstance(computer_system, list):
        for v in computer_system:
            if 'VMware, Inc.' in v['Manufacturer']:
                return True
            
    return False

def install():
    bin_name = glob.glob("VMware-tools-*.exe")[0]
    print(f"Installing: {bin_name}")

    if not is_vmware_host():
        error("The current computer is not VMware virtual machine !")

    install_exe_if_needed(
        bin_name,
        silentflags='/S /v /qn REBOOT=R',
        name="VMware Tools",
        min_version=str(Version(control.get_software_version(),3)),
        get_version=get_installed_version
    )
def get_installed_version(key):
    return str(Version(key["version"],3))

Good day,
Sincerely,
Kevin.
Locked