VMware Tools installation fails with error 1722

VMware Tools installation fails with Error 1722


  • VMware Tools installation fails on a Windows 2003 virtual machine in ESX 3.5 Update 2
  • You see the error:

    Error 1722: There is a problem with Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

  • The Event Viewer event logs display the error:

    Action VM_RegisterVCBSnapshotProviderService, location:
    C:\WINDOWS\Installer\MSI67.temp, command: -register "C:\Program Files(x86)\VMware\VMWare Tools\Drivers\vcc\VCBSnapshotProvider.dll" "VMware Snapshot Provider" "vmvss" "VMware Snapshot Provider"


To fix a VMware Tools installation on Windows 2003 in ESX 3.5 Update 2:

  1. Follow the instructions in the Microsoft Knowledge Base article http://support.microsoft.com/kb/301919/EN-US/.
  2. In Windows Services (services.msc), ensure that the following services are enabled. If they are not enabled, enable them.
    • COM+ System Application
    • Distributed Transaction Coordinator

  3. Try the installation again.

If the above steps do not resolve the issue:

  1. Double-click the Orca.msi file in the \Microsoft SDK\bin folder to install the Orca editor.
  2. Click Start > Programs > Orca.
  3. In the virtual machine, click Install VMware Tools but do not follow the wizard.
  4. Explore the VMware Tools CD mounted on the guest.
  5. Open the VMware Tools.msi file.
  6. Choose Binary on left pane and double click the comreg.exe data column on the right pane.
  7. Click Write to Binary file, browse to C:\, and click OK to save the comreg.exe file to C:\.
  8. Open a command prompt and run the following command:

    C:\comreg.exe -register "C:\Program Files\VMware\VMware Tools\Drivers\vss\VCBSnapshotProvider.dll""VMware Snapshot Provider""vmvss""VMware Snapshot Provider"

  9. Try the VMware Tools installation again.

During installation the WinZip self-extracting file fails

During installation the WinZip self-extracting file fails


  • During installation the WinZip self-extracting file fails
  • Attempting to install vCenter Server Heartbeat by double-clicking the WinZip self-extracting file results in a failure to run the vCenter Server Heartbeat Setup program.


The vCenter Server Heartbeat kit is a self-extracting executable that is built using the WinZip utility. It contains both the 64bit and 32bit versions of the vCenter Server Heartbeat code. Under normal circumstances, when you run the self-extracting executable, it extracts all files to a temporary location, discovers whether the server is 32bit or 64bit, then executes the appropriate version of the installer.
If the self-extracting executable cannot discover whether the server is 32bit or 64bit, it fails to install and issues an error message.
If this happens, use one of these methods to complete the installation:
Note: In the instructions below, replace xxxx with the version number in the file name of your kit.
  • Open a command window and set the PROCESSOR_ARCHITECTURE environment variable and then execute the self-extracting executable from that command window:




  • Manually extract the kit and execute the appropriate installer:
    1. Rename V5-5-xxxx-VCSQL.exe to V5-5-xxxx-VCSQL.zip.
    2. Extract all files to a TempLocation.
    3. CD to the location of the appropriate installer:

      CD TempLocation\V5-5-xxxx-VCSQL\V5-5-VCSQL-X64


      CD TempLocation\V5-5-xxxx-VCSQL\V5-5-VCSQL-X86

    4. Run Setup.exe.