Jump to content
Welcome to our new Citrix community!
  • 0

"This version of Citrix Workspace does not support selected encryption" after launching an app after a CWA upgrade (2006.1 to 2009.6)

Nick Panaccio


We're seeing a number of devices throwing this error and crashing after launching any published app, after upgrading CWA 2006.1 to 2009.6. It's worth noting that we also have HDX RTME 2.9 LTSR installed, and I think that may be part of the issue based on the error in the event log:


Faulting application name: WFICA32.EXE, version:, time stamp: 0x5f747f33
Faulting module name: SOCKSProxyPlugin.dll, version:, time stamp: 0x5e51765f
Exception code: 0xc0000005
Fault offset: 0x000422bc
Faulting process id: 0x1620
Faulting application start time: 0x01d6bf787fd53c05
Faulting application path: C:\PROGRA~2\Citrix\ICACLI~1\WFICA32.EXE
Faulting module path: C:\PROGRA~2\Citrix\ICACLI~1\SOCKSProxyPlugin.dll
Report Id: 2c3943d9-9a42-4564-8c35-785f3d18658a
Faulting package full name:

Anyone ever come across this before? This is literally our first upgrade attempt after moving from Receiver 4.9 LTSR to CWA 2006.1. https://support.citrix.com/article/CTX133536 doesn't appear to help our situation.


Link to comment

1 answer to this question

Recommended Posts

  • 0

In case anyone else ever comes across this, HDX RTME 2.9 LTSR is definitely the issue in our environment. Here's how we reproduce it:


  1. Install CWA 2006.1
  2. Install HDX RTME 2.9 LTSR
  3. Attempt to install any newer CWA client

This is when the errors appear. Even uninstalling HDX RTME doesn't help, which led us to the HKLM\SOFTWARE\WOW6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ICA 3.0\VirtualDriverEx registry value. The HDX RTME installer is not removing HDX RealTime Media Engine,SOCKSProxyPlugin,UDPGatewayPlugin from the above registry key. Even with HDX RTME installed, those 3 entries cause the issues. I can reproduce this on fresh builds with their first CWA install, and old devices.


TL;DR: Uninstalling HDX RTME and deleting that VirtualDriverEx registry value resolved the issue for us.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...