Omnissa App Volumes 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

• General Availability: App Volumes Manager for Windows Endpoints

  App Volumes Manager now provides full Application Lifecycle Management (ALM) for physical Windows endpoints, unifying packaging, delivery, rollback, markers, and version governance across both physical and virtual environments.

  General Availability for Windows endpoints includes the following:

  • VHD + MSI in App Volumes Manager, enabling consistent capture, replication across file shares and compressed delivery across endpoints.

  • Local copy mode in the App Volumes Agent, ensuring reliable application delivery to physical devices while maintaining the App Volumes packaging and lifecycle model.

  This release significantly expands the Apps Everywhere strategy, giving organizations a single platform to manage their entire Windows application portfolio.

  Note:

  • Advanced lifecycle capabilities for physical endpoints require the Omnissa Apps Essentials license.

  • The VHD+MSI capability (and the related functionality such as Local Copy mode) requires App Volumes Manager to be configured with VHD In-Guest as machine manager. If your existing App Volumes Manager instance is configured with vCenter Server, you cannot perform an in-place upgrade and change the machine manager configuration to VHD In-guest.
    Instead, you must install a new App Volumes Manager instance and configure the machine manager as VHD In-Guest.

• App Volumes Agent Message for Background Package Delivery

  When newly assigned application packages begin downloading, the App Volumes agent now displays a lightweight notification indicating that applications are being prepared in the background. This notification improves clarity during app delivery, reduces user confusion, and helps prevent unnecessary help-desk tickets while allowing users to continue working uninterrupted.

• Windows Update Detection Before Application Capture

  App Volumes now checks whether Windows Update is enabled before application capture begins. If active, the administrator is alerted, preventing Windows Update artifacts from being included in the package. This results in cleaner, more predictable packages by avoiding OS-layer file contamination, metadata bloat, and version drift across Windows builds.

• Published Apps on Demand for Nutanix

  App Volumes now supports Apps on Demand for Horizon deployments running on Nutanix. Applications can be assigned dynamically and launched instantly without pre-provisioning, improving resource efficiency and enhancing the published application experience in Nutanix environments.

• Configurable App Volumes Manager Log Levels

  Administrators can now adjust App Volumes Manager logging levels without restarting services. This streamlines troubleshooting, reduces operational overhead, and maintains continuous service availability.

Resolved Issues for App Volumes 2512.4

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

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

Resolved Issues for App Volumes 2512

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

• [AVM-45428] Applications with missing App Links do not get synchronized to the target App Volumes instance even after the Sync Integrations background job runs multiple times. The application status for these applications is either Syncing App Links or Syncing Properties.

• [AVM-45130] Applications with VHD+MSI packages are not delivered to Windows endpoints which are configured in the Shared Storage package access mode.
  However, these applications are delivered correctly to Windows endpoints which are configured in the Local Copy package access mode.

• [AVA-27205] Multiple shortcuts of an application having the same name are not displayed in the Start menu when the application is delivered as on-demand.

• [AVA-27166] When icon index is more than the number of RT_GROUP_ICON resources, App Volumes agent fails to extract the application shortcut icon. As a result, the application when delivered on demand has blank shortcuts.
  Note: When the application is launched for the first time, the application shortcut icon is correctly displayed.

• [AVA-27071] End user experiences a delay when logging in or logging out of a Windows endpoint which has no network connection. The action eventually succeeds but there is a delay of approximately 5 minutes and the following message is displayed: Please wait for the svservice.

  This issue occurs when the Windows endpoint is configured either in the Local Copy package access mode or the Standalone mode. For more information about these modes, see the Choose Your App Volumes Deployment Model and Application Delivery Modes with App Volumes Manager sections in the App Volumes Install Guide at Omnissa Product Documentation.

• [AVA-26981] App Volumes applications using a local database and having intensive file open or file close operations might fail to run.

• [AVA-26750] The following error You cannot call a method on a null-valued expression is observed multiple times in the command prompt when the support.bat loglevels command is used. This issue occurs when only the App Volumes agent is installed in a virtual machine and not the Horizon agent.

• [AVA-25639] A file access or access denied error occurs when running a database-related application.

Known Issues

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.

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

  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.

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

  Workaround: Configure vCenter Server as the machine manager inApp Volumes Manager and ensure that the Mount ESXi option is not enabled.

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

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

  Workaround: The user must log into the same VM to access the Writable Volume. When the user logs out of the virtual machine, the Writable Volume can be used on another virtual machine.

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

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

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

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

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

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

• [AVA-28036] In a Horizon RDSH session, MSIX applications might fail to launch with the following error Windows cannot access the specified device, path, or file. This issue occurs when using App Volumes-packaged MSIX applications due to a race condition between App Volumes and an OS operation.

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

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

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

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

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