Product Documentation

Known issues

Nov 04, 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. 

XenApp and XenDesktop

The XenApp and XenDesktop 7.11 release contains the following issues:

  • Studio cannot connect to AppDNA 7.8 or 7.9 deployments. As a workaround, upgrade AppDNA to version 7.11.


  • After the installation completes and you open the Studio console (and do not close it) and click the StoreFront node in the left pane for the first time, the MMC snap-in might crash. As a workaround, reopen Studio.


  • During logon or logoff on a Windows 10 or Windows Server 2016 machine, the operation may pause and appear to be hung. Click in the session window to resume the operation.


  • When you install a VDA on a Windows 7 SP1 machine and decline participation in Call Home, the installation may fail with an error about the inability to load a Telemetry Service item. This occurs if the machine does not have .NET Framework 4.5.2 or later already installed. As a workaround, install .NET 4.5.2, restart the machine, and then install the VDA.


  • When launching a Universal Windows Platform application in a multimonitor environment, the application may not display properly and window functions may not work as expected. Server windows (such as Settings or Explorer) may launch with the application.


  • When using Universal Windows Apps, launching two applications in rapid succession may result in only one application launching. As a workaround, launch the next application only after the first application launches successfully.


  • Some applications with custom icons (BGR subtype) do not appear in StoreFront. As a workaround, edit the application's properties in Studio to assign a different icon.



  • A Windows 7 or Windows Server 2012 R2 VDA may crash due to a trap of the Windows Explorer application (explorer.exe). This is a third-party issue. There is no workaround.

    [#645105, #649937]

  • Anonymous user support is not available when using the Windows Server 2016 Release to Manufacturing (RTM) build. There is no workaround.


  • When using the NVIDIA 4.0 Driver on a desktop OS machine, switching from dual screen to single screen windowed mode causes a grey screen to appear. This is a third-party issue. As a workaround, use the NVIDIA GRID 3.1 R361 driver.


  • NVIDIA GPU accelerated hardware encoding (NVENC) in XenApp and XenDesktop 7.11 is enabled only when the framebuffer profile is 1GB or more. It is not enabled by NVIDIA for the 512MB framebuffer profile. This issue affects NVIDIA GRID GPUs used for vGPU including the M60, M10 and M6 cards. This is a known limitation (CTX217781). Application GPU acceleration remains fully supported and available with all profiles including 512MB. 


  • Exporting the Historic Machine Utilization report in PDF format works only when the Enable Process Monitoring value in the XenDesktop group policy is set to “Allowed”. As a workaround, select CSV or EXCEL report formats while exporting the Historic Machine Utilization.


  • The Monitoring policy setting, Enable Process Monitoring controls the collection and display of the Top 10 Processes on the Historic Machine Utilization page. If you enable and then disable this setting after a while, no process data is displayed. To view the process data, keep the value of Enable Process Monitoring as "Allowed" for the specific machine.


Other components

Components available separately on the XenApp and XenDesktop download pages have the following known issues.

Session Recording

  • Reinstallation of Administrator Logging by a user having securityadmin and dbcreator permissions on the SQL server might fail if Administrator Logging was previously installed by another user who has the same or higher SQL server permissions. Workaround: Reinstall Administrator Logging with a user who has sysadmin permission on the SQL server.

    [# 655644]

  • The installation of the Session Recording Server components fails with error codes 2503 and 2502. Resolution: Check the access control list (ACL) of folder C:\windows\Temp to ensure the Local Users and Groups > Groups > Users has write permission for this folder. If not, manually add write permission.


  • Because Session Recording does not support Framehawk display mode, sessions in Framehawk display mode cannot be recorded and played back correctly. Sessions recorded in that mode might not contain the sessions' activities.


  • You cannot record the Windows 7 desktop sessions correctly when Legacy Graphics Mode is enabled by XenDesktop site policy and Disk-based Caching is enabled by Citrix Receiver for Windows policy. Those recordings show a black screen. Workaround: Disable Disk-based Caching by deploying with GPO to the machines on which you installed Citrix Receiver for Windows. For more information about disabling Disk-based Caching, see and


  • The rollover setting does not apply to VDI desktop sessions for XenDesktop 7.8, XenDesktop 7.9, and Session Recording Agent. In those cases, each recording file has a maximum size limit of 1GB and activities are not recorded after that limit is reached. The rollover setting DOES apply to XenDesktop 7.11.


  • When Machine Creation Services (MCS) or Provisioning Services creates multiple VDAs with configured master image and Microsoft Message Queuing (MSMQ) installed, those VDAs might have the same QMId in certain conditions. This might cause various issues, such as:
    • Sessions mighty not be recorded even if the recording agreement is accepted.
    • The session logoff signal might not be received by the Session Recording server, which leads to the session always in Live status.

The workaround to create a unique QMId for each VDA differs depending on the deploy methods.

No extra actions are required if Desktop OS VDAs with the Session Recording agent installed will be created with PVS 7.7 or newer and MCS 7.9 or newer in static desktop mode; for example, configured to make all changes persistent with a separate Personal vDisk or local disk of the VDA.

For Server OS VDAs created by MCS or PVS or Desktop OS VDAs and configured to discard all changes when user logs off, use a script (GenRandomQMID.ps1) to modify the QMId at system startup. Modify power management strategy to ensure that enough VDAs are running before users' login attempts.

To use the script, do the following:

 1.   Make sure the execution policy is set to RemoteSigned or Unrestricted, in PowerShell.

Set-ExecutionPolicy RemoteSigned

2.     Create a scheduled task and set the trigger as at system startup and run with SYSTEM account on the Provisioning Services or MCS master image machine.

3.     Add the command as a startup task.

powershell .exe -file C:\GenRandomQMID.ps1

Summary of the GenRandomQMID.ps1:

1.      Remove the current QMId from the registry.

2.      Add SysPrep = 1 in HKLM\Software\Microsoft\MSMQ\Parameters.

3.      Stop related services, including CitrixSmAudAgent and MSMQ.

4.      To generate a random QMId, start services that stopped previously.

GENRANDOMQMID.PS1 for reference 복사

# Remove old QMId from registry and set SysPrep flag for MSMQ

Remove-Itemproperty -Path HKLM:Software\Microsoft\MSMQ\Parameters\MachineCache -Name QMId -Force

Set-ItemProperty -Path HKLM:Software\Microsoft\MSMQ\Parameters -Name "SysPrep" -Type DWord -Value 1

# Get dependent services

$depServices = Get-Service -name MSMQ -dependentservices | Select -Property Name

# Restart MSMQ to get a new QMId

Restart-Service -force MSMQ

# Start dependent services

if ($depServices -ne $null) {

    foreach ($depService in $depServices) {

        $startMode = Get-WmiObject win32_service -filter "NAME = '$($depService.Name)'" | Select -Property StartMode

        if ($startMode.StartMode -eq "Auto") {

            Start-Service $depService.Name




  • When recording a session with a resolution higher than or equal to 4096 x 4096, there might be fragments in the recording appearance.


  • When you change your XenApp or XenDesktop license type, the change does not take effect immediately for Session Recording. Workaround: Restart the VDA machine.


  • Limitation for Session Recording to support the Pre-Launched application sessions 
    • Problem:
      • If the active policy tries to match the application name, the application launched in the pre-launched session will not be matched, which results in the session not being recorded.
      • If the active policy records every application, when the user logs into the Windows Receiver (at the same time the pre-launched session is established) a notification for recording will appear and the empty session and any applications that will be launched in this session later will be recorded.
    • Workaround:
      • Publish the applications in separate Delivery Groups according to their recording policy. Do not use the application name as the recording condition. This will ensure pre-launch sessions will be recorded. However, notifications will still appear.