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 - 2609

Pre-Delivery Validation for Local Copy

Runs pre-flight checks before delivering a package in local copy mode or to a physical endpoint. Checks cover disk space, and network bandwidth and reliability. Admin-configurable thresholds block on delivery. Users get clear remediation guidance and network throughput metrics, which means fewer failed deliveries and fewer help-desk tickets.

Multiple Markers

Lets administrators define their own markers beyond the CURRENT marker, assign multiple markers to an application, and set marker priority. Application Owners and Administrators can manage entitlements through marker assignments alone, or a combination of marker and inherited package entitlements.

Package Report Editor

Extends the Package Report Viewer so administrators can edit captured package content before deployment. It provides the opportunity to add and remove files, folders, and registry entries, and also allows administrators to make changes to package metadata and supporting package collateral.

Targeted Package Resync

Resyncs a single package instead of packages across all storage locations. This helps isolated package syncs and speeds up recovery in distributed environments and avoids a disruptive full global package resync.

Command-Line View of Attached Apps

Adds an agent command that lists the application status currently delivered to an endpoint. It shows each application's package state - Entitled, In Progress, Attached, Failed - with standard output or JSON formats. Support teams and application owners can confirm delivery without collecting logs or opening the console.

Bug in Windows 11 Causes Issues in App Volumes When Using Writable Volumes

Microsoft fixed a Windows bug in the October 2026 monthly maintenance. This bug causes Windows Explorer to crash at logon for App Volumes users with a UIA+profile or Profile-only Writable Volume, leaving the user with a black screen. The bug is present in Windows 11 versions 24H2 and 25H2 that Microsoft released in the seven-week period between late August and early October 2026.

For more information about the issue, see this knowledgebase article.

Resolved Issues for App Volumes 2609

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

• [AVM-48046] In a multi-domain Active Directory forest, login fails when a user's UPN suffix does not exactly match a domain registered in App Volumes Manager. For example: the user's UPN is user@company.com, but only the child domain abc.company.com is registered. App Volumes Manager logs this mismatch as follows Unable to locate a valid configuration to use for domain.. As a result, smart card and UPN-based logins are rejected, even though a trust relationship exists.

• [AVM-47930] App Volumes Manager log shows the following message: Skipping assignment lookup for “user: [...]” on “computer: [...]” because computer already has appstack and user has writable volume to attach which is not supported yet when a user logs into a multi-session computer that already has a computer-assigned Writable Volume attached. However, App Volumes Manager treats the Writable Volume as an application package. As a result, App Volumes Manager skips the assignment lookup and does not deliver any applications to the user.

• [AVM-46816] In the local copy mode with SSL certificate validation enabled, communication between App Volumes agent and App Volumes Manager might fail if the default certificate that App Volumes Manager generates is used. This issue is caused by a problem with the default certificate generation process.

  Workaround: Generate a custom server certificate and use this certificate for communication with App Volumes Manager.

• [AVA-29431] In the local copy mode with the EnforceSSLCertificate parameter set to 1, even if certificate validation fails at the first attempt, subsequent attempts bypass the certificate validation failure and establish communication with App Volumes Manager despite the parameter still enabled.

• [AVA-29398] Desktop shortcuts are not visible for classic applications until desktop is refreshed manually.

• [AVA-29329] Converting an App-V package to an App Volumes package fails when the App-V package contains the tokenized variable Local AppData, or when file names in the App-V package contain URL-escaped characters.

• [AVA-29327] Application shortcuts do not appear on the desktop and Start menu after a package is virtualized, if the package is captured using versions earlier than App Volumes Agent 2111.
  This issue occurs because the package's JSON file does not include an on_demand_data section. This section is required to display shortcuts. The on_demand_data section is not available when the package is captured using the earlier versions.

• [AVA-29265] Converting an App-V package (using appcapture.exe convert) to an App Volumes package fails when the App-V package has an empty registry hive or contains the tokenized variable AppVComputerName.

• [AVA-29244] Shortcuts of an App Volumes package do not launch with UNC folder redirection. When Windows folder redirection is enabled, shortcuts stored in redirected folders such as Desktop, Documents, and Downloads fail to start. The package itself is delivered correctly, and applications can still be launched through executable paths and file type associations.

• [AVA-29108] After capturing a Microsoft Office application, the following dialog is displayed: Svoffice PostProvision' failed. Please collect log files for AppVolumes support. The dialog can be dismissed and packaging machine can be restarted. The capture also completes. Even though the capture appears to succeed, the application fails to work when launched.

  This issue occurs when using the following components with these versions:

  • App Volumes Manager and packages_template (.vhd or .vmdk), versions 2509 and later

  • App Volumes agent 2412 and earlier

  Workaround: Recapture the package using App Volumes agent 2503 and later.

• [AVA-29100] When using the /sourcefolder parameter with the vmdk2vhdconverter.exe standalone executable, the conversion process fails with the following error VMware PowerCLI is not installed. However, when using the /file parameter the conversion process completes successfully for a single VMDK file.

• [AVA-28749] NTFS-delayed write errors might occur on Windows 11 23H2 when the Fast Attach feature is selected when configuring the machine manager. This issue affects only application packages and not Writable Volumes. These errors are present in the Windows System event log. In the System event log, NTFS-delayed write errors can be identified by NTFS Event ID 141 (Delayed Write Failed) entries.

• [AVA-28709] With App Volumes agent 2512 and later, Autodesk applications, such as AutoCAD, are delivered through an App Volumes package with the following licensing error at application launch: This product has not been registered with the licensing service yet.

  This issue occurs only when Palo Alto Networks Cortex XDR (cyvrfsfd.sys) is installed on the same system as the Autodesk applications. A conflict between the App Volumes Replication Guard feature and the Cortex XDR file system filter driver resets the Autodesk license data file (AdskLicensingService.sds) to an empty state when the application package is attached. As a result, the licensing service finds no registered products.

  App Volumes agent 2506 and earlier are not affected.

  Workaround: On the system image, turn off Replication Guard by adding the following registry key, and then restart the machine: HKLM\SYSTEM\CurrentControlSet\services\svdriver\parameters /v EnableReplicationGuard /t REG_DWORD /d 0 /f

  Note: EnableReplicationGuard applies to the whole system. On non-persistent virtual machines, files that build up on the implicit Writable Volume are cleared automatically when the machine restarts.

• [AVA-28361] Application capture fails with the error Error during packaging while the capture is being finalized. This issue occurs due to a conflict between Microsoft Defender and finalizing App Volumes capture.

Known Issues for App Volumes 2609

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

• [AVM-48568] When you add an App Volumes Manager, version 2609, that uses a self-signed certificate to Horizon Console, the automatic push of the Horizon Connection Server certificate to App Volumes Manager can fail, even after you accept the certificate thumbprint. App Volumes Manager is added successfully, but published applications on demand cannot be launched until the certificate is pushed manually.

  Workaround: Perform the following steps:

  1. In the Horizon Console, navigate to Settings > Servers > App Volumes Managers.
  2. Select the newly added App Volumes Manager.
  3. Click Push Certificate.

  After the certificate push completes successfully, retry launching the application (published applications on demand). Manually pushing the certificate after adding App Volumes Manager restores the application launches.

• [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-29327] Application shortcuts do not appear on the desktop and Start menu after a package is virtualized, if the package is captured using versions earlier than App Volumes Agent 2111.
  This issue occurs because the package's JSON file does not include an on_demand_data section. This section is required to display shortcuts. The on_demand_data section is not available when the package is captured using the earlier versions.

  Workaround: Update or recapture the application package using the latest App Volumes agent version.

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

• [AVA-28409] An application configured for delayed download gets automatically downloaded when this application is in a Dependency or Install Order relationship with other applications, which are configured for automatic download.

  For more information about delayed download, see the Assign an App Volumes Application to an Entity section in the App Volumes Administration Guide at Omnissa Product Documentation.

• [AVA-28322] The Notepad++ application installed in base image takes a lot of time to uninstall (approximately 4-5 minutes) when App Volumes Agent is installed on the App Volumes agent machine and at least one application is virtualized.

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