VMware App Volumes 2.18.4 | May 28 2020 | Build 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.4 release includes critical fixes.
App Volumes documentation is available in English.
Sometimes, if many files or folders are deleted when using a Writable Volume with one or more AppStack, a blue screen (BSOD) error occurs or applications from an AppStack or Writable Volume become inaccessible. 
When volumes are attached to a machine with a 32-bit operating system, a blue screen (BSOD) error might occur and the end user is unable to log in. 
App Volumes and McAfee anti-malware products freeze due to a deadlock condition when an AppStack is attached, and end users are unable to perform any activities. 
Failed to find volume and Volume does not exist in datastore errors are displayed in the System Messages tab of the App Volumes Manager after a Writable Volume on a shared datastore with multiple locations is successfully deleted from within the App Volumes Manager console. 
Writable Volumes created with profile-based templates on Windows 10 versions before 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 UEM 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.