Product Documentation

Known issues

Sep 23, 2016

Feature Pack 3

  • In recent Firefox versions, the browser add-ons for URL redirection are disabled by default, so you must enable them. This is a third-party issue. [#283844]
  • Users cannot open some files from redirected folders such as Downloads and Desktop, if they downloaded the files using the Edge browser within a Windows 10 VDA. To work around this issue, use Internet Explorer to download files. [#591635]
  • The following registry keys are not present after upgrading a brokerless VDA to FP3, and must be added manually [#591030]:
    • hklm\software\citrix\VirtualDesktopAgent\HaModeComputerName
    • hklm\software\citrix\VirtualDesktopAgent\HaModeTimeEnd
  • When using Receiver for Windows with a Wacom pen device on a Windows 10 VDA, if you lose the network connection, the cursor may fail to display once the session is reconnected (using Automatic Client Reconnection, ACR). To work around this issue, disconnect and reconnect the session. [#593516]
  • Persistent CDF tracing is not available if the Citrix Telemetry Service is running. To work around this issue, temporarily disable the Citrix Telemetry Service. [#593347]
  • There is an error in XenApp and XenDesktop 7.6 FP3, when you update an existing Windows 10 master image on XenServer to use the XenServer hotfix XS65ESP1010 with XenTools. [#593985]
  • Apps which are published from a Windows 10 VDA do not display their full borders when maximized [#593596]. To work around this issue, registry keys can be set for each application class. For example, to work around the behavior for Paint, you create the following key:




Note that you must add the Class Name for an application, not the application name. For example, for Paint add MSPaintApp. You can get the Class Name using a tool such as Spy++. For more information on Seamless Configuration Settings, see CTX101644.

  • Some "Learn more" help links may not redirect correctly to the current Product Documentation site ( To work around this issue, access the Product Documentation site directly. All documentation for 7.6 FP3 and earlier 7.6 feature packs is on the new Product Documentation site under XenApp and XenDesktop 7.6.
  • Temp files from the standalone VDA installation package remain in the VDA Operating System's temp folder after completion of the install. To work around this issue, manually delete the temporary files. [#594829]

Feature Pack 2

Linux Virtual Desktop

Rich-text formatting is lost when text is copied from an application within the session and pasted into an application outside of the session, and when it is copied from outside the session and pasted inside. [#0538497]

Host names (the host part of the fully qualified domain name, or FQDN) longer than 15 characters are truncated, preventing successful VDA registration. [#0544120]

Linux VDA registration status fails to change on the endpoint when resuming from hibernation. During a power cycle event, the endpoint fails to obtain an IP address, which prevents it from registering. [#0569303]

The Linux VDA does not currently support DNS lookup of realm mappings. [#0557555]

KDE-based applications appear unavailable in Linux VDA sessions. [#0568006]

Linux VDAs running RedHat Enterprise fail to connect if Quest authentication service is enabled and SELinux is in enforcement mode. [#0551761]

Framehawk Virtual Channel

Citrix Receiver for Windows (Version 4.3) and Citrix Receiver for iOS Classic (Version 6.0) are the only Receiver platforms currently supported.

Session Recording/Smart Auditor are not supported with Framehawk.

This release of Framehawk is designed for standard XenApp and XenDesktop workloads, such as knowledge worker and office apps. It has not been tested with high-end graphic intensive environments

Multi-monitor 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 session handshake.

If the Framehawk policy and the legacy policy are both enabled, the Framehawk policy takes precedence on Workstation operating systems (for example, Windows 7); for RDS environments (for example, Windows 2012 R2), the legacy policy is applied.

For Windows 7 environments, the initial XenDesktop 7.6 FP2 release of Framehawk does not provide touch support (for example, pinch and zoom), despite this functionality being present in a Windows 7 OS. Additionally, Windows 2008 R2 does not provide touch support.

StoreFront 3.0

For the StoreFront 3.0 known issues and fixed issues, see the StoreFront 3.0 documentation known issues and fixed issue.

HDX RealTime Optimization Pack 1.8

For the HDX RealTime Optimization Pack 1.8 known issues and fixed issues, see the Optimization Pack 1.8 documentation known and fixed issues.

Feature Pack 1

Session Recording

  • When Machine Creation Services (MCS) or Provisioning Services creates a VDA with configured master image and Microsoft Message Queuing (MSMQ) installed, the VDA has the same QMId as the MSMQ. 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. [#528678]

    The workaround to create a unique and persistent QMId for each VDA is to use a script. 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:\GenQMID.ps1


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.

Summary of the script:

  1. Generate the QMid based on the hash value of the machine FQDN.
  2. Stop related services, including CitrixSmAudAgent and MSMQ.
  3. Set the QMid in the registry.
  4. Start services that stopped previously to apply QMId's change.
This script is for reference Copy

function ConvertHexStringToByte($theString) 

$bytes = New-Object Byte[] ($theString.Length / 2) 
for ($i = 0; $i -lt $theString.Length; $i += 2) { 
$bytes[$i / 2] = [System.Convert]::ToByte($theString.Substring($i, 2), 16) 

return $bytes 

Try { 
# Get UUID of machine 
$strUUID = (Get-WmiObject -Class Win32_ComputerSystemProduct | Select-Object -Property UUID).UUID 

# Remove "-" 
$strUUID = $strUUID.ToString().Replace("-", "") 

# Convert string to bytes 
$UUID = ConvertHexStringToByte($strUUID) 

# Set UUID as QMId 
$new_QMID = $UUID 
} Catch { 
# IF exception occurred, just use MD5 digest of FQDN as QMID 

# Get FQDN 
$fqdn = [System.Net.Dns]::GetHostByName(($env:computerName)).HostName 

# Calculate MD5 hash of FQDN 
$md5 = new-object -TypeName System.Security.Cryptography.MD5CryptoServiceProvider 

# Set md5 digest as QMID 
$utf8 = new-object -TypeName System.Text.UTF8Encoding 
$new_QMID = $md5.ComputeHash($utf8.GetBytes($fqdn)) 

# Write new_QMID into registry 
Set-ItemProperty -Path HKLM:Software\Microsoft\MSMQ\Parameters\MachineCache -Name "QMId" -Value $new_QMID 

# Restart MSMQ to adopt new QMId 

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

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. [#524973]
  • When you change your XenApp or XenDesktop license type, the change does not take effect immediately for Session Recording. Workaround: Restart the VDA machine. [#532393]
  • You might receive an Installation failed error in the following two cases. You can ignore the message, but to avoid receiving the message, restart the machine before reinstalling the Session Recording components. [#544579]
    • Uninstalled the Session Recording components, and then reinstalled them without restarting the machine.
    • Installation failed and rollback happened, and then you tried to reinstall the Session Recording components without restarting the machine.
  • Limitation for Session Recording to support the Pre-Launched application sessions [BUG0561109]
    • 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.
  • When recording a session with a resolution higher than or equal to 4096 x 4096, there might be fragments in the recording appearance. [#524973]
  • When you change your XenApp or XenDesktop license type, the change does not take effect immediately for Session Recording. Workaround: Restart the VDA machine. [#532393]
  • You might receive an Installation failed error in the following two cases. You can ignore the message, but to avoid receiving the message, restart the machine before reinstalling the Session Recording components. [#544579]
    • Uninstalled the Session Recording components, and then reinstalled them without restarting the machine.
    • Installation failed and rollback happened, and then you tried to reinstall the Session Recording components without restarting the machine.
  • When recording a session with a resolution higher than or equal to 4096 x 4096, there might be fragments in the recording appearance. [#524973]
  • When you change your XenApp or XenDesktop license type, the change does not take effect immediately for Session Recording. Workaround: Restart the VDA machine. [#532393]
  • You might receive an Installation failed error in the following two cases. You can ignore the message, but to avoid receiving the message, restart the machine before reinstalling the Session Recording components. [#544579]
    • Uninstalled the Session Recording components, and then reinstalled them without restarting the machine.
    • Installation failed and rollback happened, and then you tried to reinstall the Session Recording components without restarting the machine.
  • When recording a session with a resolution higher than or equal to 4096 x 4096, there might be fragments in the recording appearance. [#524973]
  • When you change your XenApp or XenDesktop license type, the change does not take effect immediately for Session Recording. Workaround: Restart the VDA machine. [#532393]
  • You might receive an Installation failed error in the following two cases. You can ignore the message, but to avoid receiving the message, restart the machine before reinstalling the Session Recording components. [#544579]
    • Uninstalled the Session Recording components, and then reinstalled them without restarting the machine.
    • Installation failed and rollback happened, and then you tried to reinstall the Session Recording components without restarting the machine.

Citrix Licensing 11.12.1

For the Citrix Licensing 11.12.1 known issues and fixed issues, see the Citrix Licensing 11.12.1 documentation known and fixed issues.

HDX RealTime Optimization Pack 1.7

For the HDX RealTime Optimization Pack 1.7 known issues and fixed issues, see the Optimization Pack 1.7 documentation known and fixed issues.

XenApp 7.6 and XenDesktop 7.6

General issues

The following note 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.
  • On Server OS machines, the CreateAnonymousUsersApp tool may not delete all anonymous user accounts from the local machine; all anonymous users are local users, not Active Directory users. Because the tool deletes passwords and profiles, any anonymous-user account names that are not deleted are no longer useable. To delete unwanted anonymous-user account names locally on the server, use Manage User Accounts or Computer Manager. [#4999679]
  • To configure a nonstandard HTTP/SOAP port for the Universal Print Server web service, use PowerShell cmdlets to change the session printer policy. For information about configuring Group Policy settings, see the Group Policy SDK usage section in the About the SDK document. To set the policy value, use:

    Set-ItemProperty LocalGpo:\Computer\Unfiltered\Settings\ICA\Printing\UniversalPrintServer\UpsHttpPort -name Value -Value <portnumber>. [#268593]

  • After a Hyper-V host is unpaused, Microsoft System Center Virtual Machine Manager (VMM) might not update the overall host state immediately. This can affect the use of Machine Creation Services (MCS). If one Hyper-V host reports a paused state, that host will not be used to provision Virtual Machines (VMs); if all hosts report a paused state, catalog creation will fail.

    As a workaround, manually refresh the parent cluster node or Hyper-V host node. Also, running environment tests on the host will identify hosts reporting a paused state. [#285696]

  • Brokering hosted applications on Desktop OS machines is not supported using the Remote Desktop Protocol (RDP). [#377108]
  • This release does not support mounting an .iso file when Client Drive Mapping (CDM) is configured for Windows 8 sessions. [#333111]
  • If the Citrix Universal Print Server fails because of bad drivers, try running those drivers under printer driver isolation. For information about how to configure printer driver isolation, see MSDN: [#381460]
  • The Enhanced Desktop Experience policy setting does not affect pre-existing user or administrator profiles. As a workaround, delete all pre-existing profiles before enabling/disabling the setting, and delete the profile used for VDA installation (after installing the VDA). If the built-in administrator's account was used for (Virtual Delivery Agent (VDA) installation, you cannot delete the profile. In that case, the user can choose the Citrix Enhanced Desktop Theme when logged on. {#363736]
  • If monitor resolution is affected because the VDA desktop session resolution exceeds the client monitor resolution, change the resolution setting on the VDA desktop to the highest supported value for the attached monitor. Alternatively, you can detach the monitor cables from the VDA graphics card. [#365877]
  • Screen savers and the power-save option are disabled in sessions. Edit the registry and create the following DWORD value:
    HKLM\Software\Citrix\Graphics\SetDisplayRequiredMode = 0
    This change does not prevent the remote machine screen saver or power save mode from coming on. If the power save mode comes on, the remote session is not updated until the user provides input (mouse/keyboard), but the screen will not be blanked. [#380550]
  • Attempting to use a PowerShell SDK New-ProvScheme command or any MCS command from a remote machine before setting the host admin address might result in an error. Set the admin address using the Set-HypAdminConnection command before running the New-ProvScheme command. [#336902]
  • This release does not support using this product with Microsoft RemoteFX vGPU feature in a Hyper-V host. Instead, use RDP to access RemoteFX functionality such as Hyper-V vGPU. [#375577]
  • Director reports the number of GPU machines that have failed to start in the Machine Failure panel on the Dashboard page. However, this information is not displayed when you drill down to view details on the Filters page.

    You can also view this information in the Historical trends graph. [#0434722]

  • If more GPU machines are provisioned or assigned than the XenServer resource pool can support of the GPU type specified, GPU machines may fail to start. Users assigned to a machine (including those using Personal vDisk) that failed to start may not be able to access their virtual desktop through StoreFront. [#0434505]
  • If you power on a GPU machine and it fails to start, you may see the following error message:

    Exception Failure in PowerOn, PGPU_INSUFFIENT_CAPACITY_FOR_VGPU

    This indicates that there are insufficient GPU Resources to start another machine that uses the GPU. [#434509]

  • If multiple users log on to a Desktop OS machine using RDP and ICA protocols and a user locks his/her RDP session, users connecting through ICA cannot log on to the session. To prevent this issue, users should disconnect or log off RDP sessions when they are finished. [#392311]
  • When you publish an application with a Windows 8 VDA host and the application shows non-ASCII characters in the notification area, other unrelated characters might also appear in the notification area after reconnection. To resolve this issue, log off from the session and then launch the application again. [#387963]
  • The ability to disable session sharing through a registry entry is not supported in this release. As a result, session sharing is always enabled. If the registry key is set to disable session sharing, the first application launches, but subsequent applications do not launch. There is no workaround for this issue. [#383718]
  • When a user reconnects to a disconnected session on Windows Server 2012, there is a memory leak in the Desktop Window Manager. If users connect and disconnect frequently to long-lived sessions, such as in the case of an employee using the same session from work and home, this can cause memory resources on the server to be reduced, eventually leading to slow response times and possibly even server failure. This is a third-party issue in the Microsoft code. For information, see: (to be published in July 2013). [#374261]
  • The Help About topics fail when working through Windows PowerShell 3.0. This is a third-party issue with Microsoft. Other help topics are unaffected. [#408866]
  • When upgrading from XenDesktop 5 to this release (or to XenDesktop 7.1 or XenDesktop 7.0), a hosted application assigned to both Shared and Private Delivery groups produces a Delivery Group incompatibility error during upgrade. To avoid this error, do not assign hosted applications to both Shared and Private Delivery Groups. [#419424]
  • If the Profile management feature is enabled, logon scripts for sessions running Windows Server 2012 R2 or Windows 8.1 are delayed by five minutes by default. Once the session is available, the Logon duration for logon scripts step is not available in Director. The delay is controlled by the Configure Logon Script Delay policy (Enabled = 0). [#407978]
  • Desktops may not launch on computers running Windows 8.1 with Microsoft Software Update Management installed. To avoid this, in the Windows 8.1 Taskbar and Navigation properties dialog box, on the Navigation tab, select all the options in the Start screen section. [#408439]
  • If you receive the error "You cannot access this session because no licenses are available" when you try to connect through Remote Desktop Protocol to a brokered session, disable these settings in C:\inetpub\wwwroot\Citrix\Store\App_Data\default.ica: [#422212 and #403855]
    • RDPConnection=false
    • RDP-RedirectDrives=false
    • RDP-RedirectDynamicDrives=false
  • The value for the Persistent Cache Threshold policy setting is labelled incorrectly, as Kbps, in Studio. The correct value is bits per second (bps). [# 429478]
  • When selecting a custom date range for a Configuration Logging report, the calendar displays might be incorrect. [#452399]
  • Machines provisioned on Amazon Web Services or CloudPlatform will not be suspended if their Delivery Group Power Management setting is set to Suspend when disconnected. [#453780]
  • Connection times (maximum connection timer, connection timer, and disconnect timer) might fail to work on Windows Server 2012 machines containing Windows Server OS VDAs, causing unexpected session time-out behavior. [#471698]
  • When the Auto-create generic universal printer policy setting is enabled, the Citrix Print Manager Service (CpSvc.exe) does not create the Citrix Universal Printer generic printer. Hotfixes that address the issue are available as Knowledge Center articles CTX141565 and CTX141566.
  • User connections to VDAs running Windows Server 2012 R2 might fail if the Maximum allowed color depth Citrix policy setting is enabled. The Maximum allowed color depth does not apply to VDA that use a Windows Display Driver Model (WDDM) driver as the primary display driver, such as VDAs running Windows Server 2012 R2. 

  • After upgrading XenDesktop, attempts to log off from a XenDesktop session might result in a blank desktop. The following error message appears:

    "Connection Interrupted
    Citrix Receiver will try to reconnect"


Installation issues

  • Error 1904. Module C:\Program Files (x86)\Citrix\System32\rpm.dll failed to register. HRESULT -2147010895. Contact your support personnel occurs when installing or upgrading the Virtual Delivery Agent (VDA) using the Citrix MetaInstaller, the installation of the third-party Microsoft Visual C++ 2005 Runtime component fails, rolls back, and then falsely notifies the MetaInstaller that the installation completed successfully. Because of this, the MetaInstaller continues to install any remaining VDA components until it reaches the post-install component initialization stage. You cannot continue without the Microsoft Visual C++ 2005 Runtime component being present at this stage. To work around this issue, rerun the MetaInstaller VDA installation, which then successfully reruns the Microsoft Visual C++ 2005 Runtime component installation. Alternatively, see and follow Microsoft's documented solution. [#489633]
  • Installing a Virtual Delivery Agent for Server OS might fail with error 1935 because of backward compatibility errors in the Microsoft Visual C++ 2005 Redistributable. See the Microsoft website or run Windows Update to check for fixes. [354833]
  • After a successful VDA for Windows Server OS installation, but before the machine restarts, the Windows event log might contain several error messages (such as TermService 1035 or 1036, indicating the Terminal Server listener stack was down or the session creation failed). If there are no other installation failure indicators, you can safely ignore those event log messages. [#374134]
  • When upgrading from XenDesktop 5.x, make sure that the XenDesktop 5.x Desktop Studio is closed before running the upgrade. Otherwise, Studio may close unexpectedly during the upgrade. [#389374]
  • When upgrading, an administrator who was disabled in XenDesktop 5.6 might move to the later version without a role or scope. Check the Administrators display in Studio and edit administrators, as needed. [#394765]
  • If you enable the Profile management feature and users find that their default Windows 8 applications (such as Weather, News, and Bing) start the first time they log on, but not after subsequent logons, you might have to reconfigure this feature. This issue has been observed in environments where the user profile is not persisted and if the folder AppData\Local has not been excluded (the default). As a workaround, add the folders AppData\Local\Packages and AppData\Local\Microsoft\Application Shortcuts as exclusions. [#394802]
  • During VDA installation or upgrade on Windows 7, you might see a Windows dialog box prompting you to Restart the computer to apply changes. Click Restart Later to continue the upgrade; do not select Restart Now. [#396553]
  • Installing VDAs through Active Directory Group Policy using individual MSIs is not recommended and might fail. Citrix recommends using the startup scripts provided on the product installation media, as described in Install or remove Virtual Delivery Agents using scripts. [#383432, #372136]
  • The optimization phase of the Virtual Delivery Agent (VDA) installation might take a long time to complete. In some tests, it has taken about half an hour and may take longer. These instances occur when installing the VDA on an image running a Windows operating system, if, on the installation wizard Features page, Optimize Performance has been selected. This causes the Microsoft Native Image Generator (Ngen) to run. If this occurs, allow the installation process to finish. Citrix recommends that you run Ngen on your VDA base image prior to provisioning virtual desktops to avoid delays caused when it runs in the background of provisioned virtual desktops. [#381437]
  • During upgrade, if an error message mentioning PICAIsPorticaV2 entry point not found appears during an upgrade, it can be safely ignored. Complete the upgrade process and restart the machine when prompted. [#423947]
  • The VDA for Windows Desktop OS might not install on evaluation versions of Windows 8. The Installation Options screen displays the message "Cannot be installed on this operating system." The issue occurs because the installation program is incorrectly identifying Windows 8 evaluation versions as unsupported operating systems. A hotfix that addresses the issue is available as Knowledge Center article CTX139660. The hotfix lets you patch the installer before running it on Windows evaluation versions.
  • During product installation, machines created by Provisioning Services might fail if .NET Framework 3.5 is not present prior to the installation. To work around this problem, make sure that all NET Framework versions 2.0, 3.0, 3.5, 4.0, 4.5, and 4.5.1 are installed. [#442639, #447851]

Server and Delivery Controller issues

  • XenDesktop 7.6 includes a new version of the volume worker package for CloudPlatform. Citrix highly recommends updating the volume worker template in your deployment with this new version. When updating, please note that in-place upgrades for this package are not supported. Therefore, you must first fully uninstall the previous package or build a new volume worker template from scratch. [493211]

Remote PC Access issues

  • After upgrading from XenDesktop 5.6 FP1, the Remote PC Access Service administrator name may not display correctly. This does not affect operations. [#437948]

  • When an office machine has been instructed to hibernate, a subsequent Remote PC Access session launch may fail. As a workaround for desktop machines that display an error message, try launching the session again. For laptops that display a persistent grey reconnecting screen, restart the PC (remotely from the administrator console using Force Shutdown/Force Restart, or locally with the power button); this can result in data loss. [#441154]

  • When relying on the Wake-up Proxy rather than Intel Active Management Technology (AMT) or Wake on LAN packets, a machine might fail to wake up. This is a Microsoft System Center Configuration Manager issue. [#441412]
  • Starting a VDA from a user device with a smart card reader might fail if the user previously started the VDA from that device and selected Disconnect from the Desktop Viewer. In this case, the user might see the smart card credential screen or the message 'Reading smart card.' As a workaround, choose one of the following:
    • Remove and reinsert the smart card in the reader
    • Click Cancel. Then, in the VDA, press Ctrl+Alt+Del. [#322301]

Studio issues

  • Attempting to launch both StoreFront and Studio causes the Citrix console to exit unexpectedly after XenApp and XenDesktop software is installed on a single Windows 2008 R2 SP1 machine. This occurs when launching both StoreFront and Studio; at the end of the installation, from shortcut menus, or if you open StoreFront in the console first, and then open Studio. To work around this issue, force the Native Image Generator (Ngen) to update the .Net native images. To do this, open a command prompt, and then navigate to c:\windows\\framework64\<v2.0.50727>\. Run ngen update /force. This may take several minutes.
    Note: The framework64 version number may vary slightly, but it should always start with 2.0.
  • Director does not correctly report licensing errors, and Studio is unable to communicate with the license server. This issue may occur if the license server address for a Delivery Site changes while multiple instances of Studio are open and managing the same XenDesktop or XenApp site. To workaround this issue, refresh licensing data in the site by closing all open instances of Studio, reopening a single instance of Studio, and then navigating to the Licensing node. [#492971]
  • When using Machine Creation Services (MCS) to provision machines on VMware vSphere, the combination of CPU sockets and cores on the provisioned machines reflects the combination of CPU sockets and cores on the base image used to create the machine catalogs. During MCS catalog creation, if the number of Virtual CPUs selected is higher than the maximum possible on the host, then provisioned machines are created with the maximum possible sockets and cores for that host, without indication to the user. [#331269]
  • When using System Center Virtual Machine Manager in a pure IPv6 environment, and using Machine Creation Services to create machine catalogs, all VMs have both IPv4 and IPv6, even if the master VM is configured without IPv4 in the TCP/IP stack. This is a third party issue with Microsoft, and there is no workaround. [#371712]
  • When using VMware vSphere in an IPv4 and IPv6 environment with VMware ESX hypervisors configured with VMXNET3network adapters, all VMs have both IPv4 and IPv6, even if the master VM is configured without IPv4 in the TCP/IP stack. This is a third-party issue with VMware, and there is no workaround. [#371712]
  • Long machine catalog names and long storage path names might cause a disk attach error in the VMM job window. Microsoft has identified a maximum limit of 255 characters on the length of the file path for VM resources. This issue has been seen when using local storage on a standalone Hyper-V host, due to the long file path used to store the VMs; however, it is not limited standalone Hyper-V hosts. [#359673]

    As a workaround:

    • Create VMM MCS catalogs with short names, especially when the storage is accessed using a long path.
    • Shorten the path to the storage used to store the VMs.
  • To change a database to one that was previously used, you must use the SDK; it cannot be done from Studio. [#355993]

    To switch to the Configuration Logging database:

    • Set-LogDbConnection -DataStore 'Logging' -DBConnection $null
    • Set-LogDbConnection -DataStore 'Logging' -DBConnection '<new database connection string>'
    To switch to the monitoring secondary database:
    • Set-MonitorDbConnection -DataStore ‘Monitor’ -DBConnection $null
    • Set-MonitorDbConnection -DataStore ‘Monitor’ -DBConnection ‘<new database connection string>'

    For example, the new database connection string could be:

    'Server=dbserver;Initial Catalog = dbname; Integrated Security = True'

  • When you use MCS to provision machines on your hypervisor platform, CPUs are added but no cores. If you change the CPU value during catalog creation, the products licensed on a per CPU basis might need more licenses. For example, your master image has one CPU and four cores and you change the CPU value during catalog creation.

    If, during MCS catalog creation, you select more CPUs than the maximum possible on the host, provisioned machines have the maximum number supported for that host and you are not notified of the difference. For example, a Desktop OS machine can use only two physical CPUs; thus, you will see only two even if more are assigned.

    As a workaround, ensure your master image VM has the same virtual CPU configuration that you want to deploy for the catalog. [#331274]

  • When Lync 2013 client is delivered from a Desktop OS machine or Server OS machine, the video chat feature does not work. See XenDesktop 7.x, XenApp 6.x and Citrix Receiver 4.x Support for Microsoft Lync 2013 VDI Plug-in, ( for information about using Lync 2013. [#371818]
  • When launching a seamless application on a Windows server, the window might not have the Aero theme, even when Enhanced Desktop Experience is enabled.
    • Users launching only seamless applications never get the Aero theme.
    • Users with a mix of seamless applications and desktops get the Aero theme after establishing the first desktop session; then, seamless applications have the Aero theme.

    As a workaround, set the Citrix Enhanced Desktop theme in the default user profile; all users on that VDA get the Enhanced Desktop Experience for their seamless applications. The theme is part of the VDA install and must be set for all VDAs. [#348812]

  • Studio messages sent to a Windows 8 machine will display on the Windows 8 Desktop, and not the Windows default (formerly called Metro) display mode. The user must switch to Desktop mode to see the message. This is a third party issue and there is no workaround. [#387356]
  • If a Site contains more than one hosting infrastructure object with the same name, the Studio display might not be correct. When you create hosting infrastructure objects (for example, networks and storage), it is best practice to specify a unique name for each. [#384959]
  • After using Delegated Administration to create an administrator with a new scope, refresh the Studio display. Otherwise, you might receive a permissions error when you log on as the new administrator and attempt to create a new connection or resource. [#386634]
  • Applications hosted on Desktop OS machines with random assignments might fail to open after the loading dialog box disappears. This issue occurs when the time the application takes to start exceeds the default one-minute time-out and the session exits automatically. [#389025]

    As Administrator, change the base image and re-provision with a changed timeout value as follows:

    Locate the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI (Create the key if it is not available.)

    Name: ApplicationLaunchWaitTimeoutMS

    Type: REG_DWORD

    Data: Required additional time-out, in milliseconds

    Note: Specifying a value of less than 10000 reverts to 10000 because 10 seconds is the minimum override.

  • To discover and set up applications in Delivery Groups, make sure that there are some machines that are registered and can be powered on. For an App-V application to be discovered, you need to configure App-V Publishing in Studio. [#393676]
  • After a user launches the first App-V application, launching a second App-V application too quickly might fail. If this occurs, the user should wait a few minutes so that the initial synchronization can complete, and then launch the second application again. For details about this issue, see CTX138056. [#397521]
  • If the antivirus program BitDefender is installed on a VDA, you might not be able to create machine catalogs. There is no workaround for this issue. [#392705]
  • After upgrading to XenDesktop 7.5, you cannot create a connection to CloudPlatform or Amazon Web Services (AWS) if the site is configured with a connection to an on-premise hypervisor. You must create a new 7.5 Site. For a hybrid deployment (which includes cloud and non-cloud Sites), you must create separate Sites that share the same StoreFront site.[#454114]
  • Creating a machine catalog fails in an environment running VMM 2012 SP1 and Hyper-V 2012 when using a ODX-enabled Storage Area Network. Follow the instructions in to resolve this issue. [#424040]
  • The Citrix policy setting ICA listener connection timeout applies only to Virtual Delivery Agent 5.0, 5.5, and 5.6 Feature Pack 1, even though the Studio policy editing window says this setting also applies to 7.0 Desktop OS, 7.1 Desktop OS, 7.5 Desktop OS, and 7.6 Desktop OS.
  • In Studio, the description of the Citrix policy setting Launching of non-published programs during client connection incorrectly states that this setting specified whether to launch initial applications or published applications through ICA or RDP on the server. This setting specifies only whether to launch initial applications or published applications through RDP on the server.
  • Citrix policies might not be applied correctly when filtered by tags. To prevent this, apply the hotfix at CTX142439. [#529165]

Director issues

  • The User-based application usage data in the Hosted Application Usage reports, is not accurate for time ranges that exceed the last seven days. This occurs because application data beyond the last seven days is deleted. To avoid using incorrect User-based application usage data, only use data reported within the last seven days. [504642]
  • Director displays the Unexpected error. Check your network connection or view server event log for further information popup error on the Trends and Filters page because the XenDesktop database name includes spaces. The API calls used by Director do not support connecting to a database that has a name containing spaces. Follow database naming requirements when renaming a database. [494339]
  • After upgrading, Director does not persist an administrator's UI.GlobalSearchResults settings. To work around this issue, manually edit the UI.GlobalSearchResults setting in the web.config file after upgrading. [484066]
  • Hotfix inventory may take several hours to update when large numbers of hotfixes are applied at the same time to environments with more than 20,000 desktops. [#489604]
  • Historical information is preserved after you have deleted and then re-created a Delivery Group from the same Session Machine Catalog. The data then incorrectly displays that historical information on the Trends graph and table. To create Delivery Groups without preserving historical trend data, do not re-create the Delivery Group until after you have deleted the machine catalog and created the new catalog. [#480010]
  • When navigating from the Filters page to the User Device page, user names may not display. If Delivery Controllers cannot access a domain containing user accounts because of Active Directory restrictions, those full user names may not appear on the User Device page. To work around this issue, ensure that the domain where XenDesktop is installed is trusted by the domain to which the end user belongs. [#479517]
  • If all Sites within an existing Site Group do not have assigned delegated administrators, the search for machines and end-point devices within the Site Group fails. To allow an administrator to search across all Sites within a Site Group, add the administrator to the Delegated Administrator group that has permissions to the Sites. [#491740]
  • When monitoring Windows XP virtual desktops running WinRM 2.0 for users with VDAs earlier than 7, you must change the WinRM port listening order. For details about how to change the setting to 5985,80, see Advanced configuration. [#273609]
  • You cannot edit an existing Site Group using the Director Configuration Tool. To work around this issue, open the .xml configuration file from within the Director Configuration folder, and then modify the Site Group setting. [#491681]
  • Using Active Directory Users and Computers to configure users with logon scripts fails and data does not appear in the Logon Duration panel. Instead, to configure users with logon scripts, you must use a Group Policy. [#393259]
  • The logon duration data from a first-time logon to a Personal vDisk VDA might not be collected or displayed in Director. For subsequent logons, data appears normally. [#383941]
  • When you run a console session from a Windows Server 2012 desktop, navigating to the user details page in Director might result in an error and no data will be displayed.

    As a workaround, register the VDA, log off the current session, and log in to the VDA again. [#388513]

  • In the Infrastructure panel of the Dashboard page, Director displays “Not Available” for Citrix CloudPlatform-based host connections, Amazon Web Services, Hyper-V, and Microsoft System Center Configuration Manager and does not provide status information. [#449806, #446397]
  • Logon duration does not update in Director's Dashboard view if users launch a hosted application. [#386860]

HDX issues

Note: For the latest updates to HDX Flash compatibility, refer to CTX136588.

  • Configuring HDX MediaStream redirection on a new machine fails. To work around this issue, reboot the end-point machine after installing Receiver. [#494741]
  • Sessions fail if using a certificate with the SHA512 algorithm for an SSL/TLS connection. This occurs when using Receiver for HTML5 to launch sessions with Server OS machines running Windows Server 2012 R2. To avoid this issue, do not use the SHA512 algorithm for an SSL/TLS certificate in this type of configuration. [#487284]
  • With GPU pass-through and NVIDIA Kepler cards, the first connection attempt may fail for a HDX 3D Pro user device with three or four monitors. If this happens, attempt to connect again. [#422049]
  • When a user attempts to connect, change the screen resolution, or change the size of the session screen, the screen may flicker or display as black. This may occur if larger resolutions are selected and the video driver cannot allocate enough memory at boot time to support the resolution. You can view the current resolution setting in the session window by selecting Advanced Settings from the Screen Resolution dialog. To allow the driver to allocate enough memory to support higher resolutions, increase the amount of memory for the VDA. Use the following as guidelines: Windows 7: Sum-of-all-monitors (width x height x 4 BytesPerPixel x 2 BackBuffers) Win8: Sum-of-all-monitors (width x height x 4 BytesPerPixel x 3 BackBuffers). [#494671]
  • If the USB Redirection policy is enabled, USB storage and audio devices do not work when the user chooses to redirect their devices. This only occurs on Server OS machines running Windows 2012 and later. To exclude audio and storage devices from the list of devices, use the Client USB Device Redirection Rule policy. For additional information on USB redirection rules and configurations, see [#479578]
  • When the user attempts to launch a session from a Server OS machine, Receiver displays the "The connection to <app name/desktop name> failed with status (1030)" error message on the user's device after the Session Reliability Connections policy is changed from disabled to enabled by the administrator. To work around this issue, the administrator must restart the VDA for the policy to take effect. [#486073]
  • When using Remote PC to run a Lync 2013 session remotely, attached web cameras on client devices are not listed in Lync 2013 in the user's session. To work around this issue, the user can use Device Manager to disable the web cameras on their remote machines. [#482807]
  • Even though webcams might support H.264 compression, this release does not support hardware compression, so you must use software compression for those webcams. To do this, add a registry entry on user devices at HKEY_CURRENT_USER\Software\Citrix\HdxRealTime; add a DWORD registry name DeepCompress_ForceSWEncode. When set to 1, software compression is used. By default, this setting is off and hardware compression is used . [#357356]
  • HDX RealTime Webcam video lags if the video resolution is higher than 720p (1280x720). [#350187]
  • When using HDX Flash Redirection continuously, the session might become unresponsive. [#350085, 361926]
  • HDX RealTime Webcam supports most raw formats supported by a webcam, but in rare cases, if the webcam has an unsupported format, that webcam might not work as the Citrix HDX Webcam. [#338318]
  • Multiple duplicate images might be seen intermittently when using Citrix HDX Webcam with some models of webcams. [#367322]
  • HDX RealTime Webcams are not supported for these applications:
    • Citrix GoToMeeting when hosted on Server OS Machines with Windows 2012 operating systems. [#346430]
    • GoToMeeting (on any platform) if the webcam is attached after a meeting has started. [#346140]
    • Microsoft Lync 2013 and Adobe Connect with VDAs on Windows 8, Windows 8.1, and Windows 2012 operating systems. [#340784, 348506, 459732]
    • Microsoft Office Communications Server (OCS) video calls if the Webcam is attached after the call is in progress. [#370236]
    • Microsoft Silverlight. This is an intermittent issue. As a workaround, on the user device, enable the legacy codec by adding a DWORD registry key value name EnableDeepcompress_Client at HKEY_CURRENT_USER\Software\Citrix\HdxRealTime and setting it to 0. [#379779]
    • 64-bit video conferencing applications. Video compression for 64-bit applications is not supported. [#366515]
  • When using HDX 3D Pro with the XenDesktop 5.6 Feature Pack 1 Virtual Desktop Agent on Windows XP virtual desktops, during the first connection, the Fine Drawing (2D) check box is selected and sometimes greyed out. This is due to delayed registry updates, which cause the Config tool UI to pick up incorrect default values during initialization. [#353031]

    As a workaround, disconnect and reconnect the session.

    If the problem persists, clear previous session information by deleting settings under the following registry entry:


  • On Windows XP, Citrix HDX webcam might not be detected. As a workaround, install Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package from website and try again. [#382733]
  • When viewing the Display Adapters node from the Device Manager console applet, the Standard VGA Graphics Adapter appears in the list with a yellow exclamation point (yellow bang). You can ignore this warning because it does not affect functionality. This warning occurs because a legacy model XPDM display driver (Standard VGA Graphics Adapter) is not allowed to load when a new model WDDM display driver (Citrix Display Driver) is installed. [#339390]
  • Users might experience issues when attempting to play media files on Windows 8 user devices. This is because this product fails to register the correct default program for client-side content fetching protocols used to stream media files to user devices. As a workaround for Microsoft Media Streaming (MMS) and Real Time Streaming (RTS) protocols, change the default program used for playing media files from Windows Media Player to Citrix CSF Handler. There is no workaround for the Hypertext Transfer Protocol (HTTP). [#328805]
  • TWAIN redirection fails on hosted shared desktops and applications. This is a third party issue related to TWAIN applications that require TWAIN binaries to be located in certain paths. [#300854, 340999]

    As a workaround, on your Windows Server 2012 machine running the VDA, copy these files to the following locations:

    • Copy "twain_32.dll" to the "\WINDOWS" directory of the User profile (for example, copy twain_32.dll into the folder: "%USERPROFILE%\Windows\").
    • Copy "twain_32.dll.mui" into the "\WINDOWS\en-US\" directory of the User profile (for example, copy twain_32.dll.mui into the folder: "%USERPROFILE%\Windows\en-US\").
  • The 64-bit Windows Media Player or QuickTime player cannot play some video files using server-side rendering when HDX MediaStream Windows Media Redirection is disabled. As a workaround, use the 32-bit version of Windows Media Player. [#384759]

  • Universal Print Server printers selected in 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 Windows Server 2012, Windows 10 and Windows 8 platforms. [#335153]
  • With GPU pass-through and NVIDIA Kepler cards, the first connection attempt may fail for a HDX 3D Pro user device with three or four monitors. The second connection should be successful. [#422049]
  • The user’s Windows computer stops responding when a GoToMeeting session using a webcam configured for USB redirection is started in a Remote PC Access session with an Intel Core i7 processor-based computer. If this occurs, restart the user’s computer and restart the Remote PC Access session. The session resumes where the disconnection occurred. To avoid this occurrence, use HDX webcam video compression instead of USB redirection. For details, see [#423284]
  • User devices running Receiver for HTML5 might be unable to connect to a Server OS machine running Windows Server 2012 R2. To avoid this issue:
    • Use an existing machine, rather than a machine created with Machine Creation Services (MCS) or Provisioning Services, as the Windows Server OS machine.
    • If you plan to use machines created with MCS, on the master image for the catalog, edit registry and create the following DWORD value:
      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.
      HKEY_LOCAL_MACHINE\Software\Citrix\GroupPolicy\Defaults\IcaPolicies\AcceptWebSocketsConnections = 1 
      HKEY_LOCAL_MACHINE\Software\Citrix\GroupPolicy\Defaults\IcaPolicies\AllowDesktopLaunchForNonAdmins = 1 
      HKEY_LOCAL_MACHINE\Software\Citrix\GroupPolicy\Defaults\IcaPolicies\WebSocketsPort = 8008

      Because the WebSockets port number is set by editing the registry, it is not necessary to enable the Websockets connections Citrix policy for the catalog.

    • If you are using a machine created with Provisioning Services, follow the recommendations in CTX139265. [#424064]
  • When HDX Flash Redirection is used with a dual-monitor setup and the Flash content window in full-screen on one monitor, clicking anywhere else on the screen might cause the Flash content window to lose focus and be hidden behind the session window. This is behavior is as designed for HDX Flash Redirection. If this happens, users can make the Flash content window visible again by changing the session window from full-screen mode to window mode using the Citrix Desktop Viewer toolbar. [#567132]

Licensing issues

  • Errors may occur when installing the Delivery Controller if the most recent version of the license server is not installed. When upgrading to version 7.6, install the latest version of the License Server before installing any other core components. [#510425]
  • When licensing is uninstalled and then reinstalled and a read-only product administrator attempts to view Licensing information in Studio, Studio displays the error "You do not have permissions to perform this operation." A read-only administrator does not have the permission to trust a new License Server. As a workaround, a full license administrator must go to the Licensing node and authenticate the License Server. [#380982]
  • If you installed the License Server without successfully configuring it (with the post installation License Server Configuration tool), any subsequent License Server upgrade fails. As a workaround, ensure that every License Server installation is configured with the post-installation License Server Configuration tool. [#377079]
  • When you try to start the License Administration Console or the Simple License Service, a blank page might display if the Internet Explorer Enhanced Security Configuration is enabled and the License Administration Console or the Simple License Service is not in the Trusted Sites zone. Workaround: Disable Internet Explorer Enhanced Security Configuration. [#382429]
  • If port 8083 is in use when you install or upgrade the product, the License Server configuration and installation fail with a License Server Configuration Failed error. As a workaround, check the event log to ensure the error is actually "Port in use." If it is:
    1. Uninstall the License Server by double-clicking on the CTX_Licensing.msi in the x64\Licensing folder on the product installation media.
    2. Run the installer again. It displays some components as Partially installed. Click Install and the installer completes the installation and configures any necessary product components.
    3. Manually install the License Server and specify port numbers that do not conflict with other applications on the machine. [#390815]
  • The user list for the License Administration Console and the Citrix Simple License Service Web page does not support non-ASCII characters in user/group names. Due to this limitation, on a Russian operating system, the BUILTIN Administrators group is not added to the user list because it is created with non-ASCII characters. This issue applies to both fresh installs and upgrades. Any users belonging to the BUILTIN Administrators group in an earlier release of XenDesktop and the Simple License Service will not have access to the License Administration Console or the Simple License Service after an upgrade.

    As a workaround, add ASCII-character versions of Russian users/groups names post-installation using the License Administration Console interface. Alternatively, install the license server on one of the other supported operating systems. [#395305]

  • When you install or upgrade the product and have Perpetual (permanent) licenses, Studio might display your licenses with an expiration date of 01/01/2000. You can ignore this expiration date and launch your desktops and applications. [#402975]

Local App Access issues

  • In a Windows 8 or Windows Server 2012 hosting environment, if Local App Access is enabled and the extension for a client hosted app does not have a File Type Association (FTA), FTA redirection fails. The user is prompted to select "Look for an app in the Store" or "More options." [#372834]

    As a workaround, use one of these methods on the VDA master image:

    • Rename the DelegateExecute registry value for HKEY_CLASSES_ROOT\Unknown\shell\openas\command\DelegateExecute.
    • Use Notepad to open a file with the extension. FTA redirection will work for subsequent attempts.
  • URL redirection is disabled, by default, by Microsoft on Windows Server 2012. To enable it, disable Internet Explorer enhanced configuration mode. [#356260]
  • Changes to Local App Access properties during a session do not take effect automatically. As a workaround, log off and log back on. [#357488 ]
  • If Local App Access applications are launched on Windows 8 or Windows 2012 platforms, those VDAs cannot be launched from the Modern shell. As a workaround, close the local application and then launch the VDA application. [#359670]
  • Shellhook.dll is not loaded with Receiver for Windows 3.4 and earlier when local applications are launched. As a workaround, change the value of the registry key LocalAppInit_DLLs to 1 under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows. If the workaround is not used, client to server FTA redirection does not work correctly. [#356130]
  • URL redirection might fail for Internet sites that have a pop-up blocker enabled. As a workaround, disable the pop-up blocker. However, for security reasons, disabling pop-up blocker is not recommended. [#371220]
  • When Aero mode is enabled for a VDA session, there are inconsistencies between the VDA local applications and the client-hosted applications (for example, ALT+Tab; flashing taskbar entries, jump list, live preview). For compatibility, disable the Aero mode. [#361043]
  • Flash Redirection has compatibility issues such as a WMP black screen and flash pseudo-container window out of bounds. As a workaround, disable Flash redirection. [#360182]
  • The Desktop Composition Redirection graphics feature is disabled when Local App Access is enabled. To use that feature, disable Local App Access. [#377386]
  • With Session Reliability and Local App Access enabled, if network connectivity is disrupted after you click Home in the product toolbar and display the client's desktop, the VDA session might not display the last screen shown before the network disruption. Instead, only the product toolbar and the client's desktop appear. On the toolbar, only the Disconnect option works. [#357769]
  • When Local App Access is enabled and a user changes the product session to full screen before or while playing a media file, some or all of the image does not appear. To work around this issue, relaunch the session. [#402702]

Desktop Lock issues

  • After installing Citrix Desktop Lock on a domain-joined Windows 8 machine and restarting it, the desktop background may become black and a My Computer window may be displayed instead of the usual Start screen. To log off the machine, type logoff in the address bar of the window, and press Enter. For more information about configuring Windows 8 machines with Desktop Lock, see Desktop Lock. [#329075]
  • If a Windows 8 or Windows 7 machine fails and the user attempts to restart it by pressing Ctrl+Alt+Del, the Windows Security dialog on the local desktop opens. This issue occurs even when the Citrix Desktop Lock software is installed and configured. To resolve this issue, select Start Task Manager to display the Restart dialog. [#337507]
  • The Citrix Desktop Lock does not redirect Adobe Flash content to domain-joined user devices. The content can be viewed but is rendered on the server, not locally. As a workaround, configure Adobe Flash redirection for server-side content fetching to pass the content from the server to the user device. This issue does not occur on non-domain-joined devices or when the content is viewed with the Desktop Viewer. [#263092]
  • Failure to start the virtual desktop agent (VDA) on the user device may occur if the device is running Windows 7 with Desktop Lock and Receiver for Windows Enterprise 3.4. This may occur if the user is or is not connected to the Internet. The error message, “No Internet Connectivity,” may appear when this occurs. This is a third party issue with Microsoft. For a potential resolution, see [#408642]

End-user and VDA issues

  • Handle leaks by wfica32.exe can occur on the user device when playing Windows Media Player files continuously in a Windows 32-bit XP client session. [#378146]
  • Disconnect button is not available to users. As a workaround, provide a shortcut to the TSDiscon.exe utility, which is included with the operating system; this will allow them to disconnect from sessions. [#362937]
  • The user may continue to have access to the remote PC after attempting to disconnect. This occurs when the user selects the Disconnect command from the Start menu. There is a delay after Disconnect is selected. If the user presses Ctrl+Alt+Del during this delay, the VDA on the remote PC remains available for several minutes before disconnecting. During that time, the VDA on the user device freezes until the remote VDA disconnects. [#322301]
  • For VDAs installed on Windows 7 and Windows 8 platforms, two mouse pointers might be visible: one movable and one locked to the UI. This is a third party issue with the NVidia driver. As a workaround, you can disable NVidia GRID technology (formerly known as VGX) by running MontereyEnable.exe -disable -reset, and then restarting the machine. [#307921]
  • The Microsoft Desktop Composition feature has a scalability cost for VDAs. For users requiring maximum scalability, Desktop Composition should be disabled by Microsoft policy for any user not using Desktop Composition Redirection. [#386602]
  • In certain scenarios, when users attempt to unlock a locked session locally, the session relocks itself repeatedly. This issue might occur if the user unplugs or powers off a keyboard locally connected to a Remote PC Access machine during a remote ICA session. As a workaround, users should relaunch the session remotely, disconnect the session, and then log on again from the console. [#382554]
  • For VDAs earlier than 7, users' data might not appear in Director even after you correctly configure Windows Remote Management (WinRM) for these VDAs. If this issue occurs, restart the WinRM service and the data should display in Director as expected. [#392047]
  • In secure environments, a new VDA might fail to register with a Controller. Specifically, when installing a VDA containing a local security policy setting that allows only administrators to access a computer from the network, the VDA installs but cannot register with a Controller. Instead, a warning is issued that user access rights are not properly configured. For more information, see CTX117248. [#336203]
  • Receiver for Windows users cannot log on to stores using pass-through authentication, even though the domain pass-through authentication method is enabled in the StoreFront authentication service. To resolve this issue, run the command Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True from a Windows PowerShell command prompt on the Controller. [#330775]
  • ICA Roundtrip checks are not supported when legacy graphics mode has been specified using a policy for Windows Server 2012 VDAs. There is no workaround for this issue. Note that Windows 8 VDAs do not support legacy mode, so they are not affected by this issue. [#394824]
  • With Windows Server 2012 R2 and older Domain Controllers, if you require users to change their password on next login, an error occurs. To work around this problem, remove the Microsoft update KB2883201. [#438725]
  • When users connect directly to VDAs using RDP, the Controller sometimes mistakenly reports additional sessions that do not exist, and these non-existent sessions remain in a Connected state in Studio until the VDA is restarted. [#385823] 
  • When Passthrough Authentication is implemented for Citrix Storefront on FireFox and Chrome browsers, users are prompted for credentials when launching applications. [#441487]

  • For Citrix Receiver for Web with a domain pass-through configuration, when a user logs on to a device using Smartcard and then launches a published desktop, the connection may fail. To work around this issue, edit the default ICA file in the store (for example, in C:\inetpub\wwwroot\Citrix\Store\App_Data\default.ica), and add the following line to the [Application] section:



Personal vDisk issues

To view personal vDisk related known issues, see Personal vDisks.

Provisioning Services issues

To view Provisioning Services issues, see About Provisioning Services 7.0, 7.1, and 7.6