Skip to main content

Uninstalling VMware tools Manually from VM



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:


A previous version of VMware Tools is already installed


Error 1316 A network error occured while attempting to read from the file C:WindowsInstalledVMware Tools.msi


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 SoftwareMicrosoftWindowsCurrentVersionuninstall. 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 HKLMSoftwareClassesInstallerProducts . 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_ROOTInstallerProducts . 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 SoftwareVMware.  Delete the branch called VMware Tools .
  • Ensure the folder located in %ProgramFiles%VMwareVMware Tools is deleted.
  • Attempt to install the new version of VMware Tools, if applicable

Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl
google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0 google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0