VMware ESXi and vSphere Cluster Management

Install VMware Tools on a Windows Virtual Machine Using the vSphere Web Client

Learn how to mount the VMware Tools ISO and install, configure, verify, and troubleshoot VMware Tools on a Windows VM managed by vCenter Server.

VMware Tools is a collection of guest operating system drivers, services, and utilities. It is installed inside the Windows guest operating system, not on the ESXi host. This lesson explains how to mount the VMware Tools ISO from the vSphere Web Client, run the Windows installer, select a setup type, restart the VM, and verify the result.

What VMware Tools provides

A virtual machine (VM) is a software-defined computer running on a hypervisor. ESXi is VMware's bare-metal hypervisor, while vCenter Server centrally manages ESXi hosts and VMs. The guest operating system is the operating system installed inside the VM, such as Windows.

VMware Tools runs in the guest and improves communication between Windows and the VMware virtualization platform. Depending on the installed version and selected components, it provides or supports:

  • Guest-specific virtual device drivers.
  • Improved mouse movement and display behavior through the VM console.
  • More accurate or coordinated time synchronization.
  • Cleaner guest shutdown and restart operations initiated from vSphere.
  • Guest IP address and other guest information reporting to vSphere.
  • Additional guest-related management and integration features.

A Windows VM can boot and run without VMware Tools. However, it may have reduced device support, less convenient console behavior, limited guest information in vSphere, and less reliable guest operating system integration. Tools do not replace Windows updates or application drivers; they complement the guest operating system.

Prerequisites and preparation

Before starting, confirm that the target VM is powered on with Windows already installed and booted. It must be registered in vCenter Server inventory, and your account must be allowed to open the VM console and invoke the guest operating system tools-installation action.

The VM also needs an available virtual CD/DVD drive. This is virtual hardware that connects an ISO image to the guest. The VMware Tools ISO must be available from the ESXi host or from the VMware Tools repository configured for the environment.

Inside Windows, use a local administrator or an authorized domain account with local administrative rights. Installation changes drivers and services and commonly requires a restart, so confirm that a maintenance or restart window is available.

Pre-installation checklist

Check | Why it matters | How to verify

Correct target VM identified | Prevents mounting media or changing the wrong machine | Confirm the VM name, folder, host, operating system, and business owner in inventory

Windows guest is running | The guest must be available for console installation | Confirm the power state is on and Windows has reached the login screen or desktop

Administrator access is available | Drivers and services require elevation | Sign in with a local administrator or approved domain account

VM console can be opened | The console provides direct interaction with Windows | Open the console from the selected VM

Virtual CD/DVD device is available and connected | The ISO needs a device through which Windows can read it | Review VM hardware and connect the device if necessary

A restart can be performed | Tools may not become active until Windows restarts | Notify users and schedule the work if the VM is production-critical

No installation is in progress | Concurrent install, upgrade, or removal operations can conflict | Check Windows notifications, running installers, and the existing VMware Tools state

Locate the Windows VM in vCenter

  1. Connect to the appropriate vCenter Server using the vSphere Web Client.
  2. Open an inventory view such as Hosts and Clusters or VMs and Templates.
  3. Search for and select the intended Windows VM. Validate its name and operating system before taking any action.
  4. Open the VM console. A VM console is a remote display and input session that lets you interact directly with the guest operating system.

Prepare Windows

  1. Sign in through the VM console with the authorized administrative account.
  2. Save work and close applications. The installer may request a restart.
  3. Check that another VMware Tools installation, upgrade, or uninstall is not already running.
  4. Confirm the Windows architecture if the installer presents separate choices. Use the executable appropriate for 64-bit or 32-bit Windows rather than guessing.

Mount the VMware Tools ISO

The vSphere action does not install software directly from vCenter. Instead, it mounts the VMware Tools ISO to the VM's virtual CD/DVD drive. Windows then sees installation media and runs the installer from that drive.

  1. With the VM selected, open its actions menu.
  2. Choose the Guest OS option and select the action to install VMware Tools. In some vSphere versions this may be labeled Install VMware Tools, Upgrade VMware Tools, or similar.
  3. Confirm the request to mount the VMware Tools ISO.
  4. Wait briefly for the virtual CD/DVD device to become available in Windows.

If the action cannot mount media, inspect the VM hardware. The virtual CD/DVD device must exist and be connected. Also verify that the host or configured repository can provide the VMware Tools ISO.

Start the Windows installer

Using AutoPlay

AutoPlay is Windows behavior that can offer to launch a program when optical or removable media is mounted. If an AutoPlay notification appears, select the VMware Tools setup program. For a 64-bit Windows guest, choose the appropriate 64-bit setup executable when the installer presents that choice.

Windows User Account Control (UAC) may ask whether the installer can make changes. UAC protects Windows by requiring an elevation decision for administrative operations. Approve the prompt only when the source and action are expected and authorized.

When AutoPlay does not appear

  1. Open File Explorer in Windows.
  2. Find the optical drive containing the VMware Tools media. Its label may identify it as VMware Tools.
  3. Open the drive and launch the setup executable appropriate for the Windows architecture.
  4. Approve UAC elevation or provide authorized administrator credentials if requested.

Choose a setup type

The wizard normally offers three installation choices. Select the option that matches the guest workload and your organization's build standard.

Setup type | What it installs | Best use case | Administrative consideration

Typical | Commonly required VMware Tools components | Most general-purpose Windows VMs | The recommended default unless a standard requires different features

Complete | All features made available by the installer | Environments that need the full component set | Adds components that may not be necessary for every workload; validate against policy

Custom | Individually selected features | Controlled builds or specialized workloads | Document selected drivers and optional components so the VM remains supportable and consistent

For a normal Windows server or desktop VM, Typical is generally the appropriate starting point. Use Custom when security, image standards, or workload requirements require precise component selection. Use Complete only when the additional components are wanted and supported.

Install and restart Windows

  1. Review the selected setup type and begin the installation.
  2. Wait while the wizard copies files and installs VMware Tools drivers and services. Do not power off the VM during this process.
  3. Finish the wizard after it reports successful completion.
  4. Restart Windows immediately when prompted, or schedule the restart for the approved maintenance window.

VMware Tools might not be fully active until Windows has restarted. A delayed restart can leave drivers, services, or integration features in a partially applied state.

Example: standard installation on a Windows 7 guest

  1. Locate the Windows 7 VM in vCenter inventory and confirm that it is the intended machine.
  2. Open the VM console and sign in as a local administrator.
  3. Use the VM actions menu, choose Guest OS, and invoke the VMware Tools installation action.
  4. Confirm that the ISO is mounted to the virtual CD/DVD drive.
  5. Launch the 64-bit setup program from AutoPlay or from the mounted drive, as appropriate for the guest.
  6. Choose Typical, start the installation, finish the wizard, and restart the VM.
  7. After Windows returns, verify that VMware Tools is running in both Windows and vSphere.

Legacy Windows versions such as Windows 7 can have limited support with newer VMware Tools releases. Confirm compatibility before installing or upgrading tools on an older guest.

Verify the installation

Perform checks in both vSphere and Windows. A successful wizard alone is not sufficient if the service failed to start or the restart was skipped.

Verification item | Expected result | Where to check

VMware Tools install completes | The wizard reports success without an error | Windows installer wizard

Windows has restarted | The guest has booted normally after installation | VM console and Windows sign-in

Tools service is active | The VMware Tools service is running | Windows Services or the VMware Tools application entry

vSphere reports Tools running or current | The VM summary or monitor view shows an active, supported tools state | vSphere Web Client

Guest integration works | Mouse and display behavior are improved, clean shutdown options work, and IP reporting appears where supported | VM console, vSphere summary, and controlled guest-operation test

In Windows, confirm that VMware Tools appears in installed applications and that its service is running. In vSphere, check the VM summary or monitor information for the tools status. Record the installed version and determine whether a later upgrade is required by your compatibility and maintenance policy.

Upgrade and maintenance considerations

A first-time installation adds VMware Tools to a guest that does not have it. An in-place upgrade replaces or updates an existing installation. vSphere may indicate that the installed tools are outdated relative to the version supplied by the host.

  • Validate the VM name, operating system, and current tools state before every install or upgrade.
  • Use a VMware Tools version supported by the Windows guest and by the deployed ESXi and vCenter versions.
  • Plan upgrades around maintenance windows because driver changes and restarts can affect availability.
  • Test the result for important workloads before applying the same procedure broadly.
  • Do not assume that the newest available tools release supports every legacy Windows version.
  • Expect menu labels and installer behavior to vary across vSphere releases.

Troubleshooting

The installer does not start automatically

AutoPlay may be disabled or suppressed by policy, or the ISO may be mounted without producing a notification. Open File Explorer, locate the VMware Tools CD/DVD drive, and start the appropriate setup executable manually. If the drive is empty or unavailable, confirm that the virtual CD/DVD device is connected and retry the mount action.

The Install VMware Tools action is unavailable or fails

Common causes include a powered-off VM, insufficient vCenter permissions, no usable virtual CD/DVD device, or unavailable host-side installation media. Power on the VM, reconnect to vCenter, verify permissions for VM interaction and guest operations, and inspect the VM hardware. If the device is present, check that it is connected and that the ESXi host or configured repository can access the tools media.

Windows blocks the installer or requests credentials

The signed-in account may not be a local administrator, UAC may require elevation, or endpoint controls may restrict software installation. Use an approved account with local administrative rights, approve the elevation prompt when authorized, or follow the organization's endpoint-management exception process.

Tools remains outdated or not running after installation

First restart Windows if it has not been restarted. Then review the installer completion message, the installed application entry, the VMware Tools service, and relevant Windows event information. If the service is stopped, investigate the service or driver error. If vSphere reports an older version than expected, compare the installed version with the host-provided version and perform an approved upgrade.

The wrong installer executable was started

Confirm whether the guest is running 32-bit or 64-bit Windows, then run the setup executable intended for that architecture. If the architecture is uncertain, check Windows system information before continuing.

Maintenance-window example

  1. Notify users and save open work.
  2. Confirm the VM identity, tools status, compatibility, and rollback or recovery plan.
  3. Mount the VMware Tools ISO and install or upgrade the selected components.
  4. Restart Windows immediately after the wizard completes.
  5. Verify the tools service, vSphere status, guest IP reporting, console behavior, and application availability.
  6. Record the installed version, selected setup type, restart time, and any follow-up upgrade requirement.

Key exam and operations notes

  • VMware Tools is installed in the guest operating system; it is not installed on the ESXi host as a guest package.
  • The vSphere installation action mounts an ISO to the VM's virtual CD/DVD drive; Windows still runs the installer.
  • A VM can run without Tools, but guest integration and management capabilities are reduced.
  • Typical is the usual default, Complete installs all available features, and Custom permits component selection.
  • Local administrative rights and UAC approval may be required.
  • Restart Windows after installation unless a controlled, documented delay is necessary.
  • Verify status in both Windows and vSphere, and check compatibility before installing on legacy guests.

For related guidance, see VMware Tools Windows Installation.