Omnissa App Volumes Release Notes

Omnissa App Volumes 2503.1 | August 21 2025 | Build 4.17.1.87

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 2503.1 Release Notes lists New Features, Resolved Issues and Known Issues for this release.

What's New

In this release, we have made a few updates containing general quality and performance improvements with no new features.

This release contains the following update:
Unified App Volumes Application Capture Command-Line Program parameters by removing the /appproductid option and standardizing the /upgradecode option. The /upgradecode option is mandatory when using the appcapture start command. As a result, All commands now consistently accept either a GUID or MSI path with the /upgradecode option.

Resolved Issues

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

[AVM-40912] App Volumes Manager incorrectly detected a production license as Evaluation mode.
Production licenses are now detected correctly.
[AVA-26461] Microsoft Office captured using an earlier version of App Volumes agent fails to start when an end user launches any of the Microsoft Office applications.
[AVA-26340] On Windows 11 24H2, App Volumes applications using the Electron framework silently fail to start; and App Volumes applications using Python fail to start, often with the following error: ModuleNotFoundError: No module named ‘encodings’.
[AVA-26339] Horizon Agent 8.14 (2412) and 8.15 (2503) processes crash during a Horizon Client reconnect if the Horizon configuration includes an App Volumes package which contains Visual C++ x64 runtime version 14.36.32532.0 or earlier.
[AVA-26065] When Firefox is set as the default protocol handler and the Firefox application package is delivered as on-demand, invoking the protocol handler results in the following message, Application not found, displayed even though the application is delivered to the user.
[AVA-25890] Microsoft Office applications captured with any version of App Volumes agent fail to launch correctly on App Volumes 2503 if the optional .NET framework 3.5 is installed on the OS.

Known Issues

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

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-47039]

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.
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-43565]
The following error is logged in App Volumes Manager when session hosts in a host pool are shutdown: 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. [AVM-36787]

Note: This error does not affect the end user.
Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606. [AVA-28403]

Workaround: Upgrade to App Volumes 2603.2 and later.

Resolved: This issue is now resolved in App Volumes 2603.2 and later.
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-27476]
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-26684]
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. [AVA-26575]

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.
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-26485]
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-26484]
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-26477]

Workaround: Set the package delivery mode to classic.
Microsoft Office captured using an earlier version of App Volumes agent fails to start when an end user launches any of the Microsoft Office applications. [AVA-26289]
Horizon Agent 8.14 (2412) and 8.15 (2503) processes crash during a Horizon Client reconnect if the Horizon configuration includes an App Volumes package which contains Visual C++ x64 runtime version 14.36.32532.0 or earlier. [AVA-25969]
Issues related to FSLogix are as follows: [AVA-25823]
- Logoff hangs when the FSLogix Cloud Cache feature is enabled.
- FSlogix app rules do not work for files and registry keys on system volumes.
Workaround:
Create a file %SVAgent%\Config\Custom\Snapvol.cfg and add the following:
```
#FSLogix exclusions
exclude_process_path=\Program Files\FSLogix
exclude_path=\Program Files\FSLogix
```
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-25243]
.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. [AVA-24547]

Workaround: If they are not deleted due to any issue, then you can navigate to the install directory and manually delete the files.
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. [AVA-24493]

Workaround: To use the RemoteApp, the end user must log out of the Remote Desktop client app and log in back again.
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. [AVA-23264]

Workaround: Add the following in the custom snapvol.cfg file: exclude_registry_value_path=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled.
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-20343]
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. [AVA-20264]
Applications cannot write large string values (several hundred thousand characters) to the registry. [3034063]
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. [2791414]

Workaround: Deactivate the Cloud Cache feature of FSLogix Office Container.
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. [2624048]

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 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. [2845852]

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")
```
A Writable Volume move or copy operation might fail when bulk operations are performed on many volumes. [2115593]

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.

Was this page helpful?