Product Documentation

Known issues

Dec 11, 2014

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.
  • To configure a non-standard 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 topic. 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 un-paused, 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]
  • When deploying virtual desktop VMs using Provisioning Services, the setup wizard in this product does not use more than one storage resource in the Hosting Infrastructure record, even when more storage resources are available. As a workaround, when using Provisioning Services for deployment, create Hosting Infrastructure records with only one storage record. [#400212]
  • 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 pane 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]
  • When joining or removing a Controller from a Site, all StoreFront servers in the cluster must be powered on. Otherwise, the operation fails for the StoreFront part, and Studio throws an exception that mistakenly suggests operation failure. In such cases, restarting Studio corrects the Site display. If a StoreFront server cannot be brought back online, use the StoreFront console from another machine in the cluster to remove StoreFront from the failed server. To rejoin the failed server to the cluster, either reinstall StoreFront or successfully run the following commands in sequence: C:\Program Files\Citrix\ReceiverStoreFront\Scripts\ImportModules.ps1 and Clear-DSXdConfiguration. [#396193]
  • In product deployments where a SQL Server 2012 database is configured for high-availability using AlwaysOn, there may be an interval (while a database failover is in progress) when Site operations may fail; for example, VDA power management or session launches. If this occurs, retry the impacted operation after the failover is complete. [#394787]
  • Applications might fail to launch on user devices if you enable the profile streaming policy without setting antivirus exclusions for Microsoft Group Policy files, such as NTUser.pol. As a workaround, disable profile streaming or set antivirus exclusion policies for those users. For information, see In particular, read the section "Turn off scanning of Group Policy related files" for details about excluding the NTUser.pol and Registry.pol files. [#399152]
  • 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]
  • Windows Store Apps installed to the virtual desktop from the store will not launch after the virtual desktop restarts through a Restart or Shutdown-Start command. Any apps installed after the virtual desktop restarts also fail to launch. [#413003]
  • Start menu tiles might not appear when you log in to a Windows 8 machine if you have previously logged in and logged out of a Windows 8.1 machine of the same bitness. To prevent this issue, avoid using Windows 8.1 profiles on Windows 8 machines. [#422043]
  • 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]
  • After upgrading from XenDesktop 7.0 to a later version, when you select Test Site from the Studio Common Tasks pane errors relating to the Monitor Service database schema appear. You can safely ignore these errors, as the Site is not affected. Do not restore your database from the most recent backup if the following errors are the only errors you see in the report.

    StoredProcedure MonitorData.DeleteMachinesByCatalogId object definition does not match the expected reference schema.

    Restore the database <name of SQL instance>\<Monitor database name> to the most recent backup.

    StoredProcedure MonitorData.DeregisterMachinesByCatalogId object definition does not match the expected reference schema.

    Restore the database <name of SQL instance>\<Monitor database name> to the most recent backup.

    StoredProcedure MonitorData.RemoveMachinesByDesktopGroupId object definition does not match the expected reference schema.

    Restore the database <name of SQL instance>\<Monitor database name> to the most recent backup.

    StoredProcedure MonitorData.TerminateSessionsBySid object definition does not match the expected reference schema.

    Restore the database <name of SQL instance>\<Monitor database name> to the most recent backup. [#429471]

  • The default Virtual Private Cloud (VPC) must be present for Machine Creation Services (MCS) to provision machines. If you delete the Default VPC from AWS, then MCS will not work, and AWS support must be contacted to restore the default VPC. [#437085]
  • When selecting a custom date range for a Configuration Logging report, the calendar displays might be incorrect. [#452399]
  • When deploying StoreFront, do not use Unicode characters in any server names. [#452972]
  • 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]
  • When you upgrade version 7 or 7.1 VDAs that are installed on physical machines (including machines used for Remote PC Access), to version 7.5 VDAs, the Machine Identity Agent and Personal vDisk drivers might be installed, which can cause them to fail a security audit. To prevent this, upgrade the VDAs using the command-line interface and include the option /EXCLUDE "Personal vDisk", "Machine Identity Service," see Manual upgrade for VDAs on physical machines. [#455472, #455553]
  • 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]
  • 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

  • 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 installing VDA version 5.6 on a 64-bit Windows Vista or Windows XP system, do not include the Citrix Receiver in that installation; otherwise, the installation might not complete. Follow this procedure:
    1. Install the VDA, but clear the Citrix Receiver checkbox in the installation wizard.
    2. Install Receiver (CitrixReceiverEnterprise.exe) from the Citrix Receiver and Plug-ins > Windows > Receiver folder on the product installation media.
    3. If you need the offline plug-in, install CitrixOfflinePlugin.exe from the Citrix Receiver and Plug-ins > Windows > Offline Plug-in folder on the product installation media. If you specify an installation location other than the default (C:\Program Files (x86)\Citrix), be sure the destination directory exists before starting the installation.

    If you mistakenly start a VDA installation with the Citrix Receiver checkbox enabled, use Windows Task Manager to end the running application. [#381625]

  • 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]
  • After performing an upgrade on a Controller, close Studio and then restart it so that the system recognizes that the Controller has been upgraded. Register the upgraded Controllers by selecting the controller, and then clicking Register Controller. [#382898]
  • 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 in Active Directory. [#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]
  • 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]
  • 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]

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]
  • When power management is enabled for Remote PC catalogs, subnet-directed broadcasts might fail to start machines that are located on a different subnet from the Controller. If you need power management across subnets using subnet-directed broadcasts, and AMT support is not available, try the Wake-up proxy or Unicast method. [#453820]

Studio issues

  • Studio startup is delayed if the machine where it is installed does not have an Internet connection. (For security, Citrix signs .NET-based components with an Authenticode signature; Studio startup is delayed if Windows cannot verify the signature.) As a workaround, disable the Authenticode signature checking feature as described in [#337698]
  • 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]
  • When you use the PowerShell SDK to change a Site name (set-configsite -sitename "change name"), you will receive an error if you attempt to join another Controller to the Site. As a workaround, rename the Site to its original name (to match the ServiceGroupName on the output of Get-ConfigRegisteredServiceInstance) before joining the new Controller to the Site. After joining the Site, you can rename the Site again. [#386919]
  • 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.

  • When XenServer hosts are in a pool and a secure connection from this product to the pool is made, you may receive the following error message: Invalid Connection Address. Check that the address is valid and that it references a host in the XenServer pool.

    To avoid this scenario, install certificates issued by a trusted root certificate authority on all the XenServer hosts in the pool. [#392279]

  • When creating a machine catalog through MCS, a Database failover might occur when copying the master image or when adding a machine. The following message appears: Collection was modified; enumeration operation may not execute. Make sure that the database is in a healthy state before performing the following actions. If the failover occurs:

    During the master image copy, delete the machine catalog and create it again. When adding machines, select the MCS machine catalog and click Add Machines. If an error persists, delete the machine catalog and create it again. [#393889]

  • To edit Host connections in Studio, you must use the Full Administrator role or the Machine Catalog Administrator role and the All scope. Without the All scope you may experience an unexpected error. [#392799]
  • When updating a machine catalog, although the update is successful, notification messages may fail to appear on sessions running on machines in this catalog. As a workaround, the administrator can attempt to send the message again through the Search node in Studio. [#390726]
  • 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 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]
  • When a physical machine is newly configured for use with Remote PC Access, the first attempt to register with a XenDesktop Site might fail. After about five minutes, the machine successfully re-registers. Prior to this successful re-registration you cannot connect to the machine using StoreFront. [#394791]
  • If you attempt to create a connection in Studio to a Micosoft System Center Virtual Machine Manager (VMM) on a Delivery Controller where the VMM Console is installed, Studio fails to warn that the connection will not function correctly unless VMM Console is installed on all Controllers in the site. To prevent this issue, install VMM Console on all Controllers and restart the Controllers. [#348614]
  • If the antivirus program BitDefender is installed on a VDA, you might not be able to create machine catalogs. There is no work-around for this issue. [#392705]
  • When XenServer 6.2 or 6.1 is configured with an open vSwitch controller, MCS will fail to create machines unless the option The Master Image is built using Windows XP or Windows Vista is checked. Selecting this option means that some features in this product are unavailable for this catalog. [#394771]
  • If a Citrix CloudPlatform administrator attempts to create a machine catalog on a system where one or more user accounts are also using XenDesktop, the creation may fail. To work around this issue, the administrator should create a user account and use that account to create machines. [#452528]
  • When you create Machine Creation Services (MCS) provisioned machine catalogs with a large number of machines, deleting machines or performing power actions may cause Studio to use up available memory and fail on Delivery Controllers with 8GB RAM or less. Go to the Actions tab and clear the background actions before closing and restarting Studio after performing tasks involving large numbers of machines. For information about a fix released for this issue, see CTX140706. [#455848]
  • 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]

Director issues

  • 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]
  • 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.
  • 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]
  • 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 of 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 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

  • 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 the 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]
  • Launching client-hosted shortcuts in the Local Programs folder in a session connected from Japanese or Chinese clients might result in an application error. To resolve this issue, log off from the session then launch the session again. If the problem persists, create a client-hosted application as described in Provide access to local applications to publish specific local applications in place of client-hosted shortcuts [#399100]

Personal vDisk issues

  • The presence of antivirus products can affect how long it takes to run the inventory or perform an update. Performance can improve if you add CtxPvD.exe and CtxPvDSvc.exe to the PROCESS exclusion list of your antivirus product. These files are located in C:\Program Files\Citrix\personal vDisk\bin. [#326735]
  • If copy-on-write is enabled and alternate data streams are used, changes made to the contents of the alternate data streams are not saved. Copy-on-write does not support alternate data streams. To avoid this conflict, relocate the files containing alternate data streams to the guest volume. For details, see the documentation in the custom rule files in %ProgramData%\Citrix\personal vDisk\Config with custom_* names. [#369193]
  • Hard links between files inherited from the master image are not preserved in personal vDisk catalogs. [#0368678]
  • After upgrading from Office 2010 to 2013 on the Personal vDisk master image, Office might fail to launch on virtual machines because the Office KMS licensing product key was removed during the upgrade. As a workaround, uninstall Office 2010 and reinstall Office 2013 on the master image. [#391225]
  • Personal vDisk catalogs do not support VMware Paravirtual SCSI (PVSCSI) controllers. To prevent this issue, use the default controller. [#394039]
  • For virtual desktops that were created with Personal vDisk version 5.6.0 and are upgraded to 7, users who logged on to the master virtual machine (VM) previously might not find all their files in their pooled VM. This issue occurs because a new user profile is created when they log on to their pooled VM. There is no workaround for this issue. [#392459]
  • Personal vDisks running Windows 7 cannot use the Backup and Restore feature when the Windows system protection feature is enabled. If system protection is disabled, the user profile is backed up, but the userdata.v2.vhd file is not. Citrix recommends disabling system protection and using Backup and Restore to back up the user profile. [#360582]
  • When you create a VHD file on the base VM using the Disk Management tool, you might be unable to mount the VHD. As a workaround, copy the VHD to the PvD volume. [#355576]
  • Sometimes, after performing an image update on a virtual desktop, the personal vDisk associated with the desktop does not start and an error (error code 0x10) is displayed. There is no workaround for this issue. [#416128]
  • Office 2010 shortcuts remain on virtual desktops after this software is removed. To work around this issue, delete the shortcuts. [#402889]
  • When using Microsoft Hyper-V, you cannot create a catalog of machines with personal vDisks when the machines are stored locally and the vDisks are stored on Cluster Shared Volumes (CSVs); catalog creation fails with an error. To work around this issue, use an alternative storage setup for the vDisks. [#423969]
  • When you log on for the first time to a virtual desktop that is created from a Provisioning Services catalog, the desktop prompts for a restart if the personal vDisk has been reset (using the command ctxpvd.exe -s reset). To work around this issue, restart the desktop as prompted. This is a once-only reset that is not required when you log on again. [#340186]
  • If you install .NET 4.5 on a personal vDisk and a later image update installs or modifies .NET 4.0, applications that are dependent on .NET 4.5 fail. To work around this issue, distribute .NET 4.5 from the base image as an image update.”

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 Configure the 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]
  • 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]
  • 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]
  • When installation of a VDA for Windows Server OS from the graphical interface appears to hang, check for an error message ("Printers - The arguments are invalid") which might appear behind the main installation window. This message appears if the Print Spooler Service has not yet started. Either wait for the Print Spooler Service to start, or start the service manually. After clicking OK in the message box, installation continues. [#385526]
  • 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]
  • When using Machine Creation Services (MCS) to provision machines, only use ASCII characters for machine names.

    Using non-ASCII characters results in other unrelated characters for host names in provisioned machines. [#415134]

  • When creating a Machine Creation Services (MCS) machine catalog, a name containing the back tick character (`) results in an error. Refrain from using this character in machine catalog names [#414419].
  • Users may encounter blank or black screens when logging in to Windows Server 2012 R2 machines, and be unable to connect to the server through RDP connection. In addition, on the server console some system processes such as task manager may also be unable to run, requiring a system cold boot.

    To alleviate this problem, change the Enhanced Desktop Experience policy to Prohibited for Server 2012 R2 Delivery Groups. [#425255]

  • 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: