How to fix VMware Tools and black screens with Windows 10 Creator Update

At “press time”, Microsoft has announced that Windows 10 Creator Update [i.e. Redstone 2, a.k.a. build 15063, a.k.a. v1703] has been released. Those on the technical side probably know how to get it. For the rest, it will be on or after April 11th.

This article deals with VMware Workstation 11 [and probably older] as well as VMware Player. So most likely the audience are those who are technical.

If you are like me and are using an unsupported VMware Workstation or Player and get a black screen for the video [or at least that] after upgrading Windows 10 or installing VMware Tools in a fresh Windows 10 installation, the following may make Windows 10 Creator Edition [a.k.a. blah, blah, blah] run better with VMware Workstation or Player:

Go here and download either the ISO image or the applicable EXE for the architecture. You probably want the ISO as you may not be able to copy over the executable but you can attach the ISO. Tested with version 10.1.5 build 5055683.

What you are doing is installing the VMware Tools for the latest version of VMware Workstation 12.5. The video issue gets corrected. I am guessing you can install any VMware Tools for your product [and not VMware Tools for ESX].

I tested this on two VMs, one upgraded from v1607 to v1703 and a fresh installation of v1703 and both worked but I recommend removing the current VMware Tools first.

Prior to trying this, I would suggest you take a snapshot [applies to Workstation only] or back up your VM.

[Update 2017/07/19:] Installing Windows Server 2016 also works in the same method. Install and then download and install the ISO file for the VMware Tools associated with VMware Workstation 12.5.

Losing disk space in VMware Workstation and don’t know why?

If you use VMware Workstation and you wonder where you are losing disk space, of course you look into the standard folders such as %windir%\temp and %userprofile%\appdata\local\temp and of course trimming WinSXS in Windows 7 [and Server 2008 R2] and later.

But logically you may ignore the VMware-%username% folder because it may contain some useful [but still temporary] files. Probably true, but when you copy and paste something from the host system to your virtual machine, it copies the files from your host computer to a temporary folder and then to where you are pasting it to. But for whatever reason, the temporary location is permanent.

So if you go into %userprofile%\AppData\Local\Temp\vmware-%username%\VMwareDnD, you will have a copy of everything you copied from the host.

Note: The AppData folder is hidden. Don’t ask me why.

For example if you logged in with John, the above would translate as c:\users\John\AppData\Local\Temp\vmware-John\VMwareDnD [assuming using Windows Vista and later].

Note: %windir% is the replacement variable for the location to Windows including the drive. %userprofile% is the replacement variable for the Users [or Documents and Settings] folder with your login name and the drive letter. %username% is the replacement variable for your login name.