Installation Issues with Receiver While Upgrading OS to Windows 10

This article is intended for Citrix administrators and technical teams only.Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information

Users need to upgrade their Receiver for Windows to 4.3 before performing a Windows 10 OS in-place upgrade.

Note: Receiver 4.2 and earlier versions are not supported by Windows 10.

Issue description

If you are using Receiver for Windows prior to 4.3 installed on the machine and try to upgrade from Windows 7, Windows 8 or Windows 8.1 to Windows 10, you might not be able to uninstall Receiver through Add/Remove Programs. Upgrade or uninstallation fails.

Scenarios

Non-working Scenario

If a computer with Windows 7, Windows 8 or Windows 8.1 and Receiver for Windows 4.2.100 or earlier is upgraded to Windows 10, users are unable to remove Receiver using the control panel. The following error message is displayed. Upgrading to Receiver for Windows 4.3 also fails.

User-added image

Working scenario – 1

  1. Upgrade Receiver for Windows to 4.3.

  2. Upgrade to the computer to Windows 10.

Working scenario – 2

  1. On a computer which does not have Receiver installed, upgrade to Windows 10.

  2. Install Receiver for Windows 4.3

Related:

  • No Related Posts

Storefront – generating event viewer warning – ” The Receiver for Windows package file could not be found at the path”

Updated the Web.config file with the correct path for the MAC receiver client on the storefront server.


1. Navigate to the following path on the storefront server C:inetpubwwwrootCitrix(storename)Web

2. Open the Web.config file.

3. Locate the Win32 and macOS file paths and update accordingly.

<pluginAssistant enabled=”true” upgradeAtLogin=”false” showAfterLogin=”false”>

<win32 path=”http://downloadplugins.citrix.com/Windows/CitrixReceiverWeb.exe” />

<macOS path=”http://downloadplugins.citrix.com/Mac/CitrixReceiverWeb.dmg”

Related:

  • No Related Posts

Profile Management: File Type Association (FTA) Fails to Roam on Windows 10 and Windows Server 2016

On Windows 10 and Windows Server 2016, Microsoft introduced a new security mechanism to check settings of default applications in the registry. Occasionally, the Windows Profile Service changes the security settings of the user registry entry. As a result, the settings of default applications are reset to Microsoft recommended defaults.

When testing Windows 10 and Windows Server 2016 without a VDA installed, this issue does not happen. Citrix is working with Microsoft to provide a long term solution. In the meantime, use the following workaround to avoid this issue.

Related:

  • No Related Posts

Legacy graphics mode with Windows 8, 8.1, 10, Server 2012, R2 & 2016

Legacy graphics is a host (computer) policy and its use should be treated as an always on or always off. Behavior will differ between Workstation OS VDA and Server OS VDA. You should only ever be using legacy mode for OS’s for which it was designed for: i.e. Windows 7, Windows 2008 R2 and earlier (also called Legacy OS’s). Legacy graphics is highly optimised for legacy OSs and should be regarded as the first choice for those operating systems unless other factors are involved.

Legacy graphics mode is not tested or supported with modern operating systems: Windows Desktop OS: 8, 8.1, 10 or Windows Server 2012, 2012 R2 & Windows Server 2016.

Thinwire plus (aka: TW+ or compatibility mode) should be used instead and is the replacement for legacy mode.

The above doesn’t necessarily mean it will not work with modern operating systems. However, issues like: grey, frozen and black screens have been observed and reported.

Before calling your support representative please test the issue against Thinwire, the modern graphics delivery method.

Related:

  • No Related Posts

Error Message: Cannot Start Desktop “[DesktopName]” When Trying to Launch a Desktop VDA

Open an RDP connection to the Desktop VDA that cannot be launched and check if there is another existing connected/disconnected session in the Task manager. If that is the case then logoff the session and try to launch the published Desktop again.

Note: If the session cannot be logged of from the Task Manager, that probably is because it is an administrator account. Administrator accounts cannot be logged off from the Task Manager. In that case try to contact the person who owns the administrator account and request to logoff. Otherwise, proceed to reboot the host. Then try to launch the published Desktop again.

Related:

  • No Related Posts