Product Documentation

Known issues

Apr 04, 2018

The following warning applies to any workaround that suggests changing a registry entry.

Warning

Editing the registry incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

XenApp and XenDesktop

The XenApp and XenDesktop 7.17 release contains the following issues:

App-V

  • When App-V applications are disabled on the App-V management server, they are still listed in Studio in the App-V Publishing node, even though they cannot be used. To hide the disabled applications, restart Studio.  [#DNA-50304]
  • When you remove an App-V package from the Application Library, it is removed from the Studio display, but not from the VDA. [#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 subsequently 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]

Install and upgrade

  • An intermittent (observed when the Windows CEIP process runs nightly) StoreFront upgrade issue occurs during an upgrade from a 7.12 of later Delivery Controller. The following message is displayed:

"StoreFront cannot be upgraded because the following program is using some files. Close the program and try again.
Program name: CompatTelRunner"

To work around this issue, follow the instruction in the message. [#DNA-51341]

  • 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 a XenDesktop 5.6 deployment, group policy is missing. As a workaround, first upgrade from XenDesktop 5.6 to XenDesktop 7.13. Then upgrade to the current release. [#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 upgrading a Delivery Controller from version 7.15 CU1 to version 7.16, a Citrix licensing error message might appear. You can safely click OK and ignore this message. [#DNA-52820]

Director

  • Citrix Studio allows assignment of multiple Desktop Assignment Rules (DAR) for different users or user groups to a single VDA in the Delivery Group. StoreFront displays the assigned desktop with the corresponding Display Name as per the DAR for the logged in user. However, Director does not support DARs and displays the assigned desktop using the Delivery Group name regardless of the logged in user. As a result, you cannot map a specific desktop to a machine in Director.
    Workaround: To map the assigned desktop displayed in StoreFront to the Delivery Group name displayed in Director, use the following PowerShell command:
    Get-BrokerDesktopGroup | Where-Object { $_.Uid -eq (Get-BrokerAssignmentPolicyRule | Where-Object { $_.PublishedName -eq "<Name on StoreFront>" }).DesktopGroupUid } | Select-Object -Property Name, Uid [#DNA 53578]

General

  • If using HDX adaptive transport with Citrix Receiver for Windows in a LAN environment with NetScaler Gateway, we recommend that you upgrade to Citrix Receiver for Windows 4.10. Older Citrix Receivers might experience fragmentation issues with DTLS. [#HDX-2149]
  • Multi-stream (with or without multi-port) and session reliability UDP transport information might  appear incorrectly as inactive in the HDX monitor or in Director. This might occur when a session is using the multi-stream or multi-port with UDP transport. [#HDX-13416]
  • A stop error (blue screen) is intermittently observed during the installation of a 7.16 VDA on a Surface Pro 3 or 4. During installation, the Intel driver igdkmd64 stops responding. This is a third-party issue that impacts Intel GPUs: Intel 5000 HD, and Intel Iris 530. [#HDX-12662] 
  • 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]
  • 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]

  • When LogonUISuppression is enabled, users have these issues:
    • Users attempting smart card authentication cannot log on to use their published applications. 
    • Users are unable to change their passwords using CTRL+F1 >> Change password, and they cannot unlock their machine after locking their session using CTRL+F1 >> Lock.

As a workaround, disable LogonUISuppression. [#HDX-11413, #HDX-12465]

  • When a user starts a published application and immediately starts a desktop (or tries the reverse order), the second request might fail with the following error message: The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on. As a workaround, retry after a few seconds. [#HDX-12492]
  • After installing the Skype for Business Web App Plug-in, webcams might not be enumerated and meeting pages on Firefox might not refresh automatically. [#HDX-13288]

Printing

  • 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. [#HDX-5043, #335153]

  • The default printer might not be marked correctly in the printing dialog window. This issue does not affect print jobs sent to the default printer. [#HDX-12755]

Third-party issues

  • A VDA running on Azure might freeze, requiring a session reconnect. As a workaround, set udtMSS=1400 and OutbufLength=1400 in Azure environments. [#HDX-12913]
  • 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 https://support.citrix.com/article/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, HDX-11255] 

  • After starting a YouTube video using the YouTube HTML5 video player, full-screen mode might not work. You click the icon in the lower-right corner of the video, and the video doesn't resize leaving the black background in the full area of the page. As a workaround, click the full screen button, and then select theater mode. [#HDX-11294]

Other components

Components and features that are documented separately have their own known issues articles.