VMware App Volumes 4, version 2009 | 15 October 2020 | Build 126.96.36.199
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 2009 includes new features, bug fixes, and known issues.
- Extended support for App Volumes 4 with Horizon 7
Extended support is now available for App Volumes 4, version 2009 with Horizon 7.13. For more details, see the VMware Knowledge Base (KB) article, VMware Horizon 7 version 7.13 Support Plan.
- Customer Experience Improvement Program
App Volumes has joined the VMware Customer Experience Improvement Program to better understand what is most important to our customers.
Participation in this program is optional and encouraged as it will help VMware to guide the future development of App Volumes.
- Security Updates
This App Volumes release includes an update to jQuery.
Administrators might have to clear their browser cache before accessing the App Volumes Manager to ensure the new jQuery version takes effect.
- Documentation Updates
- Added new information to the Administration Guide to help explain how application assignments are resolved for specific users and computers based on a set of criteria: entity type, assignment type, length of the computer name’s prefix, and the date on which the application is assigned.
- Removed Windows 7 from system requirements in the Installation Guide.
App Volumes documentation is available in English.
During a volume (.vmdk) replication, if the volume’s metadata does not get replicated then the volume’s status is displayed as "Legacy" in the App Volumes Manager UI at the replication site. The volume’s attributes and corresponding Program icons and data might be missing from the UI. 
If kernel-mode CFG (Control Flow Guard) is enabled on Windows 10, a blue screen error (BSOD) occurs on reboot after installing App Volumes. 
Applications using ADS (Alternate Data Streams) fail because svdriver fails to identify the ADS in certain scenarios. 
In a Horizon VDI environment with a remote desktop running App Volumes agent that has a UIA-only Writable volume, while using the VMware Integrated Printing feature if the spooler service takes a long time to restart, the local printer to remote desktop mapping fails on a user’s second login. As a result, printers are not redirected to the remote desktops and the end users are unable to see any local printers. 
On a UIA-only Writable Volume attached to the App Volumes Agent, when a file is renamed with a long filename and the next time the file is opened by using the short filename, the file does not open. As a result, the corresponding application does not run correctly. 
Sometimes when a file or folder is renamed to an existing file or folder’s name on an application package or Writable Volume, the rename operation erroneously succeeds and the existing file or folder becomes inaccessible. 
An application might rename a file to a name that is not in the 8.3 format and later retrieve the alternate 8.3 name (for example, LONGFI~1.TXT or LO7B27~1.TXT) that was automatically added by Windows. When the application attempts to open the file by using the 8.3 name, the file open operation fails. For example, an application that has this issue was Scilab. 
In the presence of virtualized applications, such as ArcGIS, that have many HKCR subkeys, the “Insert Object” functionality in the Microsoft Office suite of applications is slow even when Office is installed on the base image. 
During storage group replication, if previously not imported to the database, AppStacks do not get imported to the storage group members and the database. However, the Import Storage Groups job completes without errors. 
During the installation of Microsoft Visual Basic 6 on a Windows 10 agent computer with a UIA-only Writable Volume, the HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Perflib\009 query run by the application fails. As a result, the administrators are unable to install Microsoft Visual Basic 6 on the agent computer. 
When the Program Files for a 32-bit application, which is deployed in an application package and attached to a 64-bit Windows agent, is not replaced by Program Files (x86) in the Run registry key at HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion and if the Run key is essential for this application, then the 32-bit application becomes unstable. As a result, the end user is unable to run the application. 
Computer start-up and user login requests using a SQL UPDATE with JOIN might cause SQL locking issues. As a result, Writable Volumes failed to attach when end users logged into their VDIs. 
Sometimes, after an upgrade to App Volumes 4, version 2006 from earlier versions of App Volumes 4, applications have missing icons. 
App-V packages do not load when App Volumes agent is used with an application package or UIA-only Writable Volume. 
When a Run registry key in an application package or Writable Volume uses an executable and the executable parameters have spaces or the executable path is specified by mentioning the name of the executable and not the complete path, then the registry key either does not execute or the key executes incorrectly with an error. 
When App Volumes agent and Dynamic Environment Manager (DEM) are deployed in the Horizon VDI environment with a Writable Volume attached to a user or computer and DEM configured in NoAD mode, DEM is unable to capture the user settings. As a result, user settings are not preserved across different login sessions. 
An application that requires a restart during a package update is not seen on the packaging computer after the restart. As a result, when an end user logs in, the end user is unable to find the application which has been installed before the restart. 
When more than 32 users log into an App Volumes published desktop in the RDSH environment, it results in a blue screen (BSOD) error on the RDSH server. 
When determining application assignment resolution, the criteria has been based on the entity type and the date on which the assignment is created. Users expected the priority criteria to include the length of the prefix of the computer name and assignment type (Package and Marker). As a result, packages attached to computers were unexpected because assignments created first were prioritized. 
App Volumes Manager can cache an invalid vCenter connection, which causes some App Volumes Manager-related administrative tasks to fail continuously until the App Volumes Manager service is restarted. As a result, administrators are unable to perform certain tasks on the App Volumes Manager UI such as deleting a Writable Volume. 
Occasional failure in deleting a user's Writable volume. As a result, the user is unable to delete the Writable Volume and create a volume. 
Computer-based assignments are not enabled at computer startup. Instead, the assignments are enabled at end-user 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. 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.
If you belong to one of the App Volumes Manager roles and delete the role assigned to the group to which you belong, you will not be able to log into App Volumes Manager again. 
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. 
Workaround: Reorganize the packages back to the correct Applications by using the Move functionality in the Inventory -> Packages tab of the App Volumes Manager UI and fix any missing metadata.
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. 
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.
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. 
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.
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. 
Workaround: Disable the Microsoft Windows feature, User Account Control (UAC) on the base image.
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.