VMware Tools Automatically Upgrades Despite "Manual" Policy Setting
search cancel

VMware Tools Automatically Upgrades Despite "Manual" Policy Setting

book

Article ID: 428890

calendar_today

Updated On:

Products

VMware vCenter Server 8.0 VMware vSphere ESXi 8.0

Issue/Introduction

Administrators observe the following behaviors in a vSphere environment:

  • VMware Tools updates automatically on Windows Virtual Machines without vSphere administrator intervention.
  • Policy Ignored: The issue occurs even when the Virtual Machine configuration parameter tools.upgrade.policy is explicitly set to "manual".
  • Unexpected Reboots: VMs reboot automatically to complete the installation, causing service disruption.
  • Version Mismatch: The installed version of VMware Tools on the Guest (e.g, 13.0.10) is newer than the version bundled with the ESXi host (e.g, 12.5.0).
  • Log Evidence: The vmware.log file shows a "hard reset" initiated by the Chipset (Guest OS) rather than a User or VimAPI event.
    YYYY-MM-DDTHH:MM:SS.509Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset.

    YYYY-MM-DDTHH:MM:SS.535Z In(05) vcpu-0 - Tools: ToolsRunningStatus_Reset, delayedRequest is 0x0

Cause

This issue is caused by an external update mechanism within the Guest Operating System, such as Windows Update (WSUS) or an Endpoint Management System, rather than the vSphere Platform.

  1. Microsoft Driver Distribution: VMware publishes certified drivers (pvscsi, vmxnet3, etc.) and the VMware Tools package directly to the Microsoft Update Catalog.
  2. Scope of Control: The vSphere setting tools.upgrade.policy = "manual" is a Hypervisor-level control. It successfully prevents the ESXi host from mounting the windows.iso and triggering an update. However, it cannot prevent the Windows Operating System from downloading drivers from Microsoft servers or an internal SCCM distribution point.
  3. The "Impossible Version" Indicator: If the Guest OS installs a version of Tools that does not exist on the ESXi host's filesystem, the update could not have originated from vSphere.

Resolution

Step 1: Validate the Update Source:
To confirm if the update was guest-initiated, review the vmware.log file for the affected VM. Identify any discrepancies where the version installed on the Guest OS is higher than the version available on the ESXi Host.

      Example Log Evidence: vmware.log
            YYYY-MM-DDTHH:MM:SS.611Z In(05) vmx - ToolsUpdateManifestInfoWorkerThreadDone: Compared tools manifest from host and from the guest. Status = 4.
            YYYY-MM-DDTHH:MM:SS.611Z In(05) vmx - TOOLS installed legacy version 13322, available legacy version 12448

  • Analysis: The Guest installed Build 13322, but the Host only has Build 12448. This proves the source was external to vSphere.

Engagement of the Guest OS / Windows Administration Team is required for Steps 2 and 3 to audit the Windows Event Logs within the VM.
Step 2: Identify the Guest Trigger Action Required:Open Event Viewer (eventvwr.msc).

  1. Navigate to Windows Logs > Application.
  2. Filter for Source: MsiInstaller.
  3. Look for Event ID 11707 or 1040 with the description: "Installation operation completed successfully for product 'VMware Tools'."
  4. Check the User field. If it lists SYSTEM, the trigger was likely an automated agent (SCCM/Windows Update).

Step 3:Block Driver Updates via Group Policy (GPO)
To prevent Windows from automatically updating VMware drivers, the Guest OS Team must apply the following Group Policy to the affected Organizational Unit (OU):

  1. Open Group Policy Management Console.
  2. Navigate to: Computer Configuration > Administrative Templates > Windows Components > Windows Update.
  3. Locate the policy: "Do not include drivers with Windows Updates".
  4. Set this policy to Enabled.

Note: Ensure this is applied to the source VM / source template.

Additional Information

For more details on VMware Tools drivers being published to Windows Update, please refer to: