VMware Tools 13.1.0 auto-upgrade fails due to VGAuthService file lock

Products

• VMware vSphere ESXi

Issue/Introduction

VMware Tools automated upgrades fail on Windows virtual machines when version 13.1.0 is initiated. The installation rolls back, leaving the virtual machine in a state where VMware Tools are uninstalled or unresponsive. This issue is triggered by an active file lock on the VGAuthService log file.

• VMware Tools installation rolls back with error code 1603.
• Log analysis (vminst.log) indicates a sharing violation (80070020) when accessing C:\ProgramData\VMware\VMware VGAuth\logfile.txt.0.
• Service VGAuthService holds an active file handle on the log file, preventing the installer from completing required directory security operations.

Environment

• VMware Tools 13.1.0
• Windows-based virtual machines

Cause

A regression in the VMware Tools 13.1.0 installer prevents the VGAuthService (VMware Alias Manager and Ticket Service) from stopping correctly during the upgrade process. This creates a file-locking conflict that forces the installer to roll back.

Resolution

To resolve this issue, perform the following steps to clear the file lock before upgrading VMware Tools:

1. Open the Windows Services console (services.msc) or a PowerShell terminal with administrative privileges.
2. Locate the service VMware Alias Manager and Ticket Service (vgauthservice).
3. Stop the service:
   
   
   • PowerShell: Stop-Service -Name "vgauthservice"
   • Command Prompt: sc stop vgauthservice
4. Initiate the VMware Tools upgrade process manually or restart the auto-upgrade policy.
5. After the upgrade succeeds, verify the service is running.

Best Practices: To prevent recurrence, decouple Windows Update cycles from VMware Tools upgrades. Perform system reboots to complete VMware Tools upgrades before applying Windows Update cycles, as overlapping reboots can interrupt installation processes.

 

Additional Information

Note: Engineering has identified this issue. Please subscribe to Article 275360 to be notified once the permanent fix is released in a future version of VMware Tools.