VMware App Volumes 2.18.2 | 17 March 2020 | Build 22.214.171.124
Check for additions and updates to these release notes.
What is in the Release Notes
The VMware App Volumes 2.18.2 release includes bug fixes and known issues.
Customers using Writable Volumes must not install VMware App Volumes 2.18.2, but instead upgrade to VMware App Volumes 2.18.4 or later.
App Volumes documentation is available in English.
Chrome fails with an "Aw, Snap!" error due to compatibility issues with Chrome version 78 and later. 
On the first attempt, an online file is not accessible when using OneDrive with Writable Volumes template type UIA + Profile and Profile-Only. 
End users see an error that license activation has failed after launching any Microsoft Office 365 application from the Windows image while any AppStack is attached. 
In the App Volumes Manager administration console, on the DIRECTORY > Users page, the data table by default is sorted as per the “Last Login” column. After using any other column for sorting, the “Last Login” column can no longer be used for sorting purposes. 
AppStacks and Writable Volumes are not attached and a
Lock request time out period exceededODBC error is logged when many users log in or computers boot over a short period of time. This NTLM authentication failure happens when an App Volumes Manager attempts to update the ‘domain_controllers’ table in the SQL server database in rapid succession. 
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.
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.