| VMware App Volumes 2.18.10 | April 08 2021 | 2.18.10.10 Check for additions and updates to these release notes. |
What is in the Release Notes
The VMware App Volumes 2.18.10 release has security updates and bug fixes.
Internationalization
App Volumes documentation is available in English.
Resolved Issues
Occasional failure in deleting a user's Writable volume. As a result, the user is unable to delete the Writable Volume and create a volume. [2521454]
A user-initiated reboot during a package update, prior to the reboot requested by App Volumes as part of capture complete, results in App Volumes deleting any service present on the package. [2724792]
When aksfridge.sys, a driver from Aladdin Knowledge Systems, is present on a virtual machine with either a Writable Volume or an Appstack, a blue screen (BSOD) error occurs. [2734177]
Known Issues
AppCheck might report a WEBrick-related vulnerability in App Volumes Manager. [2712891]
NOTE: VMware has evaluated this issue and believes that App Volumes Manager is not impacted by the Ruby vulnerability as per CVE-2020-25613
Workaround: None.
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.
Workaround: Use a profile management solution.
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.
