Fix 'VMware Tools not installed' error in vSphere 8

You're in vSphere 8, you power on a Windows Server 2022 or Ubuntu 24.04 VM, and you see a yellow triangle in the summary tab. The message says VMware Tools is not installed or VMware Tools is outdated. This usually happens after you clone a VM from a template that didn't have Tools, or after you upgrade the ESXi host but forgot to update Tools on the guest.

Why this happens

VMware Tools is a driver package that makes your VM talk properly to the ESXi host. Without it, the VM can't report its IP address correctly, you can't shut it down cleanly from vCenter, and mouse integration in the console is broken. The error appears because vCenter checks the Tools version on every power-on and compares it to what the host expects. If it's missing or too old, you get the warning.

The real trigger is often:

• You deployed a VM from an OVF/OVA that didn't include Tools.
• You upgraded vSphere from 7 to 8 but didn't upgrade Tools on existing VMs.
• You manually uninstalled Tools for testing and forgot to reinstall.

How to fix it

Option 1: Install Tools through vSphere (easiest)

1. Right-click the VM in vSphere Client.
2. Go to Guest OS > Install VMware Tools.
3. On a Windows VM, this mounts an ISO. On Linux, it mounts a virtual CD.
4. Log into the guest OS and run the installer:

For Windows:

D:\setup.exe

For Linux (Ubuntu/Debian):

sudo mount /dev/cdrom /mnt
cd /mnt
sudo tar -xzf VMwareTools-*.tar.gz -C /tmp
cd /tmp/vmware-tools-distrib
sudo ./vmware-install.pl -d

The -d flag accepts all defaults. Don't skip it unless you have a reason.

Option 2: Use the Tools ISO directly (when vSphere can't mount it)

1. Download the proper Tools ISO from VMware's site. Match it to your ESXi version.
2. Upload the ISO to a datastore.
3. Edit the VM settings, add a CD/DVD drive, and point it to the ISO.
4. Boot the VM and install as above.

This works when the guest OS doesn't have the virtual CD driver loaded yet — common on fresh Linux installs.

Option 3: Upgrade instead of reinstall (for outdated Tools)

If Tools is already installed but outdated, you don't need to uninstall first. Just mount the new ISO and run the installer. It will detect the existing version and upgrade.

On Windows, run setup.exe /s /v "/qn REBOOT=R" from an admin command prompt to do a silent upgrade with no reboot.

What to check if it still fails

• Check the Tools service status: On Windows, look in Services.msc for VMware Tools. Make sure it's running and set to Automatic. On Linux, run systemctl status vmtoolsd. If it's dead, the install didn't finish.
• Check the VM's hardware version: Right-click the VM > Compatibility. If it's way older than the host (e.g., version 10 on ESXi 8), Tools might not work. Upgrade the VM hardware first.
• Look at logs: On Windows, check C:\ProgramData\VMware\VMware Tools\vmware.log. On Linux, /var/log/vmware-tools.log. Error messages like Unable to start services point to a corrupted install — uninstall Tools, reboot, then install fresh.
• Firewall rules: Tools uses ports 902 and 903 for host-guest communication. If a firewall blocks those, Tools shows as connected but doesn't work. On Windows, the installer usually adds exceptions. On Linux, check with sudo ufw status.
• One weird case: I've seen a VM where the Tools status stayed "Not running" even after a clean install. The fix was to disable then re-enable the VM's virtual hardware version in the vSphere Client — it reset something in the VMX file.

My opinion: Skip the old vmware-toolbox-cmd on Linux. It's being deprecated. Use vmtoolsd instead. And never, ever copy the Tools binary from another VM — always install from the matching ISO. I've seen people break their VMs that way.

Once Tools is installed and running, the yellow triangle goes away after a few seconds. You can verify by looking at the VM's summary tab — it should show a green check and the version number (like 12.3.5). If it doesn't refresh, hit F5.