Why is my Citrix version different from what is installed?

Symptoms / Problem Description

In the console, the reported software name and version number for Citrix Workspace appear to be mismatched or conflicting. For example, an endpoint may show an apparent downgrade sequence where a higher version number updates to what looks like a lower version name (e.g., version 22.5.0.18 updating to software named Citrix Workspace 2203 with version number 22.6.0.60).

Cause

This behavior is expected and is due to how Citrix structures its versioning numbers between Current Releases (CR) and Long Term Service Releases (LTSR).

1. Citrix Versioning Schema

Citrix uses two different release tracks, which leads to overlapping version numbers:

• Current Release (CR): Follows a standard YYMM naming convention. For example, version 22.5.0.18 maps directly to Citrix Workspace 2205.

• Long Term Service Release (LTSR): Keeps the baseline version name of the original LTSR cycle (e.g., 2203), but continues to increment the actual build numbers for stability and security updates.

Because of this, an update to an LTSR release can have a higher underlying version number than a later Current Release, even though the software display name refers back to the LTSR baseline year and month (2203).

2. Version Mapping Example

As shown above, version 22.6.0.60 belongs to the 2203 LTSR track. It is a higher, newer build number than the standard 2206 Current Release (22.6.0.59), which explains why a device running 2205 would target this version.

Resolution

No action is required. This is a display characteristic of Citrix's native installer naming convention.

Note: The console does not generate or rename software versions installed on target endpoints. The system strictly reflects the specific software name and version string provided directly by the operating system's registry or the application package itself.