January 20, 2021 You can uninstall Citrix Workspace app for Windows using the Windows Programs and Features utility (Add or Remove Programs). The Citrix Workspace app desktop clean-up tool allows you to delete the desktop shortcuts that remain after you uninstall Citrix Workspace app for Windows (Store). The Citrix Workspace app desktop clean-up tool is available for download from here.You can run this tool using the command line interface. Receiver Clean-Up Utility. The Receiver Clean-Up utility is designed to assist with the following scenarios: When errors occur during upgrade from an earlier version of Receiver or Online Plug-in; When unexpected behavior or performance is experienced after upgrade from an earlier Receiver or Online Plug-in. Mar 19, 2021 Citrix Cleanup Utility – Click here to run the Citrix Clean Utility. This is recommend to be run before installing any new Citrix receiver. Citrix Workspace 1911 (for Windows) – Click here to download the Citrix Receiver Citrix Workspace 1911 (for Windows). Citrix Receiver 2002 (for MAC) – Click here to download the Citrix Receiver.
I am having issues on various W7 builds where Receiver 4.1/4.2 will not launch ICA files. When you try to open a published app from either the StoreFront Web site or Receiver self service, it displays the error 'Cannot start app. Please contact your helpdesk'.
I have uninstalled Receiver, using the Receiver cleanup utility, and manually removed any Receiver registry keys/folders etc before re-installing but this does not make any difference.
When verbose logging is enabled, a problem.txt Self Service log is produced when trying to launch an app. This shows a 'launch error code 3' when trying to launch the ICA file.
Any idea what this means and how I go about resolving the issue? Controllers for mac gaming.
How To Run Citrix Cleanup Utility
If I launch the ICA file manually from Windows Explorer, the published app will launch successfully.
Remove Citrix Receiver
This problem is not happening on all machines and so I don't believe it is a StoreFront issue. (StoreFront 2.6 on Windows Server 2012 R2 is being used).