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.
1603.vminst.log) indicates a sharing violation (80070020) when accessing C:\ProgramData\VMware\VMware VGAuth\logfile.txt.0.VGAuthService holds an active file handle on the log file, preventing the installer from completing required directory security operations.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.
To resolve this issue, perform the following steps to clear the file lock before upgrading VMware Tools:
services.msc) or a PowerShell terminal with administrative privileges.vgauthservice).Stop-Service -Name "vgauthservice"sc stop vgauthserviceBest 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.
Note: Since this is a known product defect, please ensure the customer is aware of the recommendation to subscribe to Article 275360 to receive updates regarding the future permanent fix.