Fixed issues in 2203 LTSR CU1

Last published : Oct 20, 2026
Compared to: Citrix Provisioning™ 2203 LTSR initial release
Citrix Provisioning 2203 LTSR CU1 contains all fixes included in the 2203 LTSR initial release, plus the following, new fixes:
Related information
Cumulative Update 1 (CU1)

Citrix Provisioning console issues

  • Provisioned VMs do not inherit the EnableNestedVirtualization template property in Microsoft System Center Virtual Machine Manager (SCVMM) 2019 Rollup Update 1 and later versions.
  • Citrix Provisioning version 2203 might fail to work on Microsoft Azure when public access to the storage account is disabled.
  • The Citrix Virtual Apps and Desktops Setup wizard and target power management console fail when working with Azure. The issue occurs because Azure doesn’t support TLS1.0, which the current Provisioning Services release uses.

Citrix Provisioning server issues

  • Search for database servers located nearby using the Browse button might exclude some servers.
  • Citrix Provisioning server might not recognize available valid licenses for target devices if any of the licenses in the license server is expired or corrupt.
  • When you use Berkley International Naming Domain (BIND) 9.11.4 or later as the DNS server, attempts to start a Unified Extensible Firmware Interface (UEFI) target device might fail.

Citrix Provisioning target device issues

  • Insufficient resources might cause transient errors resulting in Citrix Provisioning target devices becoming unresponsive.
  • Citrix Provisioning target devices version 2106 might become unresponsive four days (96 hours and 5 minutes) after the device license becomes invalid. This error message appears:
    No device license is currently available for this computer. A system shutdown will be initiated in 96 hours. To avoid loss of data, save your work now and close all applications.
    This issue might be caused due to the problem covered by Fix CVADHELP-19711.
  • Target devices using async-IO vDisk crash after you rebalance or reconnect.
  • In the imaging wizard, the Boot Device Manager (BDM) configuration stage does not work with Windows Server 2016 on a public cloud.
  • Citrix Provisioning target VMs in Azure might use the Azure temporary disk for the cache instead of the dedicated cache disk. The issue occurs when the temporary disk is larger than the selected vDisk.
  • Citrix Provisioning server failover takes a long time when you use a 2203 target device.