Omnissa App Volumes Release Notes

Omnissa App Volumes 2509 | October 30 2025 | Build 4.19.0.98 Omnissa App Volumes 2509.1 | November 24 2025 | Build 4.19.1.103 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 for App Volumes 2509

• Unified Lifecycle Management for all Windows Endpoints (Technical Preview)

  App Volumes now provides a single unified platform to manage the complete lifecycle of applications across all Windows endpoints, whether connected or offline. Through App Volumes Manager, administrators can centrally manage application versions, rollbacks, and entitlements for both shared storage (connected) and local copy (offline) delivery models.

  For endpoints configured with local copy delivery, packaged applications are stored on the device and can be launched on demand even when the device is offline. When reconnected, the endpoint automatically updates entitlements managed by App Volumes, ensuring continuous and consistent application availability.

• Apps On Demand Integration with Workspace ONE Intelligent Hub

  App Volumes can now be connected to Omnissa Workspace ONE Intelligent Hub with Omnissa Access, allowing administrators to publish and manage App Volumes applications directly through App Volumes Manager. This integration enables applications and shortcuts to appear in a single catalog powered by Workspace ONE Hub Services where users can discover and launch apps on demand.

• Application Update and Uninstall within Active User Session

  Administrators can now configure App Volumes to notify end users when an application update or uninstall is triggered, allowing the process to complete within the same active session. This improvement removes the dependency on logoff or reboot cycles, ensuring faster application transitions and a smoother end user experience.

• Application Packaging without Mandatory Reboot

  Application packaging, whether initiated through the App Volumes Application Capture Command-Line Program or App Volumes Manager, no longer requires a mandatory system reboot to finalize the capture process unless the application itself mandates one. This reduces downtime and accelerates packaging workflows.

• Package Report Viewer

  A new Package Report Viewer functionality provides deeper visibility into captured content before finalization. Administrators can review and validate all files, directories, and registry keys within a package, with clear identification of restricted or excluded entries. Reports can be exported in both JSON and HTML formats for analysis or integration with automation workflows.

• Optimized VHD Package Size

  App Volumes now aligns VHD package sizes more closely with the footprint of natively installed applications. This optimization improves efficiency, reduces local storage consumption, and accelerates package download and update times. The improvement is particularly beneficial for endpoints using the local copy delivery mode, where each device stores a local version of the package.

• Selective App Link Activation

  Administrators can now selectively enable or hide individual application shortcuts and links. This provides fine-grained control over which application entry points are published in environments such as Horizon Published Apps or Amazon AppStream 2.0, ensuring a more streamlined end-user experience.

Resolved Issues for App Volumes 2509

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

• [AVM-43565] The following error is displayed in the System Messages tab and logs for a few application packages Error while refreshing Applications: Primordial OS is immutable and cannot be changed. when Rescan Applications action is performed. This issue occurs due to a mismatch in some package properties in the files associated with the package.

• [AVM-41466] When installing or upgrading to App Volumes Manager 2312.2 or later, though the Custom Setup window shows the correct custom directory path, after clicking Next, the Ready to Install the Program window incorrectly shows that App Volumes Manager will be installed in C:\Program Files (x86)\Cloud Volumes. Regardless, App Volumes Manager gets installed at the custom directory path, which is specified in the Custom Setup window.

• [AVA-26831] If a packaged application launches many processes quickly, one after another, svservice.log might contain a large number of nearly identical lines related to User Sentiment.

• [AVA-26575] An unwanted message for deleting user created virtual disks is displayed when upgrading the App Volumes Application Capture Command-Line Program. This message prompts the administrator to select Yes or No. Either action can be selected as the upgrade is not affected.
  The message reads as follows: The current installation of App Volumes Tools has – user -created vhd virtual-disk files in C:\ProgramData\Omnissa\AppVolumes\Packages. Click Yes to delete these files. Click No to retain them.

• [AVA-26684] Writable Volumes fail to attach for some users, and the following message is displayed: Volumes were not mounted due to an issue with your Writable Volume. Please try logging in again, or contact your administrator.
  This issue causes user login failures.

• [AVA-26485] Application icon is not captured for an application when using the App Volumes Application Capture Command-Line Program. As a result, the icon for the application is not displayed when this package is imported to App Volumes Manager.

• [AVA-26484] An MSI application package update might fail, or the application package might be handled incorrectly if more than one MSI package has the same version number.
  This issue occurs when a product version is not specified during an application capture using the App Volumes Application Capture Command-Line Program. As a result, a default version of 1.0.0.0 is assigned to the captured package. If multiple versions of the same application are captured without the product version, then the resulting packages have the same default version. To resolve this issue, the /productversion parameter can be used.
  For more information about this parameter, see the Windows Command-Line Arguments for the App Volumes Application Capture Command-Line Program section in the App Volumes Administration Guide.

• [AVA-26477] svservice stops running for some applications when the delivered package is on-demand. As a result, the user is unable to either see the application shortcut or the user does not receive the delivered application after launching the shortcut.

• [AVA-25243] When the CrowdStrike antivirus agent is installed on a machine running App Volumes agent, users might experience increased login time and delay in application virtualization.

• [AVA-23264] Running the change logon command on an RDS host does not work when application packages or Writable Volumes are attached to the RDS host. Status of the RDS host machine is not updated in the Omnissa Horizon console.

Resolved Issues for 2509.1

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

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

Known Issues for App Volumes 2509

The number included after each known issue is used by 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-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.
  
  Note: There is no workaround. You must upgrade to a later version of App Volumes.

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

  Workaround: Use VHD packages for delivering applications to the Windows endpoints in the Shared Storage package access mode.

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

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

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

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