Windows 10 Fall Creators Update (v1709) – Citrix Known Issues

Citrix Virtual Apps and Desktops, formerly XenDesktop, fits the enterprise need to bring both VDI and apps into a user-centric experience.

Citrix Virtual Apps, formerly XenApp, fits the enterprise need to bring legacy apps into a cloud management environment.

Microsoft releases software updates for Windows 10 twice a year through the Semi-Annual Channel. On 17th October 2017, Microsoft released its latest Semi-Annual Channel (Targeted) release for Windows 10 called Fall Creators Update (v1709). As of January 2018, Microsoft has made Fall Creators Update (v1709) available for broad deployment. Information on Windows 10 releases support can be found on CTX224843 “Windows 10 Compatibility with Citrix XenDesktop”. 

This article is intended to capture known issues with Windows 10 v1709 that have been identified so far through Citrix internal testing and customer reports.

• Citrix Virtual Delivery Agent (VDA) for Windows Desktop OS 
• Citrix Receiver for Windows
• Citrix Provisioning Services

Notes:

• This is a live article and is updated as and when new information becomes available.

• Citrix Provisioning Services supports Windows 10 v1709 with known issues for both 7.15 & 7.16.

Known Issues

The following are the known issues: 
 

Issue 1

Issue Description

Citrix VDA for Windows Desktop OS fails to install on Windows 10 v1709 (x64) with error message “Installation of the Citrix Diagnostic Facility failed with error code 1603”
[TPV-605]

Problem Cause

Changes made with Windows 10 v1709 (x64) are preventing the Citrix CDF driver from installing. 

Solution

This issue is fixed with the Windows 10 update (KB4051963) released by Microsoft on 30th November 2017. Before attempting to install the Citrix VDA on Windows 10 v1709, users are advised to apply KB4051963 or its replacement.

The OS Build number should be 16299.98 or higher if the above update is installed. To check OS Build number, run ‘winver’ from command prompt.

This issue is not seen with x86 platform.

Issue 2

Issue Description

When a Windows 10 v1511/1607/1703 system with Citrix VDA for Windows Desktop OS is upgraded to Windows 10 v1709, Windows will roll back to previous state of Windows 10.
[TPV-532]

Problem Cause

While upgrading to Windows 10 v1709, one of the Citrix driver files “CtxMcsWbc” is preventing write operations that causes the update to roll back.

Solution

This issue is fixed with the Windows 10 update released by Microsoft on 14th November 2017. Before attempting to upgrade to Windows 10 v1709, users are advised to update their respective Windows 10 as below:

• If Windows 10 version is v1511, install KB4048952 OR its replacement.
• If Windows 10 version is v1607, install KB4048953 OR its replacement.
• If Windows 10 version is v1703, install KB4048954 OR its replacement.

Issue 3

Issue Description

When 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 4

Issue Description

The mouse cursor could appear smaller within a session when using display with high DPI/Resolution with Windows 10 v1709

[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.3000 or its replacement that avoids the cursor scaling issue.

Issue 5

Issue Description

Mouse cursor is distorted or may disappear at times when 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 Description

Citrix Desktop Lock feature of Citrix Receiver fails to work when Windows 10 is upgraded to v1709

[TPV-744]

Problem Cause

During the Operating System upgrade, under [HKLM -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion -> Winlogon] the value for Shell is getting restored to default value of explorer.exe

Solution

Citrix is working with Microsoft to resolve the issue. As a workaround, user may manually update the registry key by following below steps:

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.
   
   On x86 machine, browse to HKEY_LOCAL_MACHINE  -> Software -> Microsoft -> Windows NT -> CurrentVersion -> Winlogon
   
   On x64 machine, browse to HKEY_LOCAL_MACHINE  -> Software -> WOW6432Node -> Microsoft -> Windows NT -> CurrentVersion -> Winlogon

3. On the right pane, right click on ‘Shell’ and choose ‘Modify’.
   
   On x86 machine, replace the value ‘explorer.exe’ to ‘C:\Program Files\Citrix\ICA Client\SelfServicePlugin\selfservice.exe’ and click Ok.
   
   On x64 machine, replace the value ‘explorer.exe’ to ‘C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\selfservice.exe’ and click Ok. 

4. Right click on Winlogon in left pane, choose New -> String Value

5. Enter the value as ‘CtxBackUpShell ’ and hit enter.

6. Double click on ‘CtxBackUpShell ’ and enter value as ‘explorer.exe’.

7. Close Registry Editor and restart the machine.

Issue 7

Issue Description

An error ‘Failed to get network providers’ appears under Advanced Settings of the Network Adaptor when Citrix Receiver with Single Sign-on (SSON) is installed.
[RFWIN-7435]

Problem Cause

PnSson value is not populated under the newly introduced registry key ‘Provider Order’ under HKEY_LOCAL_MACHINE  -> System -> CurrentControlSet -> Control -> Network Provider -> Provider Order.

Solution

This issue is being fixed in newer versions of Windows 10 (Redstone 4 and newer). This issue does not affect the Single Sign-On (SSON) feature.

To workaround the issue, users could add the missing PnSson value in Registry by following steps below to resolve this issue:

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. In the left pane, browse to HKEY_LOCAL_MACHINE  -> System -> CurrentControlSet -> Control -> Network Provider -> Provider Order
4. In the right pane, right click and choose New -> DWORD (32 bit) value and name it ‘PnSson’.
5. Double click on PnSson. Choose base as Decimal and enter the value as 4000 and click Ok.

This will list all the Network Providers under Advanced Settings of the Network Adaptor

Issue 8

Issue Description
PVS Target Device uninstall hangs on Windows 10 v1709
[LCM-3219]

Solution
This issue is fixed in Microsoft with KB 4093105. Install KB4093105 OR its replacement and then try to uninstall PVS Target Device. 

Issue 9

Issue Description
Windows 10 x86 v1709 cannot boot from vDisk in private mode
[LCM-3224]

Solution
There is no solution.
 

Issue 10

Issue Description

Citrix Workspace Environment Management (WEM) Agent fails to work when Windows 10 is upgraded to Windows 10 v1709.
[TPV-1184]

Problem Cause

The registry key ‘Norskale’ under [HKLM -> System -> CurrentControlSet -> Control] is removed during the upgrade to Windows 10 v1709.

Solution

Citrix is working with Microsoft to resolve this issue. To restore functionality, users could uninstall WEM Agent on the upgraded machine, reinstall and reconfigure.

 

Issue 11

Issue Description

Some maximized applications in Local App Access(LAA) enabled desktop sessions cannot be minimized using the minimize button. (Example application: Notepad, CMD)
[LC8813]

Problem Cause

The issue is due to an incorrect function call getting triggered for LAA enabled desktops.

Solution

This issue is resolved in Citrix XenDesktop 7.18 and CU2 for XenDesktop 7.15.
 

Issue 12

Issue Description

Upgrade from Windows 10 v1607 to v1709 fails if Citrix User Profile Manager (UPM) is installed.
[TPV-1431]

Problem Cause

The upgrade fails with an error message “error during MIGRATE_DATA operation”.

Solution

The Microsoft KB4343887 resolves this issue. Install KB4343887 OR its replacement prior to upgrade of Windows 10 v1709

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.