Omnissa App Volumes Release Notes

Omnissa App Volumes 2603.2 | June 15 2026 | Build 4.21.2.158 Omnissa App Volumes 2603.1 | May 25 2026 | Build 4.21.1.140 Omnissa App Volumes 2603 | April 14 2026 | Build 4.21.0.139 Check for additions and updates to these release notes.

Omnissa App Volumes is a real-time application delivery system that enterprises can use to dynamically deliver and manage applications.

Omnissa App Volumes Release Notes lists New Features, Resolved Issues and Known Issues for this release.

What's New - 2603.2

App Volumes 2603.2 is a maintenance release.

What's New - 2603.1

App Volumes 2603.1 is a maintenance release.

What's New - 2603

• Application Relationships

  Introduces support for application dependency, conflict, and precedence, enabling controlled and predictable application delivery across environments.

  • Application Capture with Prerequisites

    Prerequisite packages can now be delivered to the capture machine, allowing the application to be packaged with required dependencies present and referenced later through application relationships.

• VMDK-to-VHD Package Conversion

  Adds automated conversion from VMDK to VHD, enabling a consistent package format across physical, virtual, and cloud environments. VHD becomes the preferred format for modern deployments, offering greater portability and flexibility for hybrid use cases, while VMDK remains supported.

  This capability is available in prior releases; however, it is now significantly streamlined and enhanced to deliver a more efficient and enterprise-ready migration experience.

• MSIX Packaging Workflow Simplified

  Introduces a streamlined command-line workflow for MSIX packaging, reducing manual steps and simplifying large-scale package creation. This improves consistency and lowers the operational effort required to adopt and manage MSIX-based applications.

• Seamless In-Session App Updates

  Applications can now be updated without requiring user logoff or session restart. Previously limited and requiring additional configuration, this capability is now brought forward as a standard experience across both physical and virtual Windows environments.

• On Demand Delivery Selected by Default

  New packages created in App Volumes Manager now default to On Demand delivery instead of Classic. This aligns system behavior with the recommended delivery model and helps drive consistent adoption without requiring manual configuration.

Resolved Issues for App Volumes 2603.2

The number included after each resolved issue is used by the internal issue tracking system.

• [AVM-47039] A failed SyncIntegrationsJob can block subsequent synchronization requests initiated from an App Voumes integration (in the App Volumes Admin UI, Infrastructure → Integrations), thus preventing new integration synchronization jobs from getting scheduled and running successfully.

• [AVM-46820] A database migration failure might occur when upgrading to App Volumes 2512 and the following error is logged at C:\Program Files (x86)\CloudVolumes\Manager\log\svmanager_setup.log: CREATE UNIQUE INDEX terminated because a duplicate key was found.... This issue causes the upgrade to fail.

• [AVM-46677] App Volumes Manager reports the following database error Volume access mode is not included in the list, in the System Messages tab within the App Volumes Manager admin UI, when a new computer record is created during App Volumes agent startup.
  This error occurs because App Volumes Manager is unable to detect in which package access mode (shared storage or local copy) the App Volumes agent is installed on the computer. As a result, computer-based application assignments are not attached to the computer.

• [AVM-46349] Certificate validation fails after SSL certificate regeneration on the target App Volumes Manager instance. This issue occurs because the source instance retains the previously accepted certificate. This mismatch causes certificate validation to fail, resulting in communication failure between the source and target instances.

  Note: Clicking the Certificate button on the source instance does not retrieve the newly generated certificate — it continues to display the outdated certificate.

• [AVA-28403] Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606.

• [AVA-28332] App Volumes Application Capture Command-Line Program (appappcapture.exe) fails when using the appcapture.exe convert command to convert an App-V application package to an App Volumes VHD or VMDK application package.

• [AVA-28262] When capturing an application in the MSI format using the App Volumes Application Capture Command-Line Program (appcapture.exe), the MSI file does not get created whereas the VHD and JSON files are created successfully. This issue occurs because an invalid product version is generated for the application.

• [AVA-28258] An Invalid License Key warning dialog is seen, when any App Volumes agent version currently installed in Standalone mode, without an App Essentials license key, is upgraded to App Volumes agent 2603.1 using the App Essentials license key. Regardless of this warning dialog, the upgrade is successful and the App Essentials license key is also successfully updated.

• [AVA-27476] Applications such as Google Chrome Portable (installed per user) display a blank window or an "Aw, Snap!" error at first launch when using a UIA+profile Writable Volume.

Resolved Issues for App Volumes 2603.1

The number included after each resolved issue is used by the internal issue tracking system.

• [AVM-46820] A database migration failure might occur when upgrading to App Volumes 2512 and the following error is logged at C:\Program Files (x86)\CloudVolumes\Manager\log\svmanager_setup.log: CREATE UNIQUE INDEX terminated because a duplicate key was found.... This issue causes the upgrade to fail.

• [AVA-28046] App Volumes Direct installation fails when using the App Essentials license for install and the following error occurs: The License Key entered is invalid. Verify the format and ensure it matches the provided License Key. License Keys are 35 characters long and formatted as XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.

• [AVA-28036] Some issues occur when using App Volumes-packaged MSIX applications due to a race condition between App Volumes and an OS operation. The issues are as follows:

  • In a Horizon RDSH session, the MSIX applications might fail to launch with the following error: Windows cannot access the specified device, path, or file.

  • In a Dependency or Install Order Application Relationships scenario, if an MSIX application is the base or the first application, then as per the expected behavior, the MSIX application must virtualize first followed by the dependent or the second application respectively. Instead, the dependent or the second application might get virtualized even before the MSIX application. Neither relationship type is honored.

    Note: For Dependency, the expected behavior is when the base application fails to virtualize, then virtualization of the dependent application also fails.

Resolved Issues for App Volumes 2603

The number included after each resolved issue is used by the internal issue tracking system.

• [AVM-46052] "A ConnectionTimeoutError: Could not obtain a connection from the pool within... all pooled connections were in use" might occur due to a database connection leak when a large number of ESXi hosts are used for direct mounting of App Volumes packages.
  Direct mounting occurs when a vCenter Server is configured as the machine manager with the Mount ESXi option enabled, or when an ESXi (Single Host) is configured as the machine manager. This issue is more likely when the number of ESXi hosts are high.

• [AVM-45808] An end user cannot log into any virtual machine if their VHD Writable Volume stays attached after a virtual machine crashes.

  In VHD In-guest mode if a Writable Volume is attached and the VM crashes, the following might happen: If a Writable Volume is in use during the failure, the file share might not release the file handle from the crashed virtual machine. As a result, the user is prevented from using the Writable Volume on other virtual machines. If the Exception Resolution setting of the Writable Volume is configured as Block user login, the user cannot login into other virtual machines.
  
  When the Writable Volume is requested for a user and the unused file handle is released, the Writable Volume attachment is updated in App Volumes. The user can then use the Writable Volume in any virtual machine they log into. Administrators can configure the file share to modify the behavior of unused file handles.

• [AVM-45692] The Browse button for selecting a custom location fails to work when installing App Volumes Manager in the custom location (other than the default location). As a result, App Volumes Manager cannot be installed in the custom location.

• [AVM-45652] The launch of an on demand published application, which is delivered by App Volumes, fails in Horizon 2512 with the following error message The application could not be launched, possibly because it is missing or misconfigured. Contact your administrator for more information. This issue is seen with App Volumes 2512 and earlier.

• [AVM-45784] Application capture might fail because volumes do not mount on the capture VM when the VMDK Package Attachment Resiliency, an advanced setting, is enabled in App Volumes Manager.
  For more information about this setting, see the App Volumes Manager Configuration Settings page in the App Volumes Administration Guide at Omnissa Product Documentation.

• [AVA-27583] Direct Mode installation cannot happen in non persistent machine error occurs when the App Volumes installer (msiexec) is run in an elevated command prompt, without using the /qn (silent install) parameter, with DIRECT=1 and NONPERSISTENT parameter is not used.
  If DIRECT=1 and NONPERSISTENT is not used (or NONPERSISTENT=0), then App Volumes agent is installed in the Standalone mode. For more information about the parameters, see the Install App Volumes Agent section in the App Volumes Install Guide at Omnissa Product Documentation.

• [AVA-27418] The App Volumes agent incorrectly identified mapped network drives as local drives, causing unexpected folder-creation behavior.

• [AVA-27442] In some environments like Hyper-V, application capture fails with the following error: virtual disk delete failed: The process cannot access the file because it is being used by another process.

Known Issues for App Volumes 2603.1

The number included after each known issue is used by the internal issue tracking system:

• [AVA-28258] An Invalid License Key warning dialog is seen, when any App Volumes agent version currently installed in Standalone mode, without an App Essentials license key, is upgraded to App Volumes agent 2603.1 using the App Essentials license key. Regardless of this warning dialog, the upgrade is successful and the App Essentials license key is also successfully updated.

• [AVA-28403] Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606.

  Workaround: Upgrade to App Volumes 2603.2 and later.

  Resolved: This issue is now resolved in App Volumes 2603.2 and later.

Known Issues for App Volumes 2603

The number included after each known issue is used by the internal issue tracking system:

• [AVM-47039] A failed SyncIntegrationsJob can block subsequent synchronization requests initiated from an App Voumes integration (in the App Volumes Admin UI, Infrastructure → Integrations), thus preventing new integration synchronization jobs from getting scheduled and running successfully.

  Workaround: In the App Volumes Manager admin UI, navigate to Activity → Pending Actions. Identify whether any SyncIntegrationsJob job is in the Failed state. Before proceeding with further validation, configuration, or testing activities, delete all failed jobs.

  Resolved: This issue is now fixed in App Volumes 2603.2.

• [AVM-46820] A database migration failure might occur when upgrading to App Volumes 2512 and the following error is logged at C:\Program Files (x86)\CloudVolumes\Manager\log\svmanager_setup.log: CREATE UNIQUE INDEX terminated because a duplicate key was found.... This issue causes the upgrade to fail.

  Resolved: This issue is now fixed in App Volumes 2603.2.

• [AVM-46677] App Volumes Manager reports the following database error Volume access mode is not included in the list, in the System Messages tab within the App Volumes Manager admin UI, when a new computer record is created during App Volumes agent startup.
  This error occurs because App Volumes Manager is unable to detect in which package access mode (shared storage or local copy) the App Volumes agent is installed on the computer. As a result, computer-based application assignments are not attached to the computer.

  Resolved: This issue is now fixed in App Volumes 2603.2.

• [AVM-46349] Certificate validation fails after SSL certificate regeneration on the target App Volumes Manager instance. This issue occurs because the source instance retains the previously accepted certificate. This mismatch causes certificate validation to fail, resulting in communication failure between the source and target instances.

  Note: Clicking the Certificate button on the source instance does not retrieve the newly generated certificate — it continues to display the outdated certificate.

  Workaround:

  1. Navigate to the source App Volumes Manager instance and locate the target instance which has the certificate issue.
  2. To open the target instance, click Edit.
  3. To restore communication, review and accept the current certificate to restore communication.

  Resolved: This issue is now fixed in App Volumes 2603.2.

• [AVM-36787] The following error is logged in App Volumes Manager when session hosts in a host pool are shut down: Session: Request is missing session cookie. In the Azure Virtual Desktop environment, a session cookie is provided only when an end user logs into a computer. If a computer starts and shuts down without any end user logging in, then a session cookie is never set. This results in a 401 (unauthorized) error.
  This error does not affect the end user.

• [AVA-28403] Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606.

  Workaround: Upgrade to App Volumes 2603.2 and later.

  Resolved: This issue is now resolved in App Volumes 2603.2 and later.

• [AVA-28262] When capturing an application in the MSI format using the App Volumes Application Capture Command-Line Program (appcapture.exe), the MSI file does not get created whereas the VHD and JSON files are created successfully. This issue occurs because an invalid product version is generated for the application.

  Resolved: This issue is now resolved in App Volumes 2603.2.

• [AVA-28046] App Volumes Direct installation fails when using the App Essentials license for install and the following error occurs: The License Key entered is invalid. Verify the format and ensure it matches the provided License Key. License Keys are 35 characters long and formatted as XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.

  Important: There is no workaround. Upgrade to App Volumes 2603.1 and later.

  Resolved: This issue is now fixed in App Volumes 2603.1.

• [AVA-28036] Some issues occur when using App Volumes-packaged MSIX applications due to a race condition between App Volumes and an OS operation. The issues are as follows:

  • In a Horizon RDSH session, the MSIX applications might fail to launch with the following error: Windows cannot access the specified device, path, or file.

    Workaround: Wait for a few seconds to allow the OS to complete its operation and launch the application again.

  • In a Dependency or Install Order Application Relationships scenario, if an MSIX application is the base or the first application, then as per the expected behavior, the MSIX application must virtualize first followed by the dependent or the second application respectively. Instead, the dependent or the second application might get virtualized even before the MSIX application. Neither relationship type is honored.

    Note: For Dependency, the expected behavior is when the base application fails to virtualize, then virtualization of the dependent application also fails.

  For more information about application relationship types, see Understand Types of App Volumes Application Relationships.

  Resolved: This issue is now fixed in App Volumes 2603.1.

• [AVA-27476] Applications such as Google Chrome Portable (installed per user) display a blank window or an "Aw, Snap!" error at first launch when using a UIA+profile Writable Volume.

  Resolved: This issue is now fixed in App Volumes 2603.2.

• [AVA-24547] .tmp files are seen in the install directory when an upgrade rolls back in a persistent machine with active entitlements.
  These files do not affect any App Volumes operations. By default, these files are automatically deleted after the machine restarts.

  Workaround: If they are not deleted due to any issue, then you can navigate to the install directory and manually delete the files.

• [AVA-24493] If the CURRENT marker of the application is modified after the user launches the application in a session, RemoteApp launch silently fails in Azure Virtual Desktop.

  Workaround: To use the RemoteApp, the end user must log out of the Remote Desktop client app and log back in again.

• [AVA-26351] An OS junction point from a native folder that belongs to a banned list to a non-virtualized folder (such as %APPDATA% in configurations that do no use UIA+Profile Writable Volume or a Profile-only Writable Volume) does not work properly. Files written to the junction source do not appear in the junction target.

• [AVA-26353] In a multi-session environment, the error associated with the Microsoft Office application is also visible to users who are not assigned this application package. While the application does not behave as expected for the users assigned to this package, the error has no effect on users who are not assigned to the package.

• [2791414] When a Writable Volume and FSLogix Office Container are deployed together in a VDI, the FSLogix Office Container VHD is not created on an SMB file share. This issue occurs only when the Cloud Cache feature is enabled.

  Workaround: Deactivate the Cloud Cache feature of FSLogix Office Container.

• [2624048] 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.

• [2845852] When a remote printer is defined on a UIA+Profile Writable Volume and the printer is attached to its print server through a USB interface, the printer definition on the Writable Volume might get deleted on the next non-persistent logon.

  Workaround:

  On the system volume, add the following two scripts to %SVAgent%\Config\Custom\uia_plus_profile :

  OnPreLoadApp.bat: sc config spooler start= disabled net stop spooler OnPostEnableApp.bat: sc config spooler start= auto net start spooler
  

  If you already have the same script names on the Writable Volume, add the spooler commands to the scripts.

  When a script is present on a Writable Volume and in the system volume at %SVAgent%\Config\Custom\uia_plus_profile , App Volumes agent runs the script present on the Writable Volume and ignores the script on the system volume. To ensure that the App Volumes agent runs both scripts, you can add the following to the script on the Writable Volume:

  if exist "%SVAgent%\Config\Custom\uia_plus_profile\%~nx0"
  ("%SVAgent%\Config\Custom\uia_plus_profile\%~nx0")
  

• [2115593] 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 Volumes Documentation

• For information about how to install, deploy, and upgrade Omnissa App Volumes see Omnissa App Volumes Installation Guide.

• For information about how to configure and use Omnissa App Volumes see Omnissa App Volumes Administration Guide.

Omnissa App Volumes documentation is available at Omnissa Product Documentation.

Internationalization

App Volumes content is available only in English.

Support Contact Information

To receive support, access Customer Connect.

To file a Support Request in Customer Connect and via Cloud Services Portal, see How to file a Support Request in Customer Connect and via Cloud Services Portal -6000005.