Product Documentation

System requirements and compatibility

Oct 19, 2016


Operating system

  • Windows 10
Note: Receiver for Windows 4.3 has been tested on Windows 10 (build 10108).
  • Windows 8.1, 32-bit and 64-bit editions (including Embedded Edition)
  • Windows 8, 32-bit and 64-bit editions (including Embedded Edition)
  • Windows 7, 32-bit and 64-bit editions (including Embedded Edition)
  • Windows Vista, 32-bit and 64-bit editions
  • Windows Thin PC
  • Windows Server 2012 R2, Standard and Datacenter Editions
  • Windows Server 2012, Standard and Datacenter Editions
  • Windows Server 2008 R2, 64-bit edition
  • Windows Server 2008, 32-bit and 64-bit editions
  • Windows Server 2003, 32-bit and 64-bit editions
  • Windows XP (Embedded Edition)
Note: Support for Windows XP ended April 8, 2014 when Microsoft ended extended support for Windows XP.


  • VGA or SVGA video adapter with color monitor
  • Windows-compatible sound card for sound support (optional)
  • For network connections to the server farm, a network interface card (NIC) and the appropriate network transport software

Touch-enabled devices

Receiver for Windows 4.3 can be used on Windows 7 and 8.1 touch-enabled laptops, tablets, and monitors with XenApp and XenDesktop 7 or later, and with Windows 7, 8 and 2012 Virtual Desktop Agents.

Citrix Servers

  • XenApp (any of the following products):
    • Citrix XenApp 7.6
    • Citrix XenApp 7.5
    • Citrix XenApp 6.5, Feature Pack 2, for Windows Server 2008 R2
    • Citrix XenApp 6.5, Feature Pack 1, for Windows Server 2008 R2
    • Citrix XenApp 6.5 for Windows Server 2008 R2
    • Citrix XenApp 4, feature pack 2, for Unix operating systems
  • XenDesktop (any of the following products):
    • XenDesktop 7.6
    • XenDesktop 7.5
    • XenDesktop 7.1
    • XenDesktop 7.0
    • XenDesktop 5.6 Feature Pack 1
    • XenDesktop 5.6
    • XenDesktop 5.5
    • XenDesktop 5
  • Citrix VDI-in-a-Box
    • VDI-in-a-Box 5.3
    • VDI-in-a-Box 5.2
  • You can use Receiver for Windows 4.3 browser-based access in conjunction with StoreFront Receiver for Web and Web Interface, with - or without - the NetScaler Gateway plug-in.
    • StoreFront 3.0.x, 2.6, 2.5 and 2.1

      Provides direct access to StoreFront stores.

    • StoreFront configured with a Receiver for Web site

      Provides access to StoreFront stores from a web browser. For the limitations of this deployment, refer to "Important considerations" in Receiver for Web sites.

    Web Interface in conjunction with the NetScaler VPN client:
    • Web Interface 5.4 for Windows web sites.

      Provides access to virtual desktops and apps from a Web browser.

    • Web Interface 5.4 for Windows with XenApp Services or XenDesktop Services sites
  • Ways to deploy Receiver to users:
    • Enable users to download from, then configure using an email or services address in conjunction with StoreFront.
    • Offer to install from Citrix Receiver for Web site (configured with StoreFront).
    • Offer to install Receiver from Citrix Web Interface 5.4.
    • Deploy using Active Directory (AD) Group Policy Objects (GPOs).
    • Deploy using Microsoft System Center 2012 Configuration Manager.



Citrix Receiver for Windows supports HTTPS and ICA-over-TLS connections through any one of the following configurations.

  • For LAN connections:
    • StoreFront using StoreFront services or Receiver for Web sites
    • Web Interface 5.4 for Windows, using Web Interface or XenApp Services sites

    For information about domain-joined and non-domain-joined devices, refer to the XenDesktop 7 documentation.

  • For secure remote or local connections:
    • Citrix NetScaler Gateway 10.5
    • Citrix NetScaler Gateway 10.1
    • Citrix Access Gateway Enterprise Edition 10
    • Citrix Access Gateway Enterprise Edition 9.x
    • Citrix Access Gateway VPX

    Windows domain-joined, managed devices (local and remote, with or without VPN) and non-domain joined devices (with or without VPN) are supported.

    For information about the NetScaler Gateway and Access Gateway versions supported by StoreFront, see StoreFront system requirements.

Note: References to NetScaler Gateway in this topic also apply to Access Gateway, unless otherwise indicated.

About secure connections and certificates

Note: For additional information about security certificates, refer to topics under Secure connections and Secure communications.

Private (self-signed) certificates

If a private certificate is installed on the remote gateway, the root certificate for the organization's certificate authority must be installed on the user device to successfully access Citrix resources using Receiver.

Note: If the remote gateway's certificate cannot be verified upon connection (because the root certificate is not included in the local keystore), an untrusted certificate warning appears. If a user chooses to continue through the warning, a list of apps is displayed but the apps will not start.

Installing root certificates on user devices

For information about installing root certificates on user devices as well as configuring Web Interface for certificate use, see Secure Receiver communication.

Wildcard certificates

Wildcard certificates are used in place of individual server certificates for any server within the same domain. Receiver for Windows supports wildcard certificates, however they should only be used in accordance with your organization's security policy. In practice, alternatives to wildcard certificates, such as a certificate containing the list of server names within the Subject Alternative Name (SAN) extension, could be considered. Such certificates can be issued by both private and public certificate authorities.

Intermediate certificates and the NetScaler Gateway

If your certificate chain includes an intermediate certificate, the intermediate certificate must be appended to the NetScaler Gateway server certificate. For information, see Configuring Intermediate Certificates.


For connections to StoreFront, Receiver supports the following authentication methods:
  Receiver for Web using browsers StoreFront Services site (native) StoreFront XenApp Services site (native) NetScaler to Receiver for Web (browser) NetScaler to StoreFront Services site (native)
Anonymous Yes Yes      
Domain Yes Yes Yes Yes* Yes*
Domain pass-through Yes Yes Yes    
Security token       Yes* Yes*
Two-factor (domain with security token)       Yes* Yes*
SMS       Yes* Yes*
Smart card Yes Yes No    
User certificate       Yes (NetScaler plug-in) Yes (NetScaler plug-in)

* With or without the NetScaler plugin installed on the device.

Note: Receiver for Windows 4.3 supports 2FA (domain plus security token) through NetScaler Gateway to StoreFront native service.
For connections to Web Interface 5.4, Receiver supports the following authentication methods (Web Interface uses the term "Explicit" for domain and security token authentication):
  Web Interface (browsers) Web Interface XenApp Services site NetScaler to Web Interface (browser) NetScaler to Web Interface XenApp Services site
Anonymous Yes      
Domain Yes Yes Yes*  
Domain pass-through Yes Yes    
Security token     Yes*  
Two-factor (domain with security token)     Yes*  
SMS     Yes*  
Smart card Yes No    
User certificate     Yes (NetScaler plug-in)  

* Available only in deployments that include NetScaler Gateway, with or without the associated plug-in installed on the device.

For information about authentication, see Configuring Authentication and Authorization in the NetScaler Gateway documentation and Manage topics in the StoreFront documentation. For information about authentication methods supported by Web Interface, see Configuring Authentication for the Web Interface.


Receiver for Windows 4.x can be used to upgrade Receiver for Windows 3.x as well as Citrix online plug-in 12.x. For information more information on upgrading, see Considerations when upgrading.

Note: If you are upgrading from Receiver 3.4 to version 4.2.100, follow the instructions provided in the Upgrading from Receiver 3.4 to Receiver 4.2.100 Guide. Version 4.2.100 does not support in-place upgrades by the end user. The IT administrator must prepare the environment, so all users on the network can complete the upgrade successfully. The information provided in the upgrade guide provides step by step instructions.


  • .NET Framework requirements
    • .NET 3.5 Service Pack 1 is required by the Self-Service Plug-in, which allows users to subscribe to and launch desktops and applications from the Receiver window or from a command line. For more information, see Configure and install Receiver for Windows using command-line parameters.
    • The .NET 2.0 Service Pack 1 and Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package are required to ensure that the Receiver icon displays correctly. The Microsoft Visual C++ 2005 Service Pack 1 package is included with .NET 2.0 Service Pack 1, .NET 3.5, and .NET 3.5 Service Pack 1; it is also available separately.
    • For XenDesktop connections: To use the Desktop Viewer, .NET 2.0 Service Pack 1 or later is required. This version is required because, if Internet access is not available, certificate revocation checks slow down connection startup times. The checks can be turned off and startup times improved with this version of the Framework but not with .NET 2.0.
  • For information about using Receiver with Microsoft Lync Server 2013 and the Microsoft Lync 2013 VDI Plug-in for Windows, see XenDesktop, XenApp and Citrix Receiver Support for Microsoft Lync 2013 VDI Plug-in.
  • Supported connection methods and network transports:
      Important: If stores are configured in StoreFront with a Transport type of HTTP, you must add the following key value to the registry key HKLM\Software\[Wow6432Node\]Citrix\AuthManager: ConnectionSecurityMode=Any.

      See CTX 134341 for additional values, which may be required.

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