XenApp and XenDesktop

Known issues

Known issues that are described in the 7.15 baseline, and in the CU1, CU2, CU3, CU4, CU5, CU6, CU7, and CU8 sections of this article continue to be present in CU9 unless they are included in the list of fixed issues.

Known issues in Cumulative Update 9

There are no new known issues in CU9.

Known issues in Cumulative Update 8

  • When using this VDA version, Citrix policies applied to a machine by OU can sometimes fail to apply. [CVADHELP-19826]

  • If the secure XML keys are not created in the registry, the local host cache database might be missing or corrupted. To recreate the local host cache databases, see CTX228758. [LCM-9660]

  • If StoreFront is installed on the same server as the Delivery Controller, attempts to upgrade Storefront after upgrading the Delivery Controller will fail. However, upgrading StoreFront succeeds if you upgrade Storefront before upgrading the Delivery Controller.

    As a work around, if you need to upgrade Storefront after upgrading the Delivery Controller, stop Citrix Telemetry Service before running the Storefront upgrade. [LCM-9706]

  • Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception. The issue occurs due to the Microsoft changes made on Azure. A private fix is available at CTX457802. [CVADHELP-18741]

Known issues in Cumulative Update 7

  • When attempting to update the Licensing CEIP option using the Set-LicCEIPOption cmdlet, the operation fails with a CommunicationError. As a workaround, the CEIP option can be enabled through Citrix Licensing Manager. For more information, see Knowledge Center article CTX220679.

Known issues in Cumulative Update 6

  • Citrix Workspace app 1912 and later does not support HDX-FlashRedirection, which is part of the XenApp and XenDesktop 7.15 LTSR CU6 release. HDX-FlashRedirection is available only with Citrix Workspace app 1911 and earlier. You can also use Citrix Receiver 4.9 LTSR with 7.15 LTSR CU6. [LCM-8140]

  • The CU6 release includes a later version of the Self-Service Password Reset service. The later version of the service introduces a new functionality that detects the security configurations of the central store. When you create the central store or the service on Windows Server 2008 R2, a warning dialog appears. The issue occurs because Windows Server 2008 R2 does not support SMB encryption and thus fails the security detection. The issue does not block further actions. As a workaround, create the central store and the service on Windows Server 2012 or later that supports SMB encryption. [LCM-8179]

  • Citrix Director might fail to enumerate policy information when you view session details associated with a 7.15 LTSR CU6 VDA. The issue occurs when the version of Citrix Director is earlier than VDA version 7.15 LTSR CU6. As a workaround, use Citrix Director version 7.15 LTSR CU6. Alternatively, modify the following registries on the VDA and then restart it.

    • Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\GroupPolicy

      Name: SaveRsopToFile

      Type: REG_DWORD

      Value: 1

    • Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\GroupPolicy

      Name: SaveRsopToMemory

      Type: REG_DWORD

      Value: 0

    • Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\GroupPolicy

      Name: SaveRsopToRegistry

      Type: REG_DWORD

      Value: 0


Known issues in Cumulative Update 5

  • Attempts to upgrade a Windows 7 VDA from 7.6 LTSR CU8 to this release might result in a fatal exception, displaying a blue screen. No workaround is available.

    Perform any one of the following workarounds when you upgrade a Windows 7 VDA from 7.6 LTSR CU8 to this release:

    • Uninstall 7.6 LTSR CU8 and then install 7.15 LTSR CU5.
    • Manually disable the Citrix WDDM driver on Windows 7 machines and then upgrade to this release. To disable the Citrix WDDM driver, perform the following steps:
      • Open Device Manager.
      • Click Display adapters and then expand the selection.
      • Right-click Citrix Display Driver (Citrix Systems - WDDM) and then select Disable. [LCM-6798]
  • On a VDA that is running Windows 7 or Windows Server 2008 R2, a VC++ error might occur when you launch an App-V application. The issue occurs because the App-V client relies on a specific version of VC++ 2013 to function.

    As a workaround, apply the Microsoft hotfix https://support.microsoft.com/en-in/help/4014009/march-2017-servicing-release-for-microsoft-desktop-optimization-pack. Alternatively, install the App-V client first and then install the Cumulative Update 5 version of the VDA. [LCM-6809]

  • Citrix Scout might fail to run health checks for Delivery Controllers that are running Windows 2008 R2. As a result, the following message appears: Check failed. The issue occurs when there is no internet connectivity on the Delivery Controller. As a workaround, download the check scripts and then run the scripts manually. For details, see the Knowledge Center article CTX263240. [LCM-6837]

Known issues in Cumulative Update 4

  • The custom admin scripts of the Citrix XenDesktop Admin module that targets PowerShell 2.0 might fail. The issue occurs because the module no longer supports PowerShell 2.0.

  • On the Spanish version of the Microsoft Windows operating system, the component initialization might fail. The issue occurs when you run the preliminary site tests while upgrading the Delivery Controller from any Version 7.6 Cumulative Update to Version 7.15 Cumulative Update 4.

  • Citrix Director might not display all the rows of records in the Trends tables. Director displays a limited number of records followed by an extra empty space. However, you can scroll down to find the remaining records. [LCM-5841]

Known issues in Cumulative Update 3

  • For a list of Citrix known issues with the Windows 10 October 2018 Update (v1809), see Knowledge Center article CTX234973.

  • In an AWS environment, Server VDA rollbacks to a XenApp and XenDesktop 7.15 LTSR CU2 image or snapshot might fail. As a workaround, extend the rollback timeout to a timeout value of 30 minutes with the following PowerShell cmdlet:

    Set-ProvServiceConfigurationData –Name ImageManagemntPrep_preparationTimeout –Value 30 [LCM-4364]

  • After you upgrade to XenApp and XenDesktop 7.15 LTSR CU3, a site upgrade failure might occur when the site’s License Server is not updated to the version that is released as a part of CU3. There are no notifications by the product installer during the upgrade. [LCM-5467]

  • After completing the XenDesktop wizard, the Machine Catalog in Studio is empty and the streaming IP address appears instead of the management IP address, which is incorrect. To use the management IP address, set the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices Name: UseManagementIpInCatalog Type: DWORD Value: 1


Known issues in Cumulative Update 2

  • On Windows 2016 VDAs, users logging in with smart cards might not be able to see all available users at logon. The issue is the result of the default size of the logon window, which is 600x520. For more information and a workaround, see Knowledge Center article CTX204070. [LCM-3951]

  • For a list of known issues with Windows 10 Redstone 4 (Insider Preview builds), see Knowledge Center article CTX231942.

  • After upgrading Citrix Studio to Version 7.15 Cumulative Update 2, the policies might not be localized. For more information, see Knowledge Center article CTX234711. [LC9613]

  • 7.15 LTSR CU2 sessions might launch as a black screen. The issue occurs with sessions running on XenApp and XenDesktop 7.15 LTSR CU2 and 7.17 VDAs when Profile Management is enabled. For more information and a workaround, see Knowledge Center article CTX235100. [LC9648]

Known issues in Cumulative Update 1

  • User-configurable registry keys such as picadm and MultiStreamIca under HKEY_LOCAL_MACHINE might be deleted or overwritten by the default value while installing Cumulative Updates. [CVADHELP-16481]

  • The StoreFront management console does not open after an upgrade to StoreFront 3.12.1000 (XenApp and XenDesktop 7.15 LTSR CU1) from StoreFront 3.12 (XenApp and XenDesktop 7.15 LTSR), or after an install of StoreFront 3.12.1000. The StoreFront management console displays the error “MMC could not create the snap-in. The snap-in might not have been installed correctly.” To work around this issue, follow the steps described in CTX233206. [LC8935]

  • When installing a driver signed with a SHA-256 certificate on a Windows 7 or Windows Server 2008 R2 machine, a Microsoft WHQL (Windows Hardware Quality Labs) message might appear. To resolve the issue, install the following Microsoft hotfixes on the machine:
  • When the Citrix Telemetry Service is disabled or stopped, and you use a metainstaller to upgrade XenApp and XenDesktop 7.15 LTSR to Cumulative Update 1 (CU1), the following warning message might appear: “We cannot start the Citrix service that enables you to enroll in Call Home. See CTX218094 for guidance.” [LCM-3642]

  • Profile Management can cause a black screen to appear when you attempt to launch a Microsoft Windows 10 session. With this fix, you must configure the policy “Directories to synchronize” and add the folder “*AppData\Local\Microsoft\Windows\Caches*.” For additional information and a workaround, see Knowledge Center article CTX234144. [LC9030]

Known issues in 7.15 LTSR (initial release)

The XenApp and XenDesktop 7.15 LTSR release contains the following issues:


  • If SAS notification* is enabled, a user with multiple monitors connecting to an existing session at the console might find the monitor layout is not restored correctly. For example, if the right monitor is 1 and selected as the main monitor and the left monitor is 2, the user might find the positions swapped when reconnecting. This issue affects only RemotePC users with a physical desktop. This is due to incompatibility between two features. [CVADHELP-14249]

    * SAS notification is the feature that announces to a console user on RemotePC that another user is attempting to connect.


  • In Studio, when deleting one or more App-V applications from the Applications node, or from a selected Delivery Group, the message “An unknown error occurred” appears. You can safely ignore the message; the applications are deleted. [DNA-29702]

  • You cannot remove an App-V application from a Delivery Group if a child process launched for that application, but failed to close when the application closed. The error indicates the application is in use. To determine the process name, run Get-AppVVirtualProcess. Then end that process with Task Manager or Stop-AppVClientPackage. [DNA-23624]

  • When you remove an App-V package from the Application Library, it is removed from the Studio display, but not from the VDA. As a workaround, run the following cmdlets from the VDA, with elevated administrative privilege:

    Import-Module AppvClient Get-AppVClientPackage -all #Identify the PackageId and VersionId of the package to be removed Remove-AppVClientPackage -PackageId <packageid> -VersionId <versionid> [DNA-47379]

  • Due to the way that Microsoft App-V behaves, when you publish multiple sequenced versions of the same app using the single admin or the dual admin management method, only one version of the app is able to launch at a time per user on the VDA. Whichever version a user launches first, determines the version which runs later for them. The same behavior occurs even when Citrix components are not involved and the user starts the sequenced apps from desktop shortcuts which point to different paths. To date we (Citrix) have seen this occur for different versions of Mozilla Firefox and Google Chrome browsers. [APPV-60]

Citrix Director

  • In a multiple session environment, when you navigate to Filters > Sessions > All and log off from a session, the session logs off. When you select another session with the same user name for the second time and attempt to log off, this error message appears:

    Data source unresponsive or reported an error. View Director Server event logs for further information. [LC8826]

Install and upgrade

  • When you upgrade VDA 7.14 to VDA 7.15, the keys created under the registry key HKEY_LOCAL_MACHINE\Software\Policies\Citrix for Citrix policy settings that are applied using Administrative Template might be deleted from the VDA. [LCM-3876]

  • When installing components using the AutoSelect application on the installation media, the autorun.log file might contain errors and exceptions about insufficient rights. Provided the installation completed successfully, you can ignore these errors. However, to avoid them, launch AutoSelect using Run as administrator. [DNA-45937]

  • When upgrading a XenDesktop 5.6 deployment to XenDesktop 7.15 LTSR, group policy is missing. As a workaround, first upgrade from XenDesktop 5.6 to XenDesktop 7.13. Then upgrade from 7.13 to 7.15 LTSR [DNA-44818]

  • When installing a Controller and you select I want to connect to Smart Tools and Call Home on the Smart Tools page of the installation wizard, Call Home might not be enabled. As a workaround, either use the schedule feature in Citrix Scout or enable Call Home using PowerShell. [CAM-9907]

  • When installing a Delivery Controller on Windows Server 2012 R2 or Windows Server 2016, if you choose to connect to Smart Tools, and have more than one organization linked with your Citrix Cloud account, the logon process may not complete after you enter your Citrix Cloud credentials. As a workaround, complete one of the following:
    • Ensure the Windows Server and Internet Explorer have the latest updates.
    • Clear the Internet Explore browser option: Internet Options > Security > Local Intranet > Sites> Include all sites that bypass the proxy server. [CAM-9816]
  • If StoreFront was originally installed using the executable from the installation media, StoreFront does not appear as eligible for upgrade when you use the full-product installer for a later version. As a workaround, upgrade StoreFront using the executable from the installation media. [#DNA-47816]

  • When upgrading the Delivery Controller from a version earlier than 7.13, to version 7.13 and later, an error (exception) may be seen if the “Auto client reconnect timeout” setting is configured in any of the policies. This error happens if the “Auto client reconnect timeout” setting value is outside the permitted range 0 and 300, which was first introduced in version 7.13. To prevent this error, use the Citrix Group Policy PowerShell Provider to unconfigure the setting, or to set it to a value within the specified range. For an example, see CTX22947. [DNA-52476]

  • When you select machines and add them to existing Delivery Groups, Studio allows you to add machines from incompatible Machine Catalogs to the same Delivery Group. (If you first select a Delivery Group and add machines to it, Studio correctly prevents machines from incompatible Machine Catalogs being added.) [DNA-39589]


  • When MCS creates non-persistent machines in AWS, the DeleteOnTermination flag is set to True. However, upon power cycling, MCS re-creates new EBS volumes and swaps it with the old one which changes the DeleteOnTermination flag to False. [PMCS-4953]

  • When using a Federated Authentication Service in-session certificate to authenticate a TLS 1.1 (or earlier) connection, the connection can fail. Event ID 305 is logged, indicating an unsupported hash ID. The Federated Authentication Service does not support the SHAMD5 hash. To work around this issue, use TLS 1.2 connections. This issue affects XenApp and XenDesktop 7.9 through this version. [DNA-47628]

  • The policy settings are not saved in the Printer driver mapping and compatibility policy. As a workaround, use the Citrix Group Policy PowerShell Provider to edit this setting. For more information on the workaround, see CTX226589. [DNA-47423]

  • Windows Event Log Error: “Windows is unable to verify the image integrity of the file MfApHook64.dll”. For more information, see CTX226397. [HDX-9063]

  • When you start an application from StoreFront, the application might not start in the foreground or the application is in the foreground but might not have focus. As a workaround, click the icon in the task bar to bring the application to the front or in the application screen to bring it to focus. [HDX-10126]

  • Published content will not start successfully when initiated from Citrix Receiver. Content launched through the StoreFront web client (or Web Interface) launches as expected. [LC6316, RFWIN-4957]

  • When you delete an Azure Resource Manager machine catalog, the associated machines and resource groups are deleted from Azure, even if you indicate that they should be retained. [DNA-37964]

  • Multicast might fail to display video when using Citrix Receiver for Windows newer than version 4.6. Audio is still available. As a workaround, add this registry key on the endpoint:

HKEY_CURRENT_USER\Software\Citrix\HdxMediaStream; Name: DisableVMRSupport; Type: DWORD; Value: 4; [HDX-10055]


  • Stopping or restarting the Citrix Print Manager Service may leave the CpSvc.exe process in an unresponsive state. As a workaround, stop the CpsSvc.exe process before stopping or restarting the service in the Services snap-in, or restart the VDA to avoid this issue. [HDX-10071]

  • Universal Print Server printers selected on the virtual desktop do not appear in the Devices and Printers window in Windows Control Panel. However, when users are working in applications, they can print using those printers. This issue occurs only on the Windows Server 2012, Windows 10 and Windows 8 platforms. For more information, see Knowledge Center article CTX213540. [335153]

Session Recording

  • When Machine Creation Services (MCS) or Provisioning Services (PVS) creates multiple VDAs with the configured master image and Microsoft Message Queuing (MSMQ) installed, those VDAs can have the same QMId under certain conditions. This 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 Live status.

See the Session Recording installation articles for a workaround. [528678]

Third-party issues

  • Citrix and Microsoft have identified an issue when starting seamless applications from a Server VDA running Windows Server 2016. When a user starts an application published from this VDA, Citrix Receiver displays a black screen covering the workspace of the monitor for several seconds before starting the application. For more information, see CTX225819.

    Warning: If you are using Azure Active Directory (AAD), do not make the registry change described in CTX225819. Making this change may cause session launch failures for AAD users. [HDX-5000]

  • In a stress test environment, out of 20,000 logons, Microsoft Windows WinLogon.exe might crash intermittently with a frequency of <0.001%. [HDX-9938]