Fixed issues

Jun 19, 2017

XenApp/XenDesktop 7.6 LTSR Cumulative Update 4 contains all fixes that were included in XenApp and XenDesktop 7.6 LTSR, Cumulative Update 1, Cumulative Update 2, and Cumulative Update 3, plus the following, new fixes:

Citrix Director

  • Attempts to reset the Citrix user profile using Citrix Director might fail, resulting in the following error message:

    “The reset process could not be initiated.”

    The issue occurs when Citrix Director sends only the user name instead of sending the user name along with the domain name. As a result, the Citrix Broker Service fails to locate the user in the DDC domain.

    [#LC6681]

Citrix Studio

  • Microsoft Management Console might become unresponsive when adding machines to the Catalog.

    [#LC5334]

  • Attempts to publish an App-V package that contains certain third-party applications with multiple file type associations might fail, resulting in the following error message:

    “Cannot validate argument on parameter ‘ExtensionName’. The character length of the 28 argument is too long. Shorten the character length of the argument so it is fewer than or equal to “16” characters, and then try the command again.”

    The issue occurs when you attempt to add the App-V package to Citrix Studio.

    [#LC6507]

  • With the access policy “IncludedClientIPFilterEnabled” set to enabled, the following error message might appear when you click “Edit Delivery Group” in Citrix Studio:

    “The Users configuration has been manually modified and cannot be changed by Studio.”

    [#LC6620]

  • When you attempt to add virtual machines to a Citrix Provisioning Services catalog in Citrix Studio, the following error message might appear:

    “The machine “virtual machine name” is already in a Machine Catalog.”

    [#LC6944]

Controller

  • The Configuration Logging Service might consume high memory, causing the Delivery Controller to become unresponsive.

    [#LC6480]

  • Attempts to delete virtual machines that are created by Machine Creation Services can cause Citrix Studio to become unresponsive.

    [#LC6581]

  • With the access policy “IncludedClientIPFilterEnabled” set to enabled, the following error message might appear when you click “Edit Delivery Group” in Citrix Studio:

    “The Users configuration has been manually modified and cannot be changed by Studio.”

    [#LC6620]

  • After successfully removing a machine from the MCS catalog, the following failed task notice appears on the Logging tab of Citrix Studio:
    “Locking pool catalog_name”

    [#LC6653]

  • The Machine Catalogs node in Citrix Studio can take several minutes to display its contents after selecting it.

    [#LC6756]

  • When you attempt to add virtual machines to a Citrix Provisioning Services catalog in Citrix Studio, the following error message might appear:

    “The machine “virtual machine name” is already in a Machine Catalog.”

    [#LC6944]

  • Attempts to add machines to an existing Machine Creation Services catalog might not follow the round robin method for multiple storages that can be selected to accept the new machines.

    [#LC7456]

HDX MediaStream Flash Redirection

  • Flash content might not redirect correctly on the client after configuration of the compatibility list policy.

    [#LC6892]

  • Flash content on Qumu.com does not load and the website becomes dynamically blacklisted, and the following error message appears: “The client’s Flash Player was unable to fetch Flash content directly from the client device. The browser page will be refreshed and server-side Flash rendering will be used if available.”

    [#LC6934]

  • With compatibility view enabled in Microsoft Internet Explorer, certain third-party websites with Flash content might not work.

    [#LC7513]

Provisioning Services

Server

  • Attempts to configure Provisioning Server using the Provisioning Services Configuration wizard by selecting the “Join existing farm” option might fail while using the default instance of SQL server.

    [#LC6579]

Target Device

  • Provisioning Services target devices might experience a fatal exception, displaying a blue screen.

    [#LC6604]

  • Attempts to restart or shut down target devices from the Provisioning Services Console might fail.

    [#LC6814]

  • Provisioning Services target devices might experience a fatal exception, displaying a blue screen with stop code 0x000000f.

    [#LC6990]

  • This fix addresses a memory leak issue in Provisioning Services target devices.

    [#LC7409]

Session Recording

Administration

  • You might receive an Installation failed error in the following two cases. You can ignore the message, but to avoid receiving the message, restart the machine before reinstalling the Session Recording components. [#544579]

    • Uninstalled the Session Recording components, and then reinstalled them without restarting the machine.
    • Installation failed and rollback happened, and then you tried to reinstall the Session Recording components without restarting the machine.

    [#LC6979]

StoreFront

  • 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: Fix #LC5338 works with StoreFront 3.0.4000, StoreFront 3.9 and later versions.

    [#LC5338]

  • Users cannot log on to StoreFront when a cached domain controller is offline, even when another domain controller is available.

    [#LC6358]

  • The icon color for Citrix Receiver for Windows does not change after modifying the StoreFront theme.

    [#LC6435]

  • Users are unable to see apps and desktops after logging on when one XML broker does not work correctly, even when there are many working XML brokers. The following error message appears.
    “There are no apps or desktops available to you at this time.”

    [#LC6928]

  • Attempts to propagate changes to a server group by selecting “Propagate Changes” on the StoreFront console might fail and the following error message appears:
    “Propagation failed on one or more servers.”

    [#LC7428]

  • This fix addresses an issue with Firefox. For more information, see Knowledge Center article CTX221551.

    [#LC7473]

Universal Print Server

Client

  • The print spooler service might become unresponsive and, as a result, Universal Printing does not work. The issue occurs when a timeout is reached while waiting for a transaction response from the spooler service.

    [#LC5209]

VDA for Desktop OS

HDX 3D Pro

  • When using the HDX 3D Pro agent on the VDA, two rows of pixels might be missing when starting a new desktop session.

    [#LC6409]

Printing

  • Printer redirection might fail intermittently.

    [#LC5320]

Security Issues

  • This fix updates an internal VDA component.

    [#LC6904]

Session/Connection

  • When you log on to a VDA where a user profile does not exist, a black screen might appear after the Windows Welcome screen is displayed for a period of time before the logon completes.

    [#LC2397]

  • When you attempt to send video in a Cisco WebEx meeting by using a webcam through Citrix Receiver for Mac, the Cisco WebEx meeting might exit unexpectedly.

    [#LC5518]

  • When reading a file from a mapped client drive, the old, cached file length might be returned if the file length was changed outside of the client session. Additionally, null characters are inserted for any deleted characters.

    To enable the fix, set the following registry value to “0”:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters Name: CacheTimeout Type: REG_DWORD Value: Default value is 60 seconds. If CacheTimeOut is set to “0,” the file length is reloaded immediately and if not it is loaded after the defined timeout.

    [#LC6314]

  • With local app access enabled, using the interactive logon disclaimer policy might result in a black or gray screen lasting for 45 seconds.

    [#LC6518]

  • The server idle timer does not reset for iOS devices with the multi-touch feature enabled.

    [#LC6743]

  • End User Experience Monitoring stops collecting metrics when the number of virtual channels exceeds 32.

    Note: With this fix, the limit that is set for virtual channels is removed.

    [#LC6768]

  • With “Application Lingering” configured for the Delivery Group, published applications occasionally fail to appear when you reconnect to a session.

    [#LC7405]

  • The window positions might not be retained when you reconnect to a published desktop session and are using multiple monitors.

    [#LC7644]

Smart Cards

  • Occasionally, removing a smart card reader might not trigger the user session to get locked, even though smart card removal is configured to lock the user session.

    [#LC7411]

System Exceptions

  • VDAs might experience a fatal exception, displaying a blue screen, on tdica.sys with bugcheck code 0x7E.

    [#LC6553]

  • VDAs might experience a fatal exception, displaying a blue screen, on vd3dk.sys with bugcheck code 0X00000050.

    [#LC6833]

  • VDAs can experience a fatal exception on wdica.sys, displaying a blue screen.

    [#LC6883]

  • VDAs might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x7F while shutting down a session.

    [#LC7545]

  • The Service Host (svchost.exe) process might experience an access violation and exit unexpectedly. The issue occurs because of the faulting module, scardhook64.dll.

    [#LC7580]

User Experience

  • This fix provides improved support for sounds that play for a short period of time when using high quality audio.

    Note:

    • This fix does not take effect in sessions running on Windows Server 2008 R2.
    • For this fix to work, you must use Citrix Receiver 4.4 for Windows Long Term Service Release (LTSR) CU5 or later versions and the VDA version of XenApp and XenDesktop 7.6 LTSR CU4 or later.

    [#LC5842]

  • The USB device instance path might have additional characters at the end of the path name when the device is redirected on Version 7.6.300 of the VDA. To change this behavior, add the Product ID (PID) or Vendor ID (VID) to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\icausbb\Parameters Name: DeviceInstanceIDOption Type: REG_DWORD Value: 0 (default value), 1, 2.

    • If “DeviceInstanceIDOption” is configured to “0” (0 being the default value), devices whose VID/PID pairs are configured to “UsingSerialNumberDevices” use the serial number as the instance ID. Other devices use “serial_number+Bus_number+port_number” as the instance ID.
    • If “DeviceInstanceIDOption” is configured to “1,” devices whose VID/PID pairs are configured to “UsingSerialNumberDevices” use “serial_number+Bus_number+port_number” as the instance ID. Other devices use the serial number as the instance ID.
    • If “DeviceInstanceIDOption” is configured to “2,” all devices use the serial number as the instance ID.
    • All other values are invalid and treated as “0.”

    [#LC6212]

  • Sessions might become unresponsive when playing videos in a web browser.

    [#LC6259]

  • In a multi-monitor environment, define the external monitor as the “Main Display” of Windows and position it to the right of the secondary laptop or tablet monitor in the display settings of the Control Panel. When you start a published application that appears on the external monitor and move this application to the tablet monitor or a laptop that is attached to the external monitor, opening or closing the lid of the tablet or a laptop can cause the published application to become black.

    To enable the fix, you must set the following registry key value on the VDA:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\Thinwire Name: EnableDrvTw2NotifyMonitorOrigin Type: REG_DWORD Value: 1 (to enable) and 0 (to disable; 0 is the default value). By default, the registry value is missing.

    [#LC7760]

User Interface

  • When using the Connection Center to log off from a seamless session with unsaved data, a black window appears with the following message:

    “Programs still need to close” - with the two options - “Force Logoff” or “Cancel.” The “Cancel” option does not work.

    After installing this fix, the Cancel option works as designed.

    [#LC6075]

  • URL shortcut icons might be displayed as blank when using a touch-optimized desktop.

    [#LC6663]

Miscellaneous

  • Attempts to reconnect to a disconnected desktop session might fail.

    [#LC6677]

  • The SHAppBarMessage API with the “ABM_GETSTATE” message might not return the correct value when executed in a seamless session.

    [#LC7579]

VDA for Server OS

Printing

  • Printer redirection might fail intermittently.

    [#LC5320]

Session/Connection

  • When you log on to a VDA where a user profile does not exist, a black screen might appear after the Windows Welcome screen is displayed for a period of time before the logon completes.

    [#LC2397]

  • When you attempt to send video in a Cisco WebEx meeting by using a webcam through Citrix Receiver for Mac, the Cisco WebEx meeting might exit unexpectedly.

    [#LC5518]

  • The VDA for Server OS might become unresponsive at the “Welcome” screen for about two minutes during the logon process. The issue occurs when you configure the last interactive logon information through Active Directory Group Policy Object (GPO).

    [#LC5709]

  • An additional published application window might open when reconnecting to a session.

    [#LC5786]

  • The VDA for Server OS can become unresponsive. As a result, user sessions might fail to log off.

    [#LC6117]

  • When reading a file from a mapped client drive, the old, cached file length might be returned if the file length was changed outside of the client session. Additionally, null characters are inserted for any deleted characters.

    To enable the fix, set the following registry value to “0”:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters Name: CacheTimeout Type: REG_DWORD Value: Default value is 60 seconds. If CacheTimeOut is set to “0,” the file length is reloaded immediately and if not it is loaded after the defined timeout.

    [#LC6314]

  • Microsoft Internet Explorer 11 might not use the virtual IP loopback address assigned to that session.

    [#LC6622]

  • The server idle timer does not reset for iOS devices with the multi-touch feature enabled.

    [#LC6743]

  • End User Experience Monitoring stops collecting metrics when the number of virtual channels exceeds 32.

    Note: With this fix, the limit that is set for virtual channels is removed.

    [#LC6768]

  • Active sessions might be disconnected on the XenApp servers when the Delivery Controller loses connectivity. The issue occurs when VDAs fails to track the status of sessions that move from “pre-launch” to “active” status correctly. As a result, when the Delivery Controller is restarted, it attempts to clear the resources from the VDAs, and sessions in the pre-launch status are disconnected or logged off while the applications are being actively used.

    [#LC6819]

  • When you launch a session in windowed mode in a published desktop and span the desktop through six monitors or more, the taskbar or the screen might become gray.

    [#LC6862]

  • After setting Google Chrome as the default browser, Microsoft Internet Explorer might continue to be the default browser when you click URLs within applications.

    [#LC6948]

  • With the Electrolysis (e10s) feature enabled, the 64-bit version of Mozilla Firefox might exit unexpectedly. For more information, see Knowledge Center article CTX224067.

    [#LC6982]

  • With “Application Lingering” configured for the Delivery Group, published applications occasionally fail to appear when you reconnect to a session.

    [#LC7405]

System Exceptions

  • Certain third-party applications might fail to start in an RDP session.

    [#LC4141]

  • The service host process (Svchost.exe) that hosts Terminal Services might exit unexpectedly. The issue occurs because of the faulting module, RPM.dll.

    [#LC6277]

  • VDAs might experience a fatal exception, displaying a blue screen, on tdica.sys with bugcheck code 0x7E.

    [#LC6553]

  • VDAs can experience a fatal exception on wdica.sys, displaying a blue screen.

    [#LC6883]

  • VDAs might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x7F while shutting down a session.

    [#LC7545]

  • The Service Host (svchost.exe) process might experience an access violation and exit unexpectedly. The issue occurs because of the faulting module, scardhook64.dll.

    [#LC7580]

User Experience

  • This fix provides improved support for sounds that play for a short period of time when using high quality audio.

    Note:

    • This fix does not take effect in sessions running on Windows Server 2008 R2.
    • For this fix to work, you must use Citrix Receiver 4.4 for Windows Long Term Service Release (LTSR) CU5 or later versions and the VDA version of XenApp and XenDesktop 7.6 LTSR CU4 or later.

    [#LC5842]

  • The USB device instance path might have additional characters at the end of the path name when the device is redirected on Version 7.6.300 of the VDA. To change this behavior, add the Product ID (PID) or Vendor ID (VID) to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\icausbb\Parameters Name: DeviceInstanceIDOption Type: REG_DWORD Value: 0 (default value), 1, 2.

    • If “DeviceInstanceIDOption” is configured to “0” (0 being the default value), devices whose VID/PID pairs are configured to “UsingSerialNumberDevices” use the serial number as the instance ID. Other devices use “serial_number+Bus_number+port_number” as the instance ID.
    • If “DeviceInstanceIDOption” is configured to “1,” devices whose VID/PID pairs are configured to “UsingSerialNumberDevices” use “serial_number+Bus_number+port_number” as the instance ID. Other devices use the serial number as the instance ID.
    • If “DeviceInstanceIDOption” is configured to “2,” all devices use the serial number as the instance ID.
    • All other values are invalid and treated as “0.”

    [#LC6212]

  • Sessions might become unresponsive when playing videos in a web browser.

    [#LC6259]

  • In a multi-monitor environment, define the external monitor as the “Main Display” of Windows and position it to the right of the secondary laptop or tablet monitor in the display settings of the Control Panel. When you start a published application that appears on the external monitor and move this application to the tablet monitor or a laptop that is attached to the external monitor, opening or closing the lid of the tablet or a laptop can cause the published application to become black.

    To enable the fix, you must set the following registry key value on the VDA:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\Thinwire Name: EnableDrvTw2NotifyMonitorOrigin Type: REG_DWORD Value: 1 (to enable) and 0 (to disable; 0 is the default value). By default, the registry value is missing.

    [#LC7760]

User Interface

  • When using the Connection Center to log off from a seamless session with unsaved data, a black window appears with the following message:

    “Programs still need to close” - with the two options - “Force Logoff” or “Cancel.” The “Cancel” option does not work.

    After installing this fix, the Cancel option works as designed.

    [#LC6075]

  • URL shortcut icons might be displayed as blank when using a touch-optimized desktop.

    [#LC6663]

Miscellaneous

  • The SHAppBarMessage API with the “ABM_GETSTATE” message might not return the correct value when executed in a seamless session.

    [#LC7579]