Known issues

Last published : Oct 19, 2026
The following issues have been identified in this release:
  • A 400 Bad Request error might occur when a user attempts to replay recorded sessions using the Session Recording player or web player. The issue can occur when the user is a member of too many Active Directory user groups. To work around this issue, complete the following steps:
    1. Go to the IIS server machine where the Session Recording server is installed and add the MaxFieldLength and the MaxRequestBytes DWORD values under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters.
    2. Set the DWORD values to 65534 in decimal.
    3. Restart the IIS server machine.
  • Session Recording might not function properly. The issue occurs with CU3 and CU4 and is resolved in CU5 and later versions.
  • If you are using Citrix Web App Firewall (WAF) signatures to mitigate in part the CVE-2021-44228 vulnerability, Session Recording might not work as expected. To resolve the issue, exclude the IP addresses of your Session Recording servers from the mitigate_cve_2021_44228 policy on the NetScaler side.
  • A domain user with local administrator privileges on the Session Recording policy console can add local and domain users to which the action of a policy rule applies. However, a local user with local administrator privileges can add only local users but not domain users.
  • The web player might not work properly if you upgrade it from Version 2009 or earlier. To work around the issue, clear your browser cache.
  • Rules of custom policies might be lost after you update Session Recording from the version included in XenApp and XenDesktop 7.6 LTSR to the latest version. As a workaround, update the software to the version included in the latest CU of XenApp and XenDesktop 7.15 LTSR and then update it to the latest release.
  • When Machine Creation Services™ (MCS) or Citrix Provisioning (PVS) creates multiple VDAs with Microsoft Message Queuing (MSMQ) installed, those VDAs can have the same QMId. This condition might cause various issues, for example:
    • Sessions might not be recorded even if the recording agreement is accepted.
    • The Session Recording server might not be able to receive session logoff signals and therefore, sessions might always be in a live state.
    For information about a workaround, see Install, upgrade, and uninstall.
  • Session Recording may experience performance issues when performing searches in the web or native player.