Ever had the problem where you either have a corrupt copy of VMware Tools that can’t be updated or you perform an update and the install fails part way through leaving remnants behind? These remnants then stop you from reinstalling VMware Tools and you are presented with the following error messages:
Even an uninstall doesn’t always work so unfortunately you’ll have to revert to to manually removing the items from the registry and file system that are stopping a new install from taking place.
The process to resolve this is simple and the following has been taken from VMware’s Knowledge Base article here. I found that performing these steps helped resolve this problem for me.
Open the Windows Registry editor. Click Start > Run.
Type regedit press Enter.
Browse to HKLM \Software\Microsoft\Windows\CurrentVersion\uninstall. Search for the branch with a key named DisplayName and has a value of VMware Tools . Delete the branch associated with that entry. Do not delete the entire uninstall branch.
Browse to HKLM\Software\Classes\Installer\Products . Search for the branch with the key named ProductName and has a value of VMware Tools . Delete the branch associated with that entry.
Browse to HKEY_CLASSES_ROOT\Installer\Products . Search for the branch with the key named ProductName and has a value of VMware Tools . Delete the branch associated with that entry.
Browse to HKLM \Software\VMware. Delete the branch called VMware Tools .
Ensure the folder located in %ProgramFiles%\VMware\VMware Tools is deleted.
Attempt to install the new version of VMware Tools, if applicable
In the future I might look at generating a script to perform this for me though it happens so rarely I haven’t felt the need up to now. Let me know if you’d find a script useful.
Related posts:
- VMware P2V – Easy Method to Remove HP Agents and Utilities Following on from my original post about removing HP Proliant...
- VMware vCenter agent service does not install or upgrade on ESXi 4.0 hosts – “Cannot install the vCenter agent service. Unknown Installer error” Here’s one for all you VMware ESXi users out there...
- VMware vSphere ESX 4 Error During Install – Booting: MBI=0x000100d8, entry=0×00100212 Maybe you’ve dug out that old server that you’ve...
- VMware ESX 3.5 Update (U5) Released Just a quick post, albeit a few days late,...
- VMware ESX – How to downgrade a VM’s VM Version/HW Level from 7 (4.0) to 4 (3.x) Downgrading a VM’s ‘VM Version’ or as it is commonly...

June 5th, 2009
Kiwi Si
Posted in 





My name is Simon Seagrave and I am a London (UK) based Senior Technology Consultant and vSpecialist working for EMC. 












[...] http://www.techhead.co.uk/how-to-manually-remove-vmware-tools [...]
Ok so i followed these steps. I thought i did everything correctly, but when i try to install another version of it, it always says “A newer Version Is Already Installed” Please help!
That script would be nice to have ; )
[Reply]
Hi I tried to use to your tutorial. But after trying I realised that it only works on a x86 system. When using x64 additional steps are required. Under HKLM\Sofware\Wow6432Node you’ll find additional vmware keys
[Reply]
Great article. It just saved the life of the VM I was working on. Thank you sir!
[Reply]