VMware App Volumes 4, version 2103.4 | August 19 2021 | Build 188.8.131.52
Check for additions and updates to these release notes.
What is in the Release Notes
The release notes cover the following topics:
The VMware App Volumes 4, version 2103.4 includes new features, bug fixes, and known issues.
Added support for Microsoft Windows 11
For more information about this support, see the KB article 85960.
App Volumes documentation is available in English.
Replication fails to copy 2.x AppStacks with the following error: Replication to [DATASTORE] APPSTACK_NAME is missing required file [DATASTORE] APPSTACK_NAME.json 
Writable Volumes (2.x) are not automatically created for newly added members of an Active Directory group. 
Workaround: Create the Writable Volume manually for the user.
Instead of Writable Volumes being created before login in the background, the Writable Volumes are getting created at login causing delays in user login. 
When a UIA+profile Writable Volume is created on a Windows 10 VM and later deployed on a VM running a newer version of a Windows 10 OS, some of the Start menu items are missing. 
When an App Volumes configuration includes a UIA+profile Writable Volume, some of the Start menu items and application tiles are sometimes missing on a subsequent login. 
Users with a Profile-only or UIA+profile Writable Volume might lose recently changed registry values at logoff. This issue occurs because App Volumes agent is unable to close the user’s registry hive before detaching the volume. 
Applications packaged on Windows 11 are shown as packaged with Windows 10 in App Volumes Manager. 
When using Writable Volumes with Windows 11 and deleting files and folders, items are permanently deleted instead of being moved to the Recycle Bin. 
When creating Writable Volumes for a group with many users before user login (Delay check box is not selected), the Create Writable Volume page times out with a Server Timeout error. However, the background job for creating Writable Volumes continues to run and Writable Volumes are created for the group. 
Workaround: To continue performing further operations, refresh the App Volumes Manager Admin UI.
When many users are logging into their desktops simultaneously, Writable Volumes might not get created for a few users and they might not be able to log into a desktop. 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 might fail when bulk operations are performed on many volumes. 
Workaround: Retry the move or copy operation.
Invalid session cookie issue occurs intermittently at end user login or logoff and can be seen in the ACTIVITY -> System Messages tab of the App Volumes Manager UI. When the issue occurs during login, volume attachments might fail and the following error message is displayed on the agent computer: Volumes were not mounted due to an error on the server. 
Workaround: When the error occurs and login fails, the end user can log into the agent computer again. To disable the "Agent Session Cookie" settings, you can toggle the advanced setting in the App Volumes Manager UI. For more information about this issue, see the knowledge base article: https://kb.vmware.com/s/article/59666.
When a UIA+profile Writable Volume is attached, excluded programs fail in various ways when attempting to create or access files in C:\Users\<UserID> or any of its subfolders. 
NOTE: An excluded program is a program whose executable is in a folder which is excluded in snapvol.cfg or the program's executable itself is excluded in snapvol.cfg.
App-V packages do not load when App Volumes agent is used either with a UIA+profile or Profile-only Writable Volume. 
Sometimes, the applications that are packaged using App Volumes versions older than 2.18.2 have many redundant firewall rules. These rules can impact the end-user login time on agent computers where the application package is deployed.
This issue is fixed in App Volumes 2.18.2 and later. 
Workaround: If you are migrating an application package created in an App Volumes version earlier than 2.18.2 with such an issue, repackage the application after migrating to the target version.
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.