VMware App Volumes 4, version 2012 | 07 January 2021 | Build 22.214.171.124
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 2012 includes new features, bug fixes, and known issues.
Metadata Import Improvements
Additional App Volumes 4 metadata is saved on the storage location along with the package. This metadata is also processed during a package import and the packages are automatically associated with their parent application. For more information about this behavior, see Understanding the Behavior of Imported Application Packages section in the App Volumes Administration guide.
App Volumes documentation is available in English.
When importing application packages, a new parent application is created for each imported package. If a package has been transferred from one App Volumes system and imported into another, some metadata that is associated with its application might not be transferred with the package. 
During a volume (.vmdk) replication if the volume’s metadata already exists in the destination location, then the volume replication fails. 
In an application package, when a file is created during capture and renamed using the 8.3 name of the target path, the file becomes inaccessible after the application is deployed. 
When updating an application package, the last imported VMDK file is used as the source file in the update process. Sometimes this VMDK file might be on a storage location, such as an NFS mount, accessed by a slow connection. As a result, the “copy” process slows down and the application package is thick provisioned instead of thin provisioned. 
When creating an application or updating an existing application and during Rescan, the application can sometimes be seen as missing in the App Volumes Manager UI. This intermittent issue occurs until the file cache expires (default waiting time is 30 minutes from the time of file cache creation). 
Even when the App Volumes database connections are offline, the health check URL returns an incorrect status code of 200. Instead, the health check URL must return a status code of 500. 
Application, Packages, and Programs inventory tabs take a long time to appear when loading a large number of items. 
Blue screen (BSOD) error is seen on an agent computer when a renamed directory is opened using the target path of the directory while the rename is in progress. 
When using a Writable Volume and adding a network printer from the Control Panel, sometimes, adding a printer might fail with the following error message: Windows cannot connect to the printer. 
When using In-Guest operation mode and capturing an application to a VHD on Windows 7, the Packaging in progress pop-up window fails to show on restart of the agent VM. 
Note: Support for Microsoft Windows 7 ended on January 14, 2020. See support.microsoft.com for more details.
When a virtual machine created with instant clones fails with a blue screen (BSOD) error, volumes (Writable Volumes or application packages) remain attached even after the virtual machine reboots. When a new user logs in, the user might see these volumes as separate disks in the Windows Computer Management control panel. 
When a user who does not belong to the administrator role tries to capture applications on the packaging machine, the user is either prompted for administrator credentials or the packaging machine goes blank. Only domain administrators or local administrators have the rights to capture applications on the packaging virtual machine. The user is now alerted with an appropriate pop-up message in the packaging machine. 
If an administrator installs Microsoft Office on the system volume, creates an application package with either Visio or Project, and applies maintenance updates to Office through Windows Update, then on a subsequent launch, Visio or Project is reconfigured and a reconfiguration dialog appears. This issue is fixed. It is no longer necessary to repackage the Visio or Project application or update their packages. 
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. 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.
App-V packages do not load when App Volumes agent is used either with a UIA+profile or Profile-only Writable Volume. 
Due to an issue in the browser‘s cache, after an upgrade to App Volumes 4, 2009, App Volumes Manager UI might display a string of text that contains the words “missing translation”. 
Workaround: After an upgrade to App Volumes 4, 2009, refresh the browser cache if and when you see missing translations on any page.
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 has been 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.
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. [2646276, 2675527, 2689736]
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.