garyfritz
Enthusiast
Enthusiast

Can't install VMware Tools on Windows 2012 Server R2 guest

I've just installed Player 15 (fresh download from vmware.com) on a new Windows 10 x64 laptop.

I created a 2012 R2 guest with an ISO freshly downloaded from Microsoft.  VMware tools did not install.  Don't think it auto-mounted the Tools CD.

I tried Player > Manage > Install VMware tools but it's grayed out.

I mounted windows.iso from my VMware install directory and ran setup64.exe.  It says it can't verify KB2919355 is installed.  Windows Update says there are no more updates for this ISO image.

How can I install VMware Tools in this scenario!??

Tags (1)
8 Replies
garyfritz
Enthusiast
Enthusiast

80+ views and no answers?  Surely SOMEbody has run into this before??

0 Kudos
peetz
Leadership
Leadership

Hi Gary,

please make sure that the Windows installation meets the pre-requisites for VMware Tools 10.3.x.

Probably the "Microsoft Visual C++ 2017 Redistributable" is missing. Please see

VMware Knowledge Base

for details.

Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
0 Kudos
garyfritz
Enthusiast
Enthusiast

Thank you, I wondered if that was it.  Unfortunately I'm not having much luck installing it.  When I run the installer (from https://aka.ms/vs/15/release/vc_redist.x64.exe), it says "0x80240017 - unspecified error."  According to https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads, that suggests the update doesn't apply to my system, or at least it did with the 2015 redistributable.  That means it's already installed, it's been superseded, or possibly requirements to install the update are missing.

https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2017-system-requirements-vs says VS2017 is supported on W2012R2, so presumably the 2017 redistributable is too.

Looking at the logfile (below), it seems like it's missing parts of the install package.  I'm not quite sure what to do with that.

pastedImage_0.png

0 Kudos
davester14
Contributor
Contributor

Hi Gary,

I have this same issue,

I did some digging on this, and it appears there is another update, KB2975061 that when installed, will allow you to manually install KB2919355.

Link for KB2975061: Download Update for Windows Server 2012 R2 (KB2975061) from Official Microsoft Download Center

Link for KB2919355: Download Windows Server 2012 R2 Update (KB2919355) from Official Microsoft Download Center

I did test this on my VMs and I was able to successfully install the vmware tools

I hope this helps you and anyone else that might be experiencing this issue.

Dave

Here is my source for this information:

https://www.lemonbits.com/2016/10/12/kb2919355-update-not-applicable-computer/

kjdfhaueiase
Enthusiast
Enthusiast

I am hitting this, and it's pathetic on VMware's part.


Because I'm required to install windows updates on 2012 before having vmware tools be able to update, I am blocked from using the vmware tools network driver to install windows updates. Using the vm is extremely cumbersome. This means the whole process takes over an hour.

I actually tried to create an iso that I can mount from ESX with some of the software on it but I bumped into this problem as well.

This is a REALLY bad decision to not make vmware tools contain the Visual C++ executables. I realize there may be some newer features in tools that take advantage of advanced windows features, but a KEY point of vmware is being able to support older operating systems on new hardware.

This is a complete failure of that mission.

quangvu1991
Contributor
Contributor

Today, I run to this problem. VMware Workstation v15. After some google and try, the solution is:

1. Get Windows Update

2. Manually install Update Package (KB2919355) from here

3. In Add Role and Feature, install .NET 3.5 Framework.

4. Install VMTools normally

0 Kudos
dirch201110141
Enthusiast
Enthusiast

daveester14's tip is confirmed. Worked with Workstation 15.5 and Win2012R2 standard. Still had to mount the windows.iso manually, but at least sort of ... happy now. It still does not remove the need for hitting VMware with a damp towel

0 Kudos
Integr8
Contributor
Contributor

Thanks Dave, worked a treat.

"I'll never turn to the Dark Side..."
0 Kudos