Administrators observe the following behaviors in a vSphere environment:
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 0x0This 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.
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
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).
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):
Note: Ensure this is applied to the source VM / source template.
For more details on VMware Tools drivers being published to Windows Update, please refer to: