For VMWare, the VMWare Tools have been updated to version 12.4.5, more precisely 12.4.5.23787635. The release notes have been available since June 27th, but the tools were only uploaded today. So it will be a while before the automatic update appears.
Guest systems are supported from Windows 7 or Windows Server 2008. However, the last update already announced that this would be the last release with functions for Windows 32-bit guest operating systems. And new drivers are no longer being provided for Windows 7 or Server 2008 R2. So everything remains the same here. However, VMware Tools is still available as x86.
Another note: We are used to VMware Tools being installed in German. That will change with the next major update. Then, in addition to English, only French, Spanish and Japanese will be offered. All other languages will be dropped. But it's not that dramatic.
Fixes in VMware Tools 12.4.5
- The VMware Tools File Introspection driver running with a third-party antivirus solution without mediation capability may fail with a blue screen when scanning files for the Azure File Sync service. This error may occur under certain interoperability conditions with Azure File Sync due to a timing issue. This issue is fixed in this release.
- OpenGL applications fail with the error “IsWow64Process2 entry point not found” on Windows 8. This error only occurs with VMware Tools 12.4.0. This issue is fixed in this release.
- The service stops responding when you power on a virtual machine using VMware Tools 12.3.5 or 12.4.0. You can monitor this error in Application Logs in Windows Event Viewer. This issue is fixed in this release.
- By default, the VMware network script used by the power-on, suspend, and resume operations to manage the Dynamic Host Configuration Protocol (DHCP) leases logs to /var/log/vmware.log. The permissions on the log file are not set correctly, allowing non-root users to view the contents of the log file. This issue is fixed in this release.
- When you run the VMware Tools administrative installer, the Windows 8 build is copied to the same extraction location after the Windows 7 build and replaces the Windows 7 vsepumc.dll. This does not affect installations because the correct vsepumc.dll is installed. This issue is resolved in this release.
Some updates have been made to the driver:
- The OpenSSL version has been updated to 3.0.13.
- The zlib version has been updated to 1.3.1.
- The glib version has been updated to 2.79.1.
- The glibmm version has been updated to 2.76.0.
- The version of libxml2 has been updated to 2.12.5.
- The xmlsec version has been updated to 1.3.3.
- OpenGL 4.3 emulation support for x86 and x64 graphics applications on Windows Arm guest operating systems.
Open problems:
- When you run the Ortec application, you may experience memory consumption increasing and a memory error. Workaround: To avoid this problem, set the system environment variable to zero – SVGA_ALLOW_LLVMPIPE=0
- If the Shared Folders feature is enabled on a Linux VM while it is powered off, mounting the shared folders will not be available upon reboot. Note: This issue applies to VMware Tools running on Workstation and Fusion. When the VM is powered on, disable and enable the Shared Folders feature through the UI. To permanently fix the problem, edit /etc/fstab and add an entry to automatically mount the Shared Folders at boot time. Ex.
vmhgfs-fuse /mnt/hgfs fuse defaults,allow_other 0 0 - Microsoft has changed Windows driver signing to use the SHA-2 algorithm exclusively as of December 3, 2019. Driver signature verification will fail on older Windows systems without SHA-2 code signing support.
- When you install a Windows Vista, Server 2008, or Windows 7 operating system in a virtual machine with a boot disk on a PVSCSI controller, the required PVSCSI driver is not installed.
- When upgrading VMware Tools to a new version, if the previous version's VMware Tools service is not completely removed, this incomplete removal of the service will cause the new VMware Tools version's service installation to fail, resulting in a fatal upgrade error.
- If an incomplete service removal is detected, to prevent the VMware Tools upgrade from failing every time, the creation of the new service is paused and retried to see if the condition is resolved. The VMware Tools installer pauses for up to 2 1/2 minutes, after which a fatal error occurs. If the condition is met, the upgrade continues with the creation of the new service. Workaround: Restart the Windows system and start the VMware Tools installation again.
- 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 is still present. This issue only affects VMware Tools upgrades from versions earlier than 11.1.0.
Information and downloads:
Thanks to gur_helios for the tip.