Windows 10 October 2018 Update (v1809) – Citrix Known Issues

Microsoft releases software updates for Windows 10 twice a year through the Semi-Annual Channel. On 2nd October 2018, Microsoft released its latest Semi-Annual Channel release for Windows 10 called ‘October 2018 Update’ (v1809).

This article is intended to capture known issues with Windows 10 v1809 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 (PVS)
  • Citrix Workspace Environment Management (WEM)
  • Citrix User Profile Management (UPM)

Note:

  • This is a live article and is updated as and when new information is available.
  • This article was a known issues article for Insider Preview Builds of v1809 (Redstone 5) up to 4th October 2018.


Known Issues

The following are the known issues:

Issue 1

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.3000 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 4

Issue Description

Print command from inside an ICA session of Windows 10 v1809 client fails to print using mapped Citrix UPS configured XPS Printer.

[HDX-13664]

Problem Cause

XPS Viewer is not available on Windows 10 v1803 and later versions by default. It is available as a Feature on Demand.

Solution

To install XPS Viewer, follow the below steps:

  • Open Command Prompt in elevated mode
  • Run the command “Dism /online /add-capability /CapabilityName:XPS.Viewer~~~~0.0.1.0”

Note:

  • The machine should be connected to the Internet for above command to acquire and install XPS Viewer.


Issue 5

Issue Description

Upgrade from Windows 10 v1803 to v1809 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 KB4343909 resolves this issue. Install KB4343909 OR its replacement prior to upgrade of Windows 10 v1809.

Issue 6

Issue Description

Citrix User Profile Manager (UPM) stops working after Windows 10 is upgraded to v1809.

[TPV-1307]

Problem Cause

The upgrade process is removing some of the registry entries related to UPM.

Solution

Citrix is working with Microsoft to resolve this issue.

Workaround 1:

As a workaround, users are advised to reinstall UPM after upgrading to v1809.

Workaround 2:

Add the registry keys manually that were removed during upgrade.

Caution!

  • Refer to the Disclaimer at the end of this article before making changes to Registry.
  • Below steps need to be performed by an administrator as it involves changing of permissions of Trusted Installer key of registry.

Part A – Setting permissions to Administrator group.

  1. Login to the VDA as domain administrator
  2. Right click on Start button and choose Run
  3. Type ‘Regedit’ and click Ok.
  4. Browse to HKEY_LOCAL_MACHINE -> System -> CurrentControlSet -> Control -> Winlogon -> Notifications
  5. Right click on Notifications and choose ‘Permissions…
  6. Click on Advanced and switch over to the Owners panel by clicking on the link Change next to ‘Owner:’.
  7. Enter Administrator under ‘Enter the Object name to select’ and click Ok.
  8. On the Advanced Security Settings window, check the box for ‘Replace owner on subcontainers and objects’.
  9. On the Permissions for Notifications window, grant Full permission to Administrators group.
Part B – Add the missing registry keys
  1. Browse to HKEY_LOCAL_MACHINE SYSTEM -> CurrentControlSet -> Control -> Winlogon -> Notifications -> Configurations -> Default -> Logon
  2. On the right pane, double click on Logon
  3. Add a comma separated value ‘UserProfileMan’ right after SessionEnv and click Ok. It should look similar to below:
User-added image
  1. Double click on Logoff
  2. Add a comma separated value ‘UserProfileMan’ right after Profiles and click Ok. It should look similar to below.
  3. Browse to HKEY_LOCAL_MACHINE SYSTEM -> CurrentControlSet -> Control -> Winlogon -> Notifications -> Components
  4. Right click on Components and choose New -> Key
  5. Name it ‘UserProfileMan’ and double click on it.
  6. Once under ‘UserProfileMan’, in the right pane, right click on empty space and choose New -> String Value
  7. Enter String name as Events and value as ‘Logon,Logoff‘ and click Ok.
  8. Right click on empty space and choose New -> String Value
  9. Enter String name as ServiceName and value as ctxProfile and click Ok.

Part C – Restore permissions to TrustedInstaller

  1. Browse to HKEY_LOCAL_MACHINE -> System -> CurrentControlSet -> Control -> Winlogon -> Notifications
  2. Right click on Notifications and choose ‘Permissions…
  3. Click on Advanced and switch over to the Owners panel by clicking on the link Change next to ‘Owner:’.
  4. Select Object Types and check all the boxes and click Ok.
  5. Select ‘Locations…’, then select Local Computer.
  6. Enter ‘NT ServiceTrustedInstaller’ under ‘Enter the Object name to select’ and click Ok.
  7. On the Permissions for Notifications window, uncheck Full permission to Administrators group.

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

Citrix is working with Microsoft to resolve this issue. As a work around, users could enable mouse pointer trails by following below steps:
  1. Click Start and type ‘mouse settings’.
  2. Click on ‘Additional mouse options’.
  3. Click on ‘Pointer Options’ tab.
  4. Select the checkbox ‘Display pointer trails’.
  5. Click Apply and Ok.


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 FilesCitrixICAServiceNvFBCEnable.exe -enable

  • Make sure FBC is enabled by running

C:Program FilesCitrixICAServiceNvFBCEnable.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

Citrix is working with Microsoft to resolve this issue. As a work around, 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:

    User-added image

  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)CitrixICA Clientx64pnsson.dll on 64 bit Machine

      C:Program FilesCitrixICA Clientpnsson.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:CitrixICA 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:

    User-added image

  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:

    User-added image

  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:

    User-added image

  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.

Related:

  • No Related Posts

Leave a Reply