Cumulative Update 2 (CU2)

Last published : Nov 03, 2026
Release date: January 31, 2025
Related information
What's new

About this release

Known issues in this release
Citrix Product Subscription Advantage Eligibility Dates

Citrix Workspace app for HTML5

This release includes Citrix Workspace app for HTML5 24.11.0.51.

What's new in 2402 LTSR CU2

Modern experience - General availability

The new modern experience is now generally available for on-premises stores. This UI, which was previously available only for cloud stores, ensures a consistent look and feel across cloud and on-prem stores.
Modern experience on various devices
The new user interface is designed to enhance and simplify the end-user experience to access Citrix® apps and desktops. It reduces visual complexity, provides easy access to essential features, and refines the StoreFront app experience. It supports new features, such as Activity Manager that facilitate effective management of your virtual apps and desktop resources. Note: In this article, the current UI experience has been referred to as the classic experience.
To enable the modern experience, see User Experience.
The modern experience brings the following key improvements:
  • Activity Manager: Enables quick actions on active virtual apps and desktops, saving resources and optimizing performance. For more information, see Activity Manager.
  • Enhanced categorization of apps: Multi-level folder structures that are responsive to the user’s screen size. For more information, see categorization of apps.
  • Improved Search capabilities: New search capabilities provide for better and faster results. For more information, see Search feature.
For more information, see Modern experience.

Fixed issues since the technical preview

  • When you change the UI experience for an existing store, users connecting through locally installed Citrix Workspace app aren’t updated. They must remove the store and add it back to their app.
  • Activity Manager operations such as Logout, Disconnect, and more aren’t supported for applications that have App Protection policies enabled.
  • Citrix web extensions are not supported.
  • Direct SAML authentication using a web browser is not supported.
  • App protection for hybrid launches are now supported. Apps requiring App Protection are never displayed.
  • On {Citrix Workspace app for iOS, the user's initials aren’t displayed on the avatar.
  • On Citrix Workspace app for Windows, Mac and Linux when connecting via a gateway, after logging off, the Back to sign in option does not work. , ,
  • Activity manager cannot retrieve sessions from more resource feeds than can be enumerated concurrently.
  • In the Edit Receiver for Web Site screen, when Next generation experience is selected, settings are displayed that are not relevant to the experience.
  • Settings to hide the Already Installed option and prevent ICA® downloads are ignored.

Fixed issues in 2402 LTSR CU2

StoreFront 2402 LTSR CU2 contains all fixes included in CU1, and the following are the new fixes:
  • Adding custom footers to Receiver for Web site by inserting content with the customBottom ID of the StoreFront customization API might result in unexpected customization behavior.
  • After upgrading StoreFront 2402 to 2402 CU1, German-language device users might be unable to sign in to the Citrix Workspace™ app and Citrix Workspace web client on browsers. The sign-in page might load with no result.
    For more information, see CTX691873.
    Note that any Citrix Workspace app client that encounters this issue and goes into a bad state must be removed and re-added to the store.
  • When enabling ICA signing using the PowerShell command Set-STFStoreService $storeService -IcaFileSigning $true, the command doesn't set the necessary permissions on the certificate, causing ICA signing to fail.
  • End users can't launch the desktop if the published name contains non-English characters. The issue occurs after Citrix web extension is enabled.
  • During an outage, when the connectors go into Local Host Cache mode, StoreFront needs to send launch requests to the connector in the same zone as the resource. When a resource is available in multiple zones, previously, StoreFront would only try to launch the resource in one zone.
    With this enhancement, if the attempt to start a resource in one zone fails, in some cases StoreFront server tries to make another attempt to start the resource using connectors in other available zones to improve resilience.