VMRC failed to update from 13.0.0 or 13.0.1 to 13.0.2 due to "Failed to install USB inf file." on Windows.
You might see vminst.log like this.
YYYY-MM-DDThh:mm:17.246+TZ| USBDeviceInstUtil-build-24896162| I0: --- VMStopUSBArbSvc(): Stopping USB arbitrator service
YYYY-MM-DDThh:mm:17.246+TZ| USBDeviceInstUtil-build-24896162| I2: Inst_QueryServiceRunningStatus: Attempting to query service: VMUSBArbService
YYYY-MM-DDThh:mm:17.246+TZ| USBDeviceInstUtil-build-24896162| E1: Inst_QueryServiceRunningStatus: Service could not be opened: ERROR_SERVICE_DOES_NOT_EXIST
YYYY-MM-DDThh:mm:17.246+TZ| USBDeviceInstUtil-build-24896162| I0: VMUSBArbService service not running
YYYY-MM-DDThh:mm:19.444+TZ| USBDeviceInstUtil-build-24896162| I0: --- VMPrepDeviceInstall(): Preparing for device driver installation
YYYY-MM-DDThh:mm:19.444+TZ| USBDeviceInstUtil-build-24896162| I1: MsiUtil_GetPropertyString: Getting Property CustomActionData = C:\Program Files (x86)\Common Files\VMware\USB\DriverCache\
YYYY-MM-DDThh:mm:19.444+TZ| USBDeviceInstUtil-build-24896162| I0: Installing using drivers in: C:\Program Files (x86)\Common Files\VMware\USB\DriverCache\
YYYY-MM-DDThh:mm:19.584+TZ| USBDeviceInstUtil-build-24896162| I0: --- VMInstallUSB()
YYYY-MM-DDThh:mm:19.584+TZ| USBDeviceInstUtil-build-24896162| I1: MsiUtil_GetPropertyString: Getting Property CustomActionData = C:\Program Files (x86)\Common Files\VMware\USB\;5;Win8
YYYY-MM-DDThh:mm:19.584+TZ| USBDeviceInstUtil-build-24896162| I0: Installing USB drivers from: "Win8"
YYYY-MM-DDThh:mm:19.584+TZ| USBDeviceInstUtil-build-24896162| I0: ERROR: Failed to load vnetlib from "C:\Program Files (x86)\Common Files\VMware\USB\vnetlib.dll" [126]
VMware Remote Console
It happens because VMRC update process failed to update USB arbitrator service due to its internal version mismatch when using Windows. It won't happen if you're using Linux or Mac for VMRC.
Broadcom engineering team identified the root cause of the issue and confirmed that it's unique to updating from 13.0.0 or 13.0.1 to 13.0.2 on Windows, which means it won't happen in the next release.
Uninstalling existing VMRC and installing VMRC 13.0.2 will enable us to avoid the issue.