VMware App Volumes 2.18.9 | February 09 2021 | 188.8.131.52
Check for additions and updates to these release notes.
What is in the Release Notes
The VMware App Volumes 2.18.9 release has bug fixes.
App Volumes documentation is available in English.
During a volume (.vmdk) replication if the volume’s metadata already exists in the destination location, then the volume replication fails. 
A remote printer when added to the agent computer which has a UIA+Profile Writable Volume attached, does not get deleted from the Control Panel’s Devices and Printers applets. Though the printer appears to be deleted, it reappears at the next logon.
This issue is resolved only for remote printers that are added after upgrading to App Volumes 2.18.9. 
When a virtual machine created with instant clones fails with a blue screen (BSOD) error, volumes (Writable Volumes or application packages) remain attached even after the virtual machine reboots. When a new user logs in, the user might see these volumes as separate disks in the Windows Computer Management control panel. 
When a Writable Volume created using the UIA + Profile template is deployed on a newer version of Windows 10, Start Menu items for some built-in Universal Windows Platform (UWP) applications such as Calculator or Sticky Notes might be missing.
This issue is fixed for Writable Volumes that are created in App Volumes 2.18.9 or later. 
AppCheck might report a WEBrick-related vulnerability in App Volumes Manager. 
NOTE: VMware has evaluated this issue and believes that App Volumes Manager is not impacted by the Ruby vulnerability as per CVE-2020-25613
When using Microsoft Outlook Cached Exchange Mode with a UIA-only type Writable Volume and no profile persistence solution such as VMware Dynamic Environment Manager or roaming profiles, a new .ost cache file is created in the user’s volume upon each login.
When many users are logging into their desktops simultaneously, Writable Volumes may not get created for a few users and they might not be able to log in to a desktop.
Note: This issue does not occur if the users already have an existing Writable Volume.
Workaround: The users must log in again or have an administrator pre-create the Writable Volume for the user.
A Writable Volume move or copy operation may fail when bulk operations are performed on many volumes.
Workaround: Retry the move or copy operation.
Multiple duplicate Writables are seen after upgrading from App Volumes 2.13.2 to App Volumes 2.18.
Workaround: See the Knowledge Base article 67482.