| VMware App Volumes 2.18.1 | 18 February 2020 | Build 2.18.1.10 Check for additions and updates to these release notes. |
What is in the Release Notes
The VMware App Volumes 2.18.1 release includes the following bug fix and known issues.
Internationalization
App Volumes documentation is available in English.
Resolved Issues
When the Writable Volume Regular Backups feature is enabled, Writable Volumes are not getting backed up to the storage path correctly. Administrators must schedule the backups when a user logs off. [2474885]
Known Issues
Writable Volumes created with profile-based templates on Windows 10 versions prior to 1803 may exhibit Start Menu or search-related issues after using the same volume on Windows 10 versions 1803 or later.
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 may 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 a large number of 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.
