In the vCenter vSphere client, Windows virtual machines (VMs) running identical guest operating systems, such as Windows Server 2016 or 2022, often display different VMware Tools version numbers. Despite these discrepancies, vCenter reports the VMware Tools status for all impacted VMs as "Current." This inconsistency typically occurs because vCenter evaluates the "Current" status against the local ESXi host repository baseline rather than a universal environment-wide version.
VMware vCenter Server
VMware ESXi
vCenter will mark VMware Tools as "Current" whenever the installed VMware Tools version is equal to or newer than the host’s inbox version (the version provided by the tools-light VIB).
1. VMs are running on different ESXi hosts with different tools-light versions
Each VM’s Tools status is evaluated against the inbox version of its respective host.
If VMs are running on hosts that have different tools-light versions, even though the VMs may show different VMware Tools versions, each VM can still appear as Current because it matches (or exceeds) the inbox version of the host it is running on.
2. Some VMs have newer VMware Tools installed than the ESXi hosts provide
Another scenario is when all ESXi hosts have the same tools-light version, but some VMs have newer VMware Tools installed inside the guest OS.
This can occur when,
In such cases, the VM’s installed VMware Tools version is newer than the ESXi host’s inbox version. vCenter treats newer versions as valid and therefore reports the status as Current, even though the version number differs from other VMs.
This behavior is expected and does not indicate a problem.
If consistency is desired, the following methods can be used,
tools-light version.