- Fixed Issues
- Known Issues
Compared to: Citrix Receiver for Windows 4.4 CU4 (4.4.4000)
Receiver for Windows 4.4 CU5 (4.4.5000) contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, 4.2, 4.2.100, 4.3, 4.3.100, 4.4, 4.4 CU1 (4.4.1000), 4.4 CU2 (4.4.2000), 4.4 CU3 (4.4.3000), and 4.4 CU4 (4.4.4000), plus the following, new fixes:
With HDX 3D Pro enabled on a VDA, using certain third-party applications can cause the VDA to disconnect.
To enable the fix, set the following registry keys:
When you change the default printer on the user device from printer A to printer B and then back to printer A, the change might not be reflected in the active user session until you disconnect and reconnect the session.
If a USB device is listed as an unknown device on the user device, the USB device might not be available for redirection. The issue occurs if the USB device is plugged in before the session starts.
When you assign a desktop group to an external client IP address according to the procedure described in Knowledge Center article CTX128232, the published desktop might fail to start when you access through NetScaler Gateway. The following error message might appear:
"Cannot start app"
A published application window might cover the complete screen when maximized using the Windows Aero Snap feature.
When a user is running multiple sessions with Local App Access/HDX seamless apps enabled, applications and desktops might get shuffled intermittently. With this fix, Local App Access/HDX seamless apps can be enabled in only one session and is disabled for other, concurrent sessions of the same user.
When you launch Skype for Business from Citrix Receiver for Windows and attempt to make a video call or capture a photo using the webcam on Microsoft Surface Pro 4 devices, the following error message might appear:
"Can’t connect to this camera. Close any active conversations or other programs that are using your camera, and then try again."
Citrix Receiver for Windows might exit unexpectedly when disconnecting from a VDA that is using an integrated webcam. The issue occurs when you disconnect from the VDA while the webcam is running.
Attempts by users connecting through NetScaler Gateway to a Store through Citrix Receiver for Windows might fail, and the following error message appears:
"Cannot connect to server"
Windows Media live streams might fail to fetch content from the client.
The logon prompt might not appear when you attempt to refresh applications in Citrix Receiver for Windows after logging off.
When using the Epic Hyperspace software for medical dictation, the dictation recorder might become unresponsive on the user device while recording.
File type association might fail to open the associated document when you set the registry value "DisableStubCreation" to "true" under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Dazzle on 32-bit Windows and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle on 64-bit Windows. The issue occurs when the "%1" parameter is missing for the relevant file name extension under the registry key HKEY_CURRENT_USER\SOFTWARE\Classes\Dazzle.<appname>.<extension>.1\shell\open\command.
When you add a store through the group policy settings or the command line and configure reconnect at Windows logon, Citrix Receiver for Windows might not automatically reconnect at Windows logon.
With the local security setting "Lock Workstation," located under the policy "Interactive logon: Smart card removal behavior" set in a user session, the session might not be locked when you remove the smart card reader from that session.
When the SCardListReaderGroup API is called in a user session from the server, Citrix Receiver for Windows might not execute the API that is called on the client side.
This fix provides improved support for sounds that play for a short period of time when using high quality audio.
When using the customized phrase feature on the Input Method Editor (IME) language bar, certain characters might randomly get dropped in a user session.
The application desktop toolbar (appbar) might no longer work if the operating system of the user device is Microsoft Windows 10, and the appbar is started through a published desktop. The application might start, but the appbar does not respond to subsequent actions.
Occasionally, when using the Shift key along with any arrow key, the Shift key might not be released in a seamless application.
In a multi-monitor environment, when you restore a seamless window from full-screen to its original size and then drag it back to the original screen, the window might be clipped incorrectly. As a result, only a partial window is visible. The issue occurs with seamless windows that that are wider than the monitor and thus partially off-screen.
When you start an application in seamless mode, a second progress bar might appear for a few seconds and then disappear after the first progress bar disappears.
Double-tapping on a device's touchscreen might not work for some applications within a user session.
When you click the taskbar icons to switch the focus between the windows of a third-party application in a seamless session, the corresponding window of the third-party application might fail to appear in the foreground.
When you change the resolution of the user device while one of the mouse buttons is in the down state, seamless apps might not be able to receive the mouse up state for that mouse event. As a result, the mouse capture is lost.
When using a published version of the Microsoft Paint application with a touch-enabled device, an incorrect drawing might appear. The issue occurs when you move the window from the default position, causing the drawing to appear in an incorrect position.
When applications are subscribed using the Self-Service plug-in and they have the "prefer" keyword configured on the Citrix Delivery Controller, shortcuts and category folders for applications might fail to refresh on the user device. The application shortcuts might not appear under the desktop or Start menu when they are moved or deleted. When the shortcut is moved to a different folder, the existing shortcut and folder are not removed.
The Japanese characters that appear in the title and footer sections of the Citrix Receiver for Windows logon dialog box might display incorrectly and can be incomplete. The number of characters that are cut off from the actual length depends on the length of the server name.
The setting "RemoveICAFile" in the client-side Group policy settings or registry might not work when more than one application is closed.
With this fix, there is a behavioral change when ica temp files are created and deleted. When you start multiple seamless applications, the ica temp file for the first application is created, then for subsequent applications, the ica temp files are created and deleted immediately. The ica temp file created for the first application launch is deleted when you close all applications.
Compared to: Citrix Receiver for Windows 4.4 CU3 (4.4.3000)
Receiver for Windows 4.4 CU4 (4.4.4000) contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, 4.2, 4.2.100, 4.3, 4.3.100, 4.4, 4.4 CU1 (4.4.1000), 4.4 CU2 (4.4.2000), and 4.4 CU3 (4.4.3000) plus the following, new fixes:
The user device instances of Outlook and Skype for Business might not close when the logoff policy of local app access is set to terminate the instances.
The CPU usage of the wfica.exe process might be very high in a double hop-scenario and cause VDAs to become slow or unresponsive. The issue occurs when you launch desktop sessions from multiple user devices to a VDA for Server OS while you start other published applications through Citrix Receiver for Windows in desktop sessions.
To enable the fix, set the following registry keys:
When the "Preview on client" option is enabled, printing multiple items in a short interval can result in corrupted data printing while using EMF printer drivers.
A system administrator can configure an application with an access policy rule using the "Set-BrokerAccessPolicyRule" command. In certain scenarios, after setting some conditions through that command, attempts to subscribe the application can fail when the store is configured for "Enable Classic Receiver Experience."
USB redirection might not work for fingerprint devices using a USB 3.0 port that supports "Selective Suspend" with power state D2 before redirection. The devices might fail to wake up during redirection, which can cause the redirection to fail. To enable the fix, set the following registry keys:
Attempts to launch a session might fail with the following error message:
"The ICA file contains an invalid unsigned parameter."
Before you upgrade or replace the new ADMX file, set the ICA file signing related policy "Enable ICA File Signing" to "Not configured."
Note: This Fix, #LC5338, works with StoreFront 3.9 and later versions.
Communication between an ICA session and the WarpDrive application might fail.
When you update the "Display name" or "Application name" in AppCenter or Citrix Studio, the original desktop shortcut might be orphaned or broken instead of getting modified, and a new desktop shortcut with the updated application name is created.
If a session is recovered with Session Reliability and Local App Access is enabled, the Desktop Viewer toolbar might no longer be visible.
Attempts to start a user session immediately after terminating an ICA session might fail if the following registry key is added:
Data: Any value in seconds (Decimal)
After updating to the Windows 10 Anniversary Update (Build 14393), single mouse clicks register as double clicks within an ICA session.
When using the desktop lock appliance, the desktop might not launch and the following error message appears: "HDX engine is not running. Contact Administrator."
Attempts to launch an application from StoreFront might fail after restarting the computer.
The keyboard and mouse might intermittently disconnect when switching between a wired network LAN and WiFi.
With Single Sign-on enabled, attempts to subscribe to applications might fail if one out of two or more farms is unavailable, and the following error message appears:
"Your apps are not available at this time. Please try again in a few minutes or contact your help desk with this information: Cannot contact [Server Name]."
With this fix, selecting the "Reset Receiver" option in Citrix Receiver for Windows might not affect other users in a double-hop scenario.
Attempts to restart an HP tablet with Citrix Receiver for Windows and the Checkpoint USB driver installed and connected to a Thunderbolt USB-C docking station can cause the tablet to become unresponsive. Also, the tablet can experience a fatal exception, displaying a blue screen.
When launching a published desktop session in seamless mode by connecting a remote desktop to a user device, the keyboard shortcut dialog tip window might not appear.
After upgrading Citrix Receiver to version 4.3, certain application icons might not appear.
With local app access enabled, the desktop viewer toolbar might no longer be visible when you dock or undock the device or switch networks.
Note: On systems with Fix #LC6719 installed, the issue can occur with sessions with local app access enabled and running in the foreground, and in double-hop scenarios where the feature is enabled for both hops.
With local app access enabled, switching a VDA session between full-screen mode and windowed mode can cause multiple instances of Citrix Receiver for Windows icons to appear on the taskbar.
Compared to: Citrix Receiver for Windows 4.4 CU2 (4.4.2000)
Receiver for Windows 4.4 CU3 (4.4.3000) contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, 4.2, 4.2.100, 4.3, 4.3.100, 4.4, 4.4 CU1 (4.4.1000), and 4.4 CU2 (4.4.2000) plus the following, new fixes:
File type association might not work when logging on using a roaming user profile and opening an published application.
When you dictate into SpeechMike along with another speech recognition application, the SpeechMike might stop working.
Using the CleanUp.exe process with the silent switch on does not reload Citrix Receiver properly.
The HDX Engine might exit unexpectedly.
Attempts to launch a desktop from a Wyse thin client through NetScaler Gateway 11 might result in the following error message:
"Your client has experienced a problem with authentication to the server."
Sessions might hang or freeze when continuously moving the session window.
This fix provides improved support for sounds that play for a short period of time when using real-time mode for client audio. This fix only applies to medium quality audio.
File type association might not connect the type of file to the correct icon and application when using Windows 8.1 and Windows Server 2012 R2. With this fix, there are two group policies introduced under "SelfService."
1. Enable Default FTA - To enable or disable the default behavior of FTA
2. Enable FTA - To enable or disable the FTA feature
To get the proper file type association icon, disable the group policy "Enable Default FTA."
The file type association (FTA) icon might behave like the default Citrix Receiver for Windows FTA icon when you log on to a published desktop or if you reset the Citrix Receiver for Windows configuration.
Surface Pro 4 and HP Elite webcams might not redirect to a session. Note: Webcam redirection might also fail if the webcam doesn't support the screen resolution.
To fix this, use the following registry key:
Value: <Webcam supported resolution> Example (Surface Pro 4): 1920
Value: <Webcam supported resolution> Example (Surface Pro 4): 1080
Desktops assigned on a client name basis are not enumerated correctly in the SelfService window. This issue occurs when using the StoreFront Unified Experience.
Compared to: Citrix Receiver for Windows 4.4 CU1 (4.4.1000)
Receiver for Windows 4.4 CU2 (4.4.2000) contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, 4.2, 4.2.100, 4.3, 4.3.100, 4.4, and 4.4 CU1 (4.4.1000) plus the following, new fixes:
Flash content does not play correctly from ProofHQ.com when SOLFileHook is enabled.
When using Versions 22 or 184.108.40.2060 of Adobe Flash Player and browsing websites with Flash content, the website URLs are added to the dynamic blacklist and are rendered on the server rather than on the user device.
With the Keyboard Shortcuts policy enabled and the wfica32 process running on a user device, the "Tip: Exiting Full Screen Mode" dialog window might appear when connecting through a Remote Desktop connection. The dialog window fails to accept keyboard and mouse input.
The local on-screen keyboard might appear in the Citrix Receiver for Windows session every time you enter text while using a Microsoft Surface Pro device with an external USB or a wireless keyboard.
With Local App Access enabled, if the applications are launched inside a remote session in full-screen or windowed mode, the application icons might not be shown on the taskbar of the VDA session. The endpoint might display multiple application icons on the taskbar instead of one.
When launching a published desktop session with Local App Access enabled, the Desktop Viewer toolbar might disappear.
When connected to a Local App Access-enabled VDA, the endpoint device's Task Switcher intermittently appears in the VDA session when you press ALT+TAB.
A Local App Access enabled desktop might not render correctly when changing from windowed mode to full-screen mode.
When disconnecting from a VDA with Local App Access enabled, the taskbar might remain in the "Auto-hide" mode.
Attempts to cancel the certificate prompt with the NetScaler client certificate authentication set to "Optional" can cause the launching of a published application to fail with the Unknown client error 1110.
A multiple screen session with fast user switching might show the session only on one screen after reconnecting to the client machine.
If you launch a seamless application from user device 1 and then connect to that user device from user device 2 over RDP, the launched seamless application might go full-screen and overlap the taskbar of user device 1. The issue persists even after minimizing and restoring the application window.
Sessions connected through NetScaler Gateway might become unresponsive while consuming high bandwidth.
When using certain third party software such Cisco WAAS, Citrix Receiver for Windows sessions might disconnect.
This fix addresses a memory issue in an underlying component.
After upgrading to Citrix Receiver for Windows 4.4, attempts to start applications might fail intermittently when you log on for the first time until Citrix Receiver for Windows is restarted. The following error message appears:
"Cannot start app. Please contact your help desk."
Attempts to access apps through Citrix Receiver from StoreFront might fail from certain user devices. After adding the store successfully, the following error message might appear during the enumeration process:
"Cannot Connect to Server
Please check your network and try again
The Single Sign-on process (SSONSvr.exe) might exit unexpectedly or the credentials might not be passed through automatically to the logon screen, causing a prompt to appear to enter the credentials manually.
Citrix Receiver ignores the proxy bypass list in Internet Explorer.
After installing Citrix Receiver for Windows and configuring a store through a registry entry or Group Policy Object (GPO), when you log on for the first time after restarting the Virtual Machine (VM), applications might not enumerate.
With the "Automatically detect settings" option enabled in Microsoft Internet Explorer, application enumeration in Citrix Receiver might be slow.
With Framehawk enabled, the scroll button on a mouse might not perform any action in a XenDesktop 7.8 VDA session. The corresponding VDA side fix is available in XenDesktop 7.9.
Attempts to start applications by clicking the icons from the Start menu can fail intermittently even if you have already logged on.
The wfica32.exe process might exit unexpectedly on the first hop session while using Citrix Receiver for Windows 4.4 and when the user device is an Android device. The issue occurs while attempting to start a published application in a double-hop scenario within the user session.
During the touch and drag gesture, the mouse button might remain in the down state when using a seamless EPIC application. When you release the touch input outside the seamless EPIC application window, the session might become unresponsive.
Citrix Receiver for Windows might exit unexpectedly with the following error message:
"Citrix HDX Engine has stopped working."
When you repeatedly play an .avi file in Windows Media Player, the wfica32.exe process can experience a deadlock and might exit unexpectedly.
When launching a published application over proxy, Citrix Receiver for Windows might exit unexpectedly with the following error message:
"Citrix HDX Engine has stopped working."
The Citrix Authentication Manager (AuthMgrSvr.exe) might exit unexpectedly when you attempt to add an account after installing Citrix Receiver for Windows 4.4 on Windows Vista.
With Local App Access enabled, the session window might be positioned outside the Desktop Viewer window when you restore it from the maximized state.
During the touch and drag gesture, the touch input from Citrix Receiver for Windows might send certain unintended mouse events to the server. This can cause the seamless EPIC application to become unresponsive.
Attempts to open unsubscribed content through StoreFront with Unified Experience might fail with the following error message:
"Unable to launch your application because the required software is not installed."
On non-English language operating systems, the text of the Protocol error 1030 that appears in Receiver for Windows might be garbled.
When using VLC Media Player with skin mode and with Local App Access enabled, the endpoint might display multiple taskbar shortcuts instead of one.
The GoToMeeting icon does not display in the taskbar when opened using the GoToMeeting URL in a published instance of Microsoft Internet Explorer in seamless mode.
When switching among FastConnect API users, the following error message appears:
"Your apps are not available at this time. Please try again in a few minutes."
Additionally, when you log on using the FastConnect API, previous user application shortcuts are not removed from the desktop.
The Citrix Receiver for Windows installation page does not appear in the web interface if an earlier version of Citrix Receiver is installed on the user device.
The wfica32.exe process can consume up to 100% of the CPU.
When you create a store by using the command, "SelfService.exe command, -init –createprovider," for example, "C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe -init -createprovider store https://<StoreFrontURL>/Citrix/store/discovery," the related registry keys are created correctly. However, if you click the Receiver icon in the notification area to access the SelfService user interface, the store is deleted from the registry and the "Add Account" dialog might appear.
The wfica32.exe process can consume up to 100% of the CPU.
The Client Selective Trust (CST) settings might not be retained and the "HDX File Access" prompt appears for the first and subsequent launches even after selecting the "Do not ask me again for this virtual desktop" option. The issue occurs whenever new registries are created for the same VDA under the registry key "HKEY_Current_User\Software\Citrix\Ica Client\Client Selective Trust" even after selecting the option.
Configuring NetScaler to TLSv1.2 can prevent external Windows 7 user devices from adding a StoreFront account. The following error message might appear:
"The Authentication Service could not be contacted."
Compared to: Citrix Receiver for Windows 4.4
Receiver for Windows 4.4 CU1 (4.4.1000) contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, 4.2, 4.2.100, 4.3, 4.3.100, and 4.4 plus the following, new fixes:
When using Citrix Receiver for Windows 4.3, devices connected through USB 3.0 - including keyboards and mouse devices - might stop working and show the error DRIVER_POWER_STATE_FAILURE (0x9f).
Surface Pro Type/Touch cover devices are available for USB redirection. After USB redirection, the mouse cursor/keyboard may no longer work outside the session. Currently, a deny rule has been added at installation to prevent Surface Pro Type/Touch covers devices from redirection. Refer to CTX137939 for more details on how these rules work.
Note: The current fix is limited only for fresh installations of Receiver. For an upgrade, the following deny rule needs to be added manually to the below registry.
For 32-bit OS:
For 64-bit OS:
Edit the DeviceRules value and add specific Deny rules for the USB device.
DENY:vid=045e pid=079A # Microsoft Surface Pro TouchCover
DENY:vid=045e pid=079c # Microsoft Surface Pro Type Cover
DENY:vid=045e pid=07dc # Microsoft Surface Pro 3 Type Cover
DENY:vid=045e pid=07e4 # Microsoft Surface Pro 4 Type Cover with fingerprint reader
DENY:vid=03eb pid=8209 # Surface Pro Atmel maXTouch Digitizer
Follow the same procedure by adding VID and PID for those devices which warrant prevention of redirection.
DENY: vid=xxxx pid=xxxx rule for specific devices has to be on top of the list in devicerules.
When opening Internet Explorer inside a Local App Access session and browsing to a web page with Flash content, and an application is opened and maximized, the contents of the browser’s Flash container remain onscreen.
Attempts to suppress the "Add Account" window might fail when following the instructions in Knowledge Center article CTX135438. With this fix, occasionally the "Add Account" window may pop up again even after closing it after resetting or restarting Citrix Receiver.
If a published application uses a hotkey combination of Ctrl+Alt+[Key], and if Alt+[Key] or Ctrl+[Key] is a Citrix hotkey, the combination is not sent to the server.
When using a seamless session or applications, mouse clicks occasionally do not function as expected.
After installing the URL redirection plugin for the Mozilla Firefox portable browser, a large white box might appear in the lower portion of the browser.
When you run redirector.exe to register/unregister browsers in a session, a pop-up window appears with information that most users find not to be of value. With this enhancement, the pop-up window no longer appears unless you run the redirector.exe command with the /verbose option.
When a published desktop with Local App Access enabled connects, the session window might not respond or can disappear.
The CDViewer.exe process might not respond when both Local App Access and USB redirection are enabled in Citrix Receiver.
On occasion, font embedding fails when fonts with symbols embedded are used with EMF printer drivers.
When you start and then minimize a seamless application, you cannot restore or maximize it from the taskbar.
The session does not reconnect properly over proxy using WPAD. When reconnecting to the disconnected session, the following message appears: "The network connection to your application was interrupted. Try to access your application later or contact your help desk."
Adding a Storefront URL to a region different from the trusted sites' specific configuration for that region does not work.
To use local file type associations, use the following registry key. The following registry key is set to true by default. When the key is set to true, the local file icon changes to the Citrix Receiver icon if there are no other programs associated with that file on the client machine.
After Session Reliability and Automatic Client Reconnection timeout disconnect, session launch is delayed and session sharing does not work.
The size of a mapped client drive might display incorrectly and files cannot be copied to the drive if it exceeds 1TB. With this fix, the drive will display as 0.99TB if it exceeds 1TB. The size of a mapped client drive only get displayed when the Legacy Client Drive Mapping option is enabled.
With Local App Access (LAA) and Desktop Lock enabled, reconnecting to a full screen published server desktop session can cause the session to lose focus and become unresponsive.
Using the "Switch user" Windows logon option changes the session resolution for the virtual desktop.
When using Citrix Receiver, application launch may not work with the ICO SDK.
When a user logs on to StoreFront via Self Service Plug-in, the SelfService.exe process may intermittently take focus from the other active windows every hour.
Epic applications will occasionally lose focus when transitioning networks.
The wfica32.exe process might exit unexpectedly when you attempt to launch an application, and the following error message appears "The connection to <application_name> failed with status (Unknown client error 0)".
The NotificationDelay registry setting controls the delay in the appearance of the connection progress bar for seamless connections. Setting this registry occasionally does not work when using the SelfService Plugin to launch the application. This fix addresses that issue.
On 32-bit Windows:
Data: <Delay, in milliseconds>
On 64-bit Windows:
Data: <Delay, in milliseconds>
When updating XenApp services URLs through GPO and applying a new GPO or updating the same GPO with new store values (such as store1 and store2), Citrix Receiver for Windows might exit unexpectedly.
The wfica32.exe process might experience an access violation and exit unexpectedly.
The SelfService.exe process can consume up to 100% of the CPU.
Sessions with GPU switching enabled on the endpoint can become unresponsive.
This fix provides improved support for sounds that play for a short period of time when using real-time mode for client audio. This fix only applies to low quality audio.
Windows system sounds are occasionally inaudible in XenApp 7.5.
In an unstable network environment, popup messages such as "Your apps are not available at this time. Please try again in a few minutes or contact your help desk with this information: Cannot contact [ServerName]." and "The network connection to your application was interrupted. Try to access your application later or contact your help desk." appear. This fix adds support for the following registry key that lets you disable the pop up messages.
On 32-bit Windows:
On 64-bit Windows:
Shortcuts occasionally do not reappear if you manually delete them and then refresh the applications.
Compared to: Citrix Receiver for Windows 4.3.100
Receiver for Windows 4.4 contains all fixes that were included in Receiver for Windows 4.0, 4.0.1, 4.1, 4.1.2, 4.1.100, 4.1.200, 4.2, 4.2.100, 4.3, and 4.3.100, plus the following, new fixes:
After uninstalling Citrix Receiver, Citrix HDX WMI Provider might not work.
With Session Reliability enabled, the Snap-to feature fails to work in reconnected sessions. The Snap-to feature is a mouse/keyboard setting you configure in Control Panel > Mouse > Pointer Options > Automatically move pointer to the default button in the dialogue box.
Switching between windows by using the Alt+Tab key activates application menus in a published desktop session.
Citrix Receiver and Remote Desktop Protocol (RDP) sessions share the same keyboard shortcut; pressing "Ctrl+Alt+End" to invoke the "Ctrl+Alt+Delete" function inside a terminal session. As a result, the keyboard shortcut for RDP sessions does not take effect inside a Citrix Receiver session.
With this fix, the keyboard shortcut for "Ctrl+Alt+End" is not a default for Citrix Receiver sessions and can be enabled by setting the following registry key:
After upgrading to Version 4.2 of Citrix Receiver, mouse clicks in double hop scenarios can be erratic.
With Local App Access enabled, clicking the mouse to resize a session on a virtual machine can render the virtual machine unresponsive.
Single sign-on might not work when you attempt to log on using a cached fully qualified domain name (FQDN) for credentials.
When Receiver is configured to use pass-through authentication for a Web Interface or StoreFront server in a published desktop session, Receiver might not pass the credentials and instead prompt for credentials.
A windows session running in the foreground might unexpectedly lose focus.
Set the Policy as ProxyEnabled = false under registry hive HKEY_LOCAL_MACHINE\SOFTWARE\<Wow6432Node>\Citrix\AuthManager which will bypass the Proxy server configured on IE. Wow6432Node hive is not applicable if 32 bit OS architecture is used.
In a multi-port or multi-stream configuration where audio and video data is configured on separate ports, the audio can be out of sync with the video.
Users authenticated to Receiver 4.2 for Windows with a smart card might see a PIN authentication prompt when starting XenApp published apps.
The configuration "KEYWORDS:prefer" for a published application might not take effect. This can happen when the user logs off Receiver and the SelfService.exe process closes unexpectedly.
After logging on to Citrix Receiver, the application shortcuts might take a long time to appear on the Start menu and Desktop of the user device.
Attempts to open a Windows media (.wmv) video from an email message in a published instance of Microsoft Outlook might fail.
When the Desktop Viewer switches from full-screen mode to window mode, a floating toolbar might appear in the XenDesktop session while using Receiver.
Desktop sessions might disconnect instead of remaining active when the system that is installed with Desktop Lock with Receiver 4.3 is locked.
To enable the fix, set the following registry key:
If you are subscribed to a streamed-to-client application for Citrix Receiver that does not have the Citrix Offline Plug-in installed, the following error message might appear while refreshing applications within Citrix Receiver:
"Your apps are not available at this time"
When you log on with Citrix Receiver for Windows, multiple pre-launch sessions on different worker servers might appear in the same Delivery Group for the same user.
After undocking the Thomson Reuters Eikon toolbar in a multiple monitor session, the space occupied by the toolbar is not reclaimed by the session.
If a device has a version of Receiver for Windows earlier than 4.3 installed and the user upgrades the operating system to Windows 10 from Windows 7, Windows 8, or Windows 8.1, uninstalling the Receiver through Add or Remove Programs might fail. Attempts to upgrade to Receiver for Windows 4.3 also fail.
The wfica32.exe process might close unexpectedly while attempting to start a new session.
When you open applications from a published desktop through Citrix Receiver and change the "%appdata%" folder to another file server, the following error message might appear:
"Error 1046: Virtual Driver is not loaded"
The alarm window of a locally installed instance of Lotus Notes can take keyboard focus from published applications.
Icons can appear in category folders in both the Start menu and on the desktop. There should not be a category folder for the desktop. The issue occurs when using the registry key "UseCategoryAsStartMenuPath" to control icons in category folders for both the Start menu and the desktop.
To enable the fix, you must set the following registry keys:
Attempts to change a password in Citrix Receiver might fail with the following error message:
"The old password you have entered is incorrect."
While using Microsoft AX Dynamics 2009 or Excel 2007, Citrix Receiver 4.x can exit unexpectedly with the following error message:
"Citrix HDX Engine has stopped working."
When attempting to add icon shortcuts to the desktop in a Citrix Receiver session, certain icons might not display the application-specific icon. Instead, the generic white page icon appears.
Even with the "EnableFTU" set to "false," the CItrix Receiver connection wizard cannot be disabled.
To prevent the connection wizard from appearing, disable the EnableFTU policy setting using Receiver.adm/Receiver.admx:
ComputerConfiguration > Administrative Template > Citrix Component > CitrixReceiver > SelfService > EnableFTU
After installing the URL redirection plugin for Mozilla Firefox browser, a large white box might appear in the lower portion of the browser.
When the seamless registry flag "ENABLE COLOR SYNC" is set, a seamless session might fail to inherit some of the colors from the user device and display black instead.
To enable the fix, set the following registry key:
When changing the StoreFront URL, if the Citrix Receiver Self-service Plug-in user interface is opened and closed, the applications that were set as disabled might appear as ghost icons instead of appearing as dimmed.
Certain applications can intermittently fail to enumerate; a blank icon can appear instead of the icon associated with those applications.
If you change the icon of a published application in Citrix Studio, the desktop shortcut of the application does not update.
When you add an account to Citrix Receiver on a computer that is located behind a proxy, Citrix Receiver does not use the proxy settings when contacting beacons - the location is set to none instead of outside or inside.
Removing the registry value "ConnectionCenter" from the following key, can cause a forced repair for Citrix Receiver: