vmtools current but not running

[supermanDan]

Ever since upgrading to esxi 6.0 U2 (from 5.5) we've had a problem with vmtools on our windows vms (2008R2 and 2012R2).  The vmtools show as current but "not running".  If I RDP or open a vsphere console to one of these vm's, the vmtools will start and show as running.  However,  after logging off of the vm, the vmtools will stop again (sometimes right away; other times it takes a while).  I opened an SR with VMware support and they suggested upgrading tools from 10.0.6 to 10.0.9 in which I have done.  The issue is still occurring on some virtual machines.  I've checked power options within windows on the vm's to see if there was something making the vm sleep, but I don't see anything like that.  Just wondering if anyone else has experienced this.  We don't have this problem with any of our Linux vms.

[RajeevVCP4]

To resolve this issue, you must reinstall VMware Tools after deleting the C:\Program Files\VMware\VMware Tools and C:\ProgramData\VMware\VMware Tools folders:

1. Uninstall VMware Tools from the virtual machine.
2. Reboot the virtual machine.
3. Take a backup of the C:\Program Files\VMware\VMware Tools and C:\ProgramData\VMware\VMware Tools folders by renaming the folders.
4. Reboot the virtual machine.
5. Install VMware Tools.

The Summary tab of the Windows 2008 R2 virtual machine reports the status of VMware Tools as Not Running (Current) (2063…

[Jitu211003]

Hi,

You need to uninstall the vmtools first then reinstall

if you face msi missing error run the below command

cd rom drive>     setup.exe  /C

it will clean the registry value for msi.

If still fails, use the Microsoft MSI cleanup utility to uninstall the vmtools.

It will surely work.

for more visit,

vmwarediary.com  or vmwarediary.in

[NelsonCandela]

Hello there, supermanDan​ and others,

I was having the same problem on a W7 x64 VM in vSphere 6.0.

The VMware Tools were reported as being "Running (Not Current)", but within the OS the installed software list showed no sign of VMware Tools being installed at all.

The problem could be solved by simply re-running the installer (without the need to rename or uninstall) interactively while I was logged on on the machine. After a reboot everyting was fine, VMware Tools are now reported as "Running (Current)" within the vSphere Client (C#) and the Web Client and the behaviour is back to normal.

BR

NC

[Dave_the_Wave]

This post is related:

https://communities.vmware.com/message/2809627#2809627

I can't speak for early versions, but current versions of VM Tools appears to clean up a previous install first.

This is vitally important as it keeps the vmxnet3 mac address.

Uninstalling VM Tools and re-installing a new VM Tools will generate a new mac address, which can certainly mess up certain licensings of sorts.

[NelsonCandela]

Good advice, thanks for pointing this out @Dave_the_Wave.

[GhostRider024]

I went to the installed programs on the virtual machine and clicked Change on VMware Tools. Then I repaired the installation and rebooted.

It was running very slow and the Tools would not stay running but this fixed it for me.