Product Documentation

Known issues in XenApp 7.7 and XenDesktop 7.7

Jan 13, 2016

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

Caution: Editing the registry incorrectly can cause serious problems that may 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.

The following issues are known to exist in this release:

Installation and upgrade

  • If you upgrade from XenDesktop 5.6 to XenApp and XenDesktop 7.6 and then to XenApp and XenDesktop 7.7, users can open desktops but cannot launch applications. Workaround: Manually reset includedUsers on the upgraded Delivery Group’s access policy. [#605506]
  • Broker service initialization fails when you do an in-place upgrade from XenApp and XenDesktop 7.6 to XenApp and XenDesktop 7.7 after using the obsolete update-BrokerServiceConfig.ps1 script to enable the Linux VDA. Workaround: Install HotFix2 before upgrading. [#606649]
  • New RoleConfig is not always applied during upgrade. This results in zones not appearing in the Studio display.  Workaround: Run the following command in PowerShell (note the directory) [#610875]:
    PS C:\Program Files\Citrix\XenDesktopPoshSdk\Module\Citrix.XenDesktop.Admin.V1\Citrix.XenDesktop.Admin\StudioRoleConfig> Import-AdminRoleConfiguration .\RoleConfigSigned.xml


  • When you upgrade from XD Enterprise to Platinum, Delivery Group-based usage data and user-based usage data are inconsistent if the time range of your report includes the time that the upgrade took place. [#597138]
  • On Windows 10 VDA machines, applications launched by the user are not displayed in the Mini Task Manager for disconnected or reconnected sessions. [#603240]
  • When you edit a policy that has an active alert and you change the threshold value of that condition, the modified threshold value affects not only the new details of the alert but also the older details. [#602711]


  • On a Windows 10 desktop in a multi-monitor session, the default Display Settings application allows the user to manipulate the position of the monitors and apply the changes within a session. These changes cause erratic mouse behavior and make the session difficult or impossible to interact with. To correct the issue, disconnect then reconnect the session. To avoid the issue, prevent users from interacting with this application by using the Microsoft Group Policy: User > Administrative Templates > Control Panel > Display  > Disable the Display Control Panel. You can also use the registry setting:  HKLM\Software\Citrix\Graphics\SetNoDisplayCPLPolicy = 1; this registry value toggles the Microsoft policy On only during the session and then restores the original value. In both cases use of this policy also prevents the user from changing DPI and other display settings that may be required. [#571552]

Azure plug-in

  • Azure virtual machine (VM) naming constraints are different from Citrix Studio naming constraints. It is therefore possible to create Azure VMs with invalid names. To avoid this happening, adhere to the following rules for Azure VM names:

o   Must contain between 3 and 15 characters

o   Must contain only letters, numbers, and hyphens

o   Must start with a letter and end with a letter or a number

Warning: Names that do not adhere to these rules may still be allowed by Studio; for example, names starting with a hyphen or names that contain international characters. There is no mechanism for the plug-in to report invalid names back to the user interface. When a problem occurs, it will result in a significant failure and be reported as such.


  • XenApp and XenDesktop 7.7 supports a new always-on logging feature. As a result, existing trace levels have changed. Customers that use customized scripts to enable CDF trace collection may be affected. The new trace collection guidelines are as follows:

Previous trace level        

New recommended level






















  • If you use a XenApp and XenDesktop 7.7 Studio to manage a XenApp and XenDesktop 7.5 Site, you cannot edit the properties of a Delivery Group: an error message appears telling you that an internal error has occurred. Workaround: Use a XenApp and XenDesktop 7.5 Studio to edit Delivery Groups. [#605222]
  • If you log off through Connection Center from a Windows 10 VM-hosted application without having saved your work, application warning prompts may cause the session to freeze. Workaround: Save your work before logging off. [#547674]
  • Adding multiple Delivery Controllers to a Site simultaneously can fail to complete successfully, requiring restoration of the Site database from a backup. To avoid this, add Controllers to the Site one at a time, waiting for the successful completion of each Controller before attempting the next. [#607420]

Framehawk virtual channel

  • Session Recording/Smart Auditor are not supported with Framehawk.
  • Framehawk is not supported with high-end graphic intensive environments. It is tested for standard XenApp and XenDesktop workloads, such as knowledge worker and office apps.
  • Multimonitor clients are not supported at this time.
  • The Vd3dn.dll may crash on the client under test conditions, such as modifying bandwidth and latency on a WAN emulator in-session. Disconnect the session before making any changes to WAN emulator settings, then reconnect; Framehawk recalibrates during the session handshake.
  • If you enable policies for both Framehawk and legacy mode for the same user: on workstation OSs , the Framehawk policy setting  takes precedence; on server OSs, the legacy mode policy setting takes precedence.
  • A Framehawk session may experience session reliability issues due to a number of factors, including unplugging and reattaching a network cable while a session is active. [#592502]