Error: “Certificate with key size greater than RSA512 or DSA512 bits not supported” on NetScaler

To resolve this issue, apply any or both of the following resolutions, as required:

After applying the required resolution, the additional ciphers are available and you can add a certificate that has a key size greater than 512 bits. The NetScaler appliance supports certificates with key size 512, 1024, 2048, and 4096 bits.

Related:

  • No Related Posts

Error: “Certificate with key size greater than RSA512 or DSA512 bits not supported” on NetScaler

To resolve this issue, apply any or both of the following resolutions, as required:

After applying the required resolution, the additional ciphers are available and you can add a certificate that has a key size greater than 512 bits. The NetScaler appliance supports certificates with key size 512, 1024, 2048, and 4096 bits.

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

Error “Your smart card does not have a valid certificate” when using Citrix Receiver for iOS 7.3 with iOS 11

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.

When users try to connect to Storefront or NetScaler Gateway using smart cards (PIV or CAC) using Citrix Receiver 7.3 for iOS or earlier versions on iOS 11 devices, users may receive the following error message “Your smart card does not have a valid certificate”.

User-added image

However, users connecting from iOS 9 and 10 devices will not face this error and will be able to use smart cards to authenticate to Storefront or NetScaler Gateway.

Related:

  • No Related Posts

Error “Your smart card does not have a valid certificate” when using Citrix Receiver for iOS 7.3 with iOS 11

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.

When users try to connect to Storefront or NetScaler Gateway using smart cards (PIV or CAC) using Citrix Receiver 7.3 for iOS or earlier versions on iOS 11 devices, users may receive the following error message “Your smart card does not have a valid certificate”.

User-added image

However, users connecting from iOS 9 and 10 devices will not face this error and will be able to use smart cards to authenticate to Storefront or NetScaler Gateway.

Related:

  • No Related Posts