Updated on: 18 JUN 2020 VMware Tools | 18 JUN 2020 | Build 16303738 Check for additions and updates to these release notes. |
Hyewon bark September 16, 2020 at 9:18 pm. Regarding the above question, a Workstation 16 Pro license can be used to license VMware Fusion 12 Pro, and a Workstation 16 Player license can be used to license VMware Fusion 12 Player. Download the installer file It ought to most likely be in the download organizer as a matter of course, in the event that you have not changed the settings in your program. Record name ought to be something like VMware-workstation-full-15.0.0-10134415.exe.
windows.iso supports Windows 7 SP1 or Windows Server 2008 R2 SP1.
darwin.iso
supports Mac OS X versions 10.11 and later.linux.iso
, refer to VMware Tools 10.3.22 Release Notes.solaris.iso
, refer to VMware Tools 10.3.10 Release Notes.Important note about upgrading to ESXi 6.5 or later
Resolution on incompatibility and general guidelines: While upgrading ESXi hosts to ESXi 6.5 or later, and using older versions of Horizon View Agent, refer to the knowledge base articles:
VMware Tools 11.1.1 is available in the following languages:
The Guest OS Customization Support Matrix provides details about the guest operating systems supported for customization.
The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware Products. The VMware Product Interoperability Matrix of VMware Tools 11.1.0 can be applied to VMware Tools 11.1.1.
VMware Tools can be downloaded from the Product Download page.
The steps to install VMware Tools vary depending on your VMware product and the guest operating system you have installed. For general steps to install VMware Tools in most VMware products, see General VMware Tools installation instructions (1014294).To set up productLocker to point to the shared datastore, see KB 2004018.
For specific instructions to install, upgrade, and configure VMware Tools, see the VMware Tools Documentation page.
VMware Tools 11.1.1 supports the following driver versions on a Windows Guest Operating System.
Drivers | VMware Tools 11.1.1 |
Hardware Drivers | |
vmci | 9.8.16.0 |
vsock | 9.8.16.0 |
pvscsi | 1.3.15.0 |
wddm | 8.16.07.0008 |
vmxnet3 | 1.8.16.0 |
vmxnet2 | 2.2.0.0 |
vmmouse | 12.5.10.0 |
vmusbmouse | 12.5.10.0 |
vmaudio | 5.10.0.3506 |
efifw | 1.0.0.0 |
Software Drivers | |
vmrawdsk.sys | 1.1.5.0 |
vmmemctl.sys | 7.5.5.0 |
vmhgfs.sys | 11.0.42.0 |
vsepflt.sys | 11.1.1.0 |
vnetWFP.sys | 11.1.1.0 |
glgxi.sys | 2.3.0.0 |
giappdef | 2.3.1.0 |
Security DLL | |
vmwsu.dll | 2.5.0.0 |
NSX Network Introspection driver (vnetWFP) can cause OS crash during processing network connections, typically over loopback address. This behavior is seen in VMware Tools 11.0.0 and later versions.
This issue is fixed in this release.
Memory leak can be observed in NSX Guest Introspection drivers (vsepflt and vnetWFP) when installed in NSX environment. This can lead to customers reaching the memory limits on their respective systems after some time. This issue is seen in VMware Tools 11.0.0 and later versions.
This issue is fixed in this release.
VMware Tools for macOS contains a denial-of-service vulnerability in the Host-Guest File System (HGFS) implementation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the identifier CVE-2020-3972 to this issue. For more information, see VMSA-2020-0014.
This issue is fixed in this release.
After the upgrade, the NetworkIntrospection feature is not present in the system's VMware Tools MSI database, but the feature's vnetflt or vnetWFP driver service still exists.
Workaround:
Refer to KB 78016.
Note: Future tools upgrade from version 11.1.0 to a newer tools version will not have the issue.
Microsoft has changed Windows driver signing to use SHA-2 algorithm exclusively starting December 3, 2019. Hence, legacy Windows systems without SHA-2 code signing support fails driver signature verification.
Workaround:
Refer to KB 78708.
VMware Tools installation setup fails with a popup message: 'Setup failed to install the SVGA driver automatically. This driver will have to be installed manually.'
Workaround:
To workaround this issue:
Setup will complete successfully and retain the existing installed SVGA Driver. To reinstall the SVGA driver on a failed VMware Tools install, refer to KB1016770.
VMware Tools upgrade process hangs in a Windows Server 2008 VM. This happens because the 'vcredist' bundled in the tools installer gets stuck and does not return.
Workaround:
If you have Windows remote management interface to the VM in the guest network, then stop the process when it hangs, like 'c:vcredist_x86.exe' /quiet /noRestart -burn.unelevated BurnPipe.{32940ADA-3765-4E48-8624-3DB276BB8083} {D6A63D73-EE4C-4698-8D19-C926D5E854A4} 1088'.
You can also opt to stop the child process manually.
AppDefense driver glxgi logs an error in the event viewer similar to the following:
'The glxgi service failed to start due to the following error: A device attached to the system is not functioning.'
The events are observed when Guest Integrity is disabled.
Workaround:
These events do not impact the system and are safe to ignore.
When you have a secure boot VM with Microsoft Hyper-V and virtualization-based security enabled with Device Guard and Code Integrity policy set to enforced, then drivers, glxgi, pvscsi, vsepflt, and vsock might generate the event log warnings similar to the following.
Log Name: Microsoft-Windows-CodeIntegrity/Operational
Source: Microsoft-Windows-CodeIntegrity
Operational Log:
Warnings
Event ID: 3083
Level: Warning
Description:
Code Integrity determined kernel module system32DRIVERSvsock.sys that did not meet the WHQL requirements is loaded into the system.
Check with the publisher to see if a WHQL compliant kernel module is available.
Workaround:
These warnings are safe to ignore. The drivers load and operate in the normal manner.
Installation process might appear to be in progress and displays a message similar to the following:
'Preparing 'VMware Tools' for installation...'
During this process, the user might be prompted to restart the operating system.
Workaround:
For more information, see KB 55798.
Drag functionality fails to work in Ubuntu 16.04.4 32-bit virtual machine installed using easy install. Also, failure of copy and paste functionality is observed in the same system.
Note: This issue is applicable for VMware Tools running on Workstation and Fusion.
Workaround:
If the Shared Folders feature is enabled on a Linux VM while it is powered off, shared folders mount is not available on restart.
Note: This issue is applicable for VMware Tools running on Workstation and Fusion.
Workaround:
If the VM is powered on, disable and enable the Shared Folders feature from the interface.
For resolving the issue permanently, edit /etc/fstab and add an entry to mount the Shared Folders automatically on boot.
For example, add the line:
vmhgfs-fuse /mnt/hgfs fuse defaults,allow_other 0 0
The Desktop Hypervisor team is proud to announce the general availability of VMware Workstation 16 Pro and Player!
Quick links:
Workstation Evaluation Page
To recap some of the new features we’ve brought to this release: