Windows 10 19H1 (Insider Preview Builds) – Citrix Known Issues

Microsoft releases regular builds of the next version of Windows 10 through their Insider Preview Program. Citrix does not support Insider Preview builds as stated on CTX224843 – Windows 10 Compatibility with Citrix XenDesktop.

This article is intended to capture known issues with Windows 10 19H1 that have been identified so far through Citrix internal testing and customer reports for the benefit of customers who are conducting early testing in preparation for when the Semi-Annual Channel release of 19H1 becomes available.

  • 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.
  • All the issues mentioned in this article have been noticed with 19H1 builds up to 18242.

Known Issues

The following are the known issues:

Issue 1

Issue Description

Print command from inside an ICA session of Windows 10 19H1 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 2

Issue Description

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

[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 19H1.

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
  4. Double click on Logoff
  5. Add a comma separated value ‘UserProfileMan’ right after Profiles and click Ok. It should look similar to below.
  6. Browse to HKEY_LOCAL_MACHINE SYSTEM -> CurrentControlSet -> Control -> Winlogon -> Notifications -> Components
  7. Right click on Components and choose New -> Key
  8. Name it ‘UserProfileMan’ and double click on it.
  9. Once under ‘UserProfileMan’, in the right pane, right click on empty space and choose New -> String Value
  10. Enter String name as Events and value as ‘Logon,Logoff‘ and click Ok.
  11. Right click on empty space and choose New -> String Value
  12. 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 3

Issue Description

Mouse pointer is not visible within a Windows 10 19H1 HDX 3D pro session. All operations inside the session are to be performed by keyboard using shortcuts.

[LCM-4951]

Solution

Citrix is working with Microsoft to resolve this issue.


Issue 4

Issue Description

After HDX 3D Pro VDA is upgraded from Windows 10 to 19H1, 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 19H1, 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 5

Issue Description

Users are unable to uninstall Desktop Lock if Windows 10 was upgraded to 19H1 with Desktop Lock installed.

[TPV-744]

Problem Cause

During the upgrade,the key CtxBackupShell is getting removed under [HKLM -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion -> Winlogon] . As a result, an error message “1: Read failed HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonCtxBackupShell=(32bit on 32bit)” is displayed.

Solution

Citrix is working with Microsoft to resolve this issue. As a workaround, the user may manually add the registry key manually and then uninstall Citrix Desktop Lock 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
  1. Right click on Winlogon in left pane, choose New -> String Value
  2. Enter the value as ‘CtxBackUpShell ’ and hit enter.
  3. Double click on ‘CtxBackUpShell ’ and enter the value as ‘explorer.exe’.
  4. Close Registry Editor and uninstall Desktop Lock.


Issue 6

Issue Description

Citrix Workspace Environment Management (WEM) Agent fails to work when Windows 10 is upgraded to 19H1.

[TPV-1184]

Problem Cause

The ‘Norskale’ key under [HKLM -> System -> CurrentControlSet -> Control] is removed during the upgrade to 19H1.

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 7

Issue Description

Pass-Through Authentication (SSON) fails to work when Windows 10 is upgraded to 19H1 with Workspace App installed.

[TPV-1916]

Problem Cause

While upgrading to 19H1, 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 that were deleted by the installer 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.

  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.

Related:

  • No Related Posts

Leave a Reply