Issue Description
When a user tries to launch a published desktop in full-screen mode using Smart card authentication through a NetScaler environment, the PIN prompt is not visible and just the progress indicator is seen. The connection times out and the launching desktop process closes.
[LC8579]

Problem Cause
Full-screen sessions hide the PIN prompt window. The Windows Security and UAC prompt are updated from Winform to XAML. This causes the PIN prompt window to lose focus and stay in the background.

Solution
This is a known issue with Citrix Receiver (https://docs.citrix.com/en-us/receiver/windows/current-release/about/known-issues.html).

• Users on Current Release of Citrix Receiver are advised to upgrade to Citrix Receiver 4.12 or its replacement that contains the fix.
• Users on the LTSR version(version 4.9) of Receiver are advised to upgrade to Citrix Receiver 4.9.3000 or its replacement that contains the fix.

• Issue 2

  Issue Description
  The mouse cursor could appear smaller within a session when using display with high DPI/Resolution
  [HDX-9959]

  Problem Cause
  Monochrome custom cursors created via CreateCursor() in a non-DPI aware application do not scale correctly with Windows 10 v1703 and later versions. Custom cursors created via CreateInconIndirect() in a non-DPI aware application do not scale correctly in all versions of Windows 10.

  Solution

  • Users on Current Release of Citrix Receiver (version 4.8) are advised to upgrade to Citrix Receiver 4.11 or its replacement that avoids the cursor scaling issue.
  • Users on the LTSR version(version 4.9) of Receiver are advised to upgrade to Citrix Receiver 4.9.5000  or its replacement that avoids the cursor scaling issue.

Issue 3

Issue Description

The mouse cursor is distorted or may disappear at times when a published application or VDA is launched in full screen on multi-monitor setup with high DPI/Resolution.
[RFWIN-7040]

Problem Cause
Monochrome custom cursors created via CreateCursor() can be distorted on multi-monitor setups with mixed DPI in Windows 10.

Solution

• Users on Current Release of Citrix Receiver (version 4.8) are advised to upgrade to Citrix Receiver 4.11 or its replacement that avoids the cursor scaling issue.
• Users on the LTSR version(version 4.9) of Receiver are advised to upgrade to Citrix Receiver 4.9.3000 or its replacement that avoids the cursor scaling issue.

Issue 6

Issue 7

Issue Description

Mouse pointer is not visible within a v1809 HDX 3D pro session. All operations inside the session are to be performed by keyboard using shortcuts.  This issue is seen with Citrix XenApp/XenDesktop 7.15 only. This issue is not seen with later versions of XenApp/XenDesktop.
[LCM-4951]

Problem Cause

A change in mouse functionality API’s is causing this issue.

Solution

Issue 8

Issue Description

After HDX 3D Pro VDA is upgraded from Windows 10 v1803 to v1809, the policy “Use hardware encoding for video codec” is not in effect and Hardware Encoding is disabled. The Registry information related to BitMap Provider is also not as expected post upgrade.
[LCM-4955, LCM-4956]

Solution
Citrix is working with Microsoft to resolve this issue.

Workaround:

• After upgrading to v1809, restart the VDA and run below commands:

C:\Program Files\Citrix\ICAService\NvFBCEnable.exe -enable 

• Make sure FBC is enabled by running

C:\Program Files\Citrix\ICAService\NvFBCEnable.exe -checkstatus 

Note – If status is still shown as disabled, then Nvidia driver may need to be reinstalled. After reinstalling the driver, try to enable FBC again.

Issue 9

Issue Description

Pass-Through Authentication (SSON) fails to work when Windows 10 is upgraded to v1809 with Workspace App installed.
[TPV-1916]

Problem Cause

While upgrading to v1809, few registry entries required by SSON gets removed under HKLM > System > CurrentControlSet > Control > NetworkProvider.

Solution

This issue is no longer seen if KB4490481 is present on target OS (v1809).  If using ISO, while upgrading to v1809, check the option of obtaining updates during upgrade. This will include KB4490481 during upgrade.

If the fix is not accessible, users may manually add the registry keys (Workaround 1) OR run a Power Shell script (Workaround 2) that adds the registry entries that were deleted by the installer.

Workaround 1:

Caution! Refer to the Disclaimer at the end of this article before making changes to Registry

1. Right click on Start button and choose Run
2. Type regedit and click OK.
3. Browse to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services.
4. Right-click on Services and choose New > Key.
5. Enter value PnSson for the new key and click OK.
6. Right-click the key PnSson for and choose New > DWORD 32 bit, enter IsEnabled and set Value data 1
7. Right-click the key PnSson for and choose New > DWORD 32 bit, enter Type and set Value data 4
8. After adding the keys and values, it should appear like below:

   

9. Right-click the key PnSson and choose New > Key.
10. Enter value NetworkProvider and click OK.
11. Add the following entries under the newly created key:
    • Right-click NetworkProvider > New > String Value, enter Name and set Value data Citrix Single Sign-on.
    • Right-click NetworkProvider > New > String Value, enter ProviderPath and set Value data to below value:

      C:\Program Files (x86)\Citrix\ICA Client\x64\pnsson.dll on 64 bit Machine

      C:\Program Files\Citrix\ICA Client\pnsson.dll on 32 bit Machine

      Note: If Workspace App is installed in Custom location, the above values should be changed accordingly to $InstallPath$\ICA Client\… Example: If install path is c:\Citrix then the value should be C:\Citrix\ICA Client\….

    • Right-click NetworkProvider > New > DWORD 32 bit, enter Class and set Value data 2.
12. After adding the keys and values, it should appear like below:

    

13. Browse to HKEY_LOCAL_MACHINE> SYSTEM> CurrentControlSet> Control> NetworkProvider> Order
14. Right Click on ProviderOrder and Select Modify.
15. Add ,Pnsson to the end of the current value in the registry.
16. After adding the keys and values, it should appear like below:

    

17. Browse to HKEY_LOCAL_MACHINE> SYSTEM> CurrentControlSet> Control> NetworkProvider> HwOrder
18. Right Click on ProviderOrder and Select Modify.
19. Add ,Pnsson to the end of the current value in the registry.
20. After adding the keys and values, it should appear like below:

    

21. Restart the machine.

Workaround 2:
Users could run the Power Shell script that adds the above entries. Download the attachment.zip file, extract it to a folder and run Receiver_SSON.PS1. This script will add the registry entries based on the Receiver install location. It also retains services registered with Microsoft Network Provider and appends PnSson value. Users are advised to test the script before using it in a production environment.

Issue 10

Issue Description

WEM cannot pin apps to taskbar in Windows 10 v1809
[WEM-3257]

Problem Cause

After pinning apps to taskbar and refreshing the agent, the apps are still not shown on the VDA.

Solution

Issue 11

Issue Description

Printers part of Universal Print Server are no longer mapped after Windows 10 is upgraded to Windows 10 v1809. This issue is not seen with fresh install of Windows 10 v1809.
[LCM-5677]

Solution