VMware Tools Not Installed on Windows 2016, but …..

Hi there,

Working on my Win2K16 VMware template.  Been a bit painful.  I installed VMware Tools and restarted but still saw this in the vSphere Web Client.

notools

Odd.  I checked the running services and there was only one and it was something about alias.  I knew I installed the tools and restarted so WTF.  Nothing in Google.

So, I have had some issues with Win2K16, and it has been a long day. So I uninstalled the tools, and restart.  But this time, when I install the tools, I click on setup64 and do the Run as Admin, and before I restart my VMware Tools message is gone.  After the restart, I check to see what VMware services are installed.

nowtools

So there is three instead of 1.  And the message about VMware Tools not installed is gone.  So all good.  But, now I have to remember that for Win2K16 I need to install VMware Tools using the Run as Admin.  I should mention I am in fact working as Administrator right now too.

Not sure what changed.

Michael

=== END ===

16 thoughts on “VMware Tools Not Installed on Windows 2016, but …..

  1. Thanks for this. Worked for me too but I needed to copy the files to the desktop (even though I’m logged in as the local admin user) before I could get it to work. Complete uninstall, reboot, copy files to desktop, run setup64 as admin.

  2. Fresh install, copied the VM Tools install files to the desktop, ran as administrator — still didn’t install the services. Had to uninstall, reboot, reinstall and finally it worked. Maybe reboot twice on initial installs gets this working the first time?

  3. Hello – I had the same issue. After uninstalling and reinstalling (using run-as administrator) it still reported that the vmware tools were not installed. This is in VCenter 6.5. I ended up having to log out of vcenter and log back in again before the vmware tools error went away.

  4. Hi Guys,

    This was still the case for me with new servers and latest versions of vSphere 6.5 when deploying a Windows 2016 VM. My situation was a tad different in the sense that even though VMware tools had installed, the “VMware Tools” service was not listed in the services console. Following your guys’ instruction, I simply re-mounted the VMware Tools installer ISO again and ran setup by right clicking setup64 and selecting “run as administrator” and did a “repair installation”; I didn’t remove the existing installation nor reboot. After the repair installation completed, I saw the “VMware Tools” service was now listed in the services console and it was started so I went back to the vSphere web client and clicked the little refresh button towards the top by the username and voila; the warning message went away and VMware tools was reporting the proper information to the vSphere web client.

    Just wanted to share my experience. Thanks again for all of the insight and take care!

  5. I had the same problem testing Windows 2019 (right click setup64 and run as administrator). I had to uninstall, reboot and reinstall to fix it

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.