Black Box on screen on Mac Receiver version 12.9.0, 12.9.1 and Workspace app for Mac 18.08.

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.

Using XenApp VD Agent 7.15 CU2, we have big black boxes show up on screen during an active ICA session that correlate to applications that are minimized.

Related:

  • No Related Posts

Error “There is a problem with this Windows Installer package…….. Contact your support personnel or package vendor” when Installing Windows Receiver

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.

Installation of Receiver fails with the following error,

“There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor”

Running Microsoft Fixit throws the following error,

“C:WindowsSystem32Rundll32.exe is missing”

\No Trolley Express log is generated under C:UsersusernameAppDataLocalTemp

In Event Viewer we see the following error from MsiInstaller,

Event 11721, MsiInstaller

Product Online Plug-in — Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: CtxCliLkdnInstallPerMachine.UID, location: C:Program FilesICA Client, command: rundll32.exe”C:Program FilesCitrixICA Clienticaconfs.dll”, ApplyConfigurationA import –replace -f -all “C:Program FilesCitrixICA ClientConfiguration” –RunAsAdmin.

Related:

  • No Related Posts

Error: “This version of Citrix Receiver does not support selected encryption” When Launching XenApp Application

This issue has been resolved. The fix was first introduced with a special release of Receiver 3.4 CU2. This update had also been included with the 4.x version release of Receiver for Windows on June 26, 2013.

There is also a fix for this issue in HDX RealTime Optimization Pack 1.4.200. This update has also been included with 1.5 and all later versions of HDX RealTime Optimization Pack.

Solution 1

Note: If you are still experiencing this error, you may have a corrupt Receiver installation. Try the following steps, if a fresh installation is required:

  1. Download and Run – CTX137494 – Receiver Clean-Up Utility
  2. Verify in Control Panel > Programs and Features or Add/Remove Programs to confirm that the Citrix Receiver software is no longer present.
  3. Restart your computer.
  4. Download and install the latest Citrix Receiver.

Note: If the issue persists, restart your computer and try again.

Solution 2

If solution 1 did not resolve the issue and you are using Receiver 4.2 or newer, then try increasing the timeout by adding the following key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

On 32-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

On 64-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

Note: Registry key values are typically listed in decimal format, unless specified otherwise.

Same VdLoadUnloadTimeout registry setting is used in two places with two different default values:

  • By WfcRun32.exe, when it has seen an error from the engine, and needs to kill the WfIca32.exe process. It waits for this registry setting with a default of 1 second before terminating the process.
  • By WfIca32.exe, when it is loading virtual drivers. It waits for this registry setting with a default of 5 seconds for the Virtual driver to load.


If you set the registry setting, then both processes will use the value that you set (in seconds). There is no upper limit.

Lower limits are forced. If the value is less than 1 for WfcRun32.exe, it will be forced to 1. If the value is less than 5 for WfIca32.exe, it will be forced to 5.


Solution 3

Misconfigured registry value if there:

If registry key exists set it to default value =True

Location: HKLMSOFTWAREWow6432NodePoliciesCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownLogonLocal Credentials

Name: LegacyLocalUserNameAndPassword

Type: REG_SZ

Data: (Default)=True

Note:

when we uninstall receiver check if all Citrix related keys under HKLMSOFTWAREWow6432Node keys are removed properly.

How Do I Articles

Related:

  • No Related Posts

Error: “This version of Citrix Receiver does not support selected encryption” When Launching XenApp Application

This issue has been resolved. The fix was first introduced with a special release of Receiver 3.4 CU2. This update had also been included with the 4.x version release of Receiver for Windows on June 26, 2013.

There is also a fix for this issue in HDX RealTime Optimization Pack 1.4.200. This update has also been included with 1.5 and all later versions of HDX RealTime Optimization Pack.

Solution 1

Note: If you are still experiencing this error, you may have a corrupt Receiver installation. Try the following steps, if a fresh installation is required:

  1. Download and Run – CTX137494 – Receiver Clean-Up Utility
  2. Verify in Control Panel > Programs and Features or Add/Remove Programs to confirm that the Citrix Receiver software is no longer present.
  3. Restart your computer.
  4. Download and install the latest Citrix Receiver.

Note: If the issue persists, restart your computer and try again.

Solution 2

If solution 1 did not resolve the issue and you are using Receiver 4.2 or newer, then try increasing the timeout by adding the following key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

On 32-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

On 64-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

Note: Registry key values are typically listed in decimal format, unless specified otherwise.

Same VdLoadUnloadTimeout registry setting is used in two places with two different default values:

  • By WfcRun32.exe, when it has seen an error from the engine, and needs to kill the WfIca32.exe process. It waits for this registry setting with a default of 1 second before terminating the process.
  • By WfIca32.exe, when it is loading virtual drivers. It waits for this registry setting with a default of 5 seconds for the Virtual driver to load.


If you set the registry setting, then both processes will use the value that you set (in seconds). There is no upper limit.

Lower limits are forced. If the value is less than 1 for WfcRun32.exe, it will be forced to 1. If the value is less than 5 for WfIca32.exe, it will be forced to 5.


Solution 3

Misconfigured registry value if there:

If registry key exists set it to default value =True

Location: HKLMSOFTWAREWow6432NodePoliciesCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownLogonLocal Credentials

Name: LegacyLocalUserNameAndPassword

Type: REG_SZ

Data: (Default)=True

Note:

when we uninstall receiver check if all Citrix related keys under HKLMSOFTWAREWow6432Node keys are removed properly.

How Do I Articles

Related:

  • No Related Posts

Error: “This version of Citrix Receiver does not support selected encryption” When Launching XenApp Application

This issue has been resolved. The fix was first introduced with a special release of Receiver 3.4 CU2. This update had also been included with the 4.x version release of Receiver for Windows on June 26, 2013.

There is also a fix for this issue in HDX RealTime Optimization Pack 1.4.200. This update has also been included with 1.5 and all later versions of HDX RealTime Optimization Pack.

Solution 1

Note: If you are still experiencing this error, you may have a corrupt Receiver installation. Try the following steps, if a fresh installation is required:

  1. Download and Run – CTX137494 – Receiver Clean-Up Utility
  2. Verify in Control Panel > Programs and Features or Add/Remove Programs to confirm that the Citrix Receiver software is no longer present.
  3. Restart your computer.
  4. Download and install the latest Citrix Receiver.

Note: If the issue persists, restart your computer and try again.

Solution 2

If solution 1 did not resolve the issue and you are using Receiver 4.2 or newer, then try increasing the timeout by adding the following key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

On 32-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

On 64-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

Note: Registry key values are typically listed in decimal format, unless specified otherwise.

Same VdLoadUnloadTimeout registry setting is used in two places with two different default values:

  • By WfcRun32.exe, when it has seen an error from the engine, and needs to kill the WfIca32.exe process. It waits for this registry setting with a default of 1 second before terminating the process.
  • By WfIca32.exe, when it is loading virtual drivers. It waits for this registry setting with a default of 5 seconds for the Virtual driver to load.


If you set the registry setting, then both processes will use the value that you set (in seconds). There is no upper limit.

Lower limits are forced. If the value is less than 1 for WfcRun32.exe, it will be forced to 1. If the value is less than 5 for WfIca32.exe, it will be forced to 5.


Solution 3

Misconfigured registry value if there:

If registry key exists set it to default value =True

Location: HKLMSOFTWAREWow6432NodePoliciesCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownLogonLocal Credentials

Name: LegacyLocalUserNameAndPassword

Type: REG_SZ

Data: (Default)=True

Note:

when we uninstall receiver check if all Citrix related keys under HKLMSOFTWAREWow6432Node keys are removed properly.

How Do I Articles

Related:

  • No Related Posts

Error: “This version of Citrix Receiver does not support selected encryption” When Launching XenApp Application

This issue has been resolved. The fix was first introduced with a special release of Receiver 3.4 CU2. This update had also been included with the 4.x version release of Receiver for Windows on June 26, 2013.

There is also a fix for this issue in HDX RealTime Optimization Pack 1.4.200. This update has also been included with 1.5 and all later versions of HDX RealTime Optimization Pack.

Solution 1

Note: If you are still experiencing this error, you may have a corrupt Receiver installation. Try the following steps, if a fresh installation is required:

  1. Download and Run – CTX137494 – Receiver Clean-Up Utility
  2. Verify in Control Panel > Programs and Features or Add/Remove Programs to confirm that the Citrix Receiver software is no longer present.
  3. Restart your computer.
  4. Download and install the latest Citrix Receiver.

Note: If the issue persists, restart your computer and try again.

Solution 2

If solution 1 did not resolve the issue and you are using Receiver 4.2 or newer, then try increasing the timeout by adding the following key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

On 32-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

On 64-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

Note: Registry key values are typically listed in decimal format, unless specified otherwise.

Same VdLoadUnloadTimeout registry setting is used in two places with two different default values:

  • By WfcRun32.exe, when it has seen an error from the engine, and needs to kill the WfIca32.exe process. It waits for this registry setting with a default of 1 second before terminating the process.
  • By WfIca32.exe, when it is loading virtual drivers. It waits for this registry setting with a default of 5 seconds for the Virtual driver to load.


If you set the registry setting, then both processes will use the value that you set (in seconds). There is no upper limit.

Lower limits are forced. If the value is less than 1 for WfcRun32.exe, it will be forced to 1. If the value is less than 5 for WfIca32.exe, it will be forced to 5.


Solution 3

Misconfigured registry value if there:

If registry key exists set it to default value =True

Location: HKLMSOFTWAREWow6432NodePoliciesCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownLogonLocal Credentials

Name: LegacyLocalUserNameAndPassword

Type: REG_SZ

Data: (Default)=True

Note:

when we uninstall receiver check if all Citrix related keys under HKLMSOFTWAREWow6432Node keys are removed properly.

How Do I Articles

Related:

  • No Related Posts

Error: “This version of Citrix Receiver does not support selected encryption” When Launching XenApp Application

This issue has been resolved. The fix was first introduced with a special release of Receiver 3.4 CU2. This update had also been included with the 4.x version release of Receiver for Windows on June 26, 2013.

There is also a fix for this issue in HDX RealTime Optimization Pack 1.4.200. This update has also been included with 1.5 and all later versions of HDX RealTime Optimization Pack.

Solution 1

Note: If you are still experiencing this error, you may have a corrupt Receiver installation. Try the following steps, if a fresh installation is required:

  1. Download and Run – CTX137494 – Receiver Clean-Up Utility
  2. Verify in Control Panel > Programs and Features or Add/Remove Programs to confirm that the Citrix Receiver software is no longer present.
  3. Restart your computer.
  4. Download and install the latest Citrix Receiver.

Note: If the issue persists, restart your computer and try again.

Solution 2

If solution 1 did not resolve the issue and you are using Receiver 4.2 or newer, then try increasing the timeout by adding the following key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

On 32-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

On 64-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

Note: Registry key values are typically listed in decimal format, unless specified otherwise.

Same VdLoadUnloadTimeout registry setting is used in two places with two different default values:

  • By WfcRun32.exe, when it has seen an error from the engine, and needs to kill the WfIca32.exe process. It waits for this registry setting with a default of 1 second before terminating the process.
  • By WfIca32.exe, when it is loading virtual drivers. It waits for this registry setting with a default of 5 seconds for the Virtual driver to load.


If you set the registry setting, then both processes will use the value that you set (in seconds). There is no upper limit.

Lower limits are forced. If the value is less than 1 for WfcRun32.exe, it will be forced to 1. If the value is less than 5 for WfIca32.exe, it will be forced to 5.


Solution 3

Misconfigured registry value if there:

If registry key exists set it to default value =True

Location: HKLMSOFTWAREWow6432NodePoliciesCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownLogonLocal Credentials

Name: LegacyLocalUserNameAndPassword

Type: REG_SZ

Data: (Default)=True

Note:

when we uninstall receiver check if all Citrix related keys under HKLMSOFTWAREWow6432Node keys are removed properly.

How Do I Articles

Related:

  • No Related Posts

Error: “This version of Citrix Receiver does not support selected encryption” When Launching XenApp Application

This issue has been resolved. The fix was first introduced with a special release of Receiver 3.4 CU2. This update had also been included with the 4.x version release of Receiver for Windows on June 26, 2013.

There is also a fix for this issue in HDX RealTime Optimization Pack 1.4.200. This update has also been included with 1.5 and all later versions of HDX RealTime Optimization Pack.

Solution 1

Note: If you are still experiencing this error, you may have a corrupt Receiver installation. Try the following steps, if a fresh installation is required:

  1. Download and Run – CTX137494 – Receiver Clean-Up Utility
  2. Verify in Control Panel > Programs and Features or Add/Remove Programs to confirm that the Citrix Receiver software is no longer present.
  3. Restart your computer.
  4. Download and install the latest Citrix Receiver.

Note: If the issue persists, restart your computer and try again.

Solution 2

If solution 1 did not resolve the issue and you are using Receiver 4.2 or newer, then try increasing the timeout by adding the following key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

On 32-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWARECitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

On 64-bit Windows:

Location: HKEY_LOCAL_MACHINESOFTWAREWow6432nodeCitrixICA Client

Name: VdLoadUnLoadTimeOut

Type: REG_DWORD

Data: Any value in seconds (Decimal)

Note: Registry key values are typically listed in decimal format, unless specified otherwise.

Same VdLoadUnloadTimeout registry setting is used in two places with two different default values:

  • By WfcRun32.exe, when it has seen an error from the engine, and needs to kill the WfIca32.exe process. It waits for this registry setting with a default of 1 second before terminating the process.
  • By WfIca32.exe, when it is loading virtual drivers. It waits for this registry setting with a default of 5 seconds for the Virtual driver to load.


If you set the registry setting, then both processes will use the value that you set (in seconds). There is no upper limit.

Lower limits are forced. If the value is less than 1 for WfcRun32.exe, it will be forced to 1. If the value is less than 5 for WfIca32.exe, it will be forced to 5.


Solution 3

Misconfigured registry value if there:

If registry key exists set it to default value =True

Location: HKLMSOFTWAREWow6432NodePoliciesCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownLogonLocal Credentials

Name: LegacyLocalUserNameAndPassword

Type: REG_SZ

Data: (Default)=True

Note:

when we uninstall receiver check if all Citrix related keys under HKLMSOFTWAREWow6432Node keys are removed properly.

How Do I Articles

Related:

  • No Related Posts

Multiple Vulnerabilities in OpenSSL Affecting Cisco Products: March 2021

On March 25, 2021, the OpenSSL Project released a security advisory, OpenSSL Security Advisory [25 March 2021], that disclosed two vulnerabilities.

Exploitation of these vulnerabilities could allow an attacker to use a valid non-certificate authority (CA) certificate to act as a CA and sign a certificate for an arbitrary organization, user or device, or to cause a denial of service (DoS) condition.

This advisory will be updated as additional information becomes available.

This advisory is available at the following link:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-openssl-2021-GHY28dJd

Security Impact Rating: High

CVE: CVE-2021-3449,CVE-2021-3450

Related:

  • No Related Posts

Chrome Launches with Error: “Extension might have been corrupted and unable to connect to websocket” with Citrix UPM

Make the following modifications to UPM policy:

Files to Synchronize:

AppDataLocalGoogleChromeUserDataFirst Run

AppDataLocalGoogleChromeUserDataLocal State

AppDataLocalGoogleChromeUserDataBookmarks

AppDataLocalGoogleChromeUserDataFavicons

AppDataRoamingGoogleChromeUserDataHistory

AppDataRoamingGoogleChromeUserDataDefaultPrefrences

AppDataLocalGoogleChromeUserDataCustom Dictionary.txt

Folders to Mirror:

AppDataLocalGoogleChromeUserDataDefault

Directories to synchronize:

AppDataLocalGoogleChromeUserDataDefault

Disable profile streaming

Related:

  • No Related Posts