Microsoft releases software updates for Windows 10 twice a year through the Semi-Annual Channel. Microsoft released its Semi-Annual Channel ‘May 2020 update’ (v2004) in May 2020, ‘October 2020 update’ (20H2) in October 2020, ‘May 2021 update’ (21H1) in May 2021 and ‘November 2021 update’ (21H2).
This article is intended to capture known issues with Windows 10 v2004, 20H2, 21H1 and 21H2 that have been identified so far through Citrix internal testing and customer reports.
Note:
- This is a live article and is updated as and when new information is available.
- Unless explicitly specified, issues seen with Windows 10 v2004 are seen with 20H2, 21H1 & 21H2 also.
Known Issues
The following are the known issues:
Issue 1
Issue Description
Citrix User Profile Manager (UPM) may stop working after Windows 10 with VDA installed is upgraded to v2004 OR it may break the native Windows applications like notepad, calculator etc when UPM is configured on fresh install of v2004.
[TPV-2706]
Changes in Windows 10 v2004 is causing this issue.
Solution
This issue is fixed in Citrix Virtual Apps and Desktops 7 2003 and later versions.
Issue 2
Issue Description
Printers part of Citrix Universal Print Server (UPS) are not mapped within ICA session of Windows 10 v2004 VDA.
Problem Cause
Changes in Windows 10 v2004 Operating System is causing the printer mapping failure.
Solution
This issue is resolved with the Microsoft Defender Advanced Threat Protection signature updates released around June 2020.
Issue 3
Issue Description
On Virtual Machine’s (hosted on vSphere) with VM version 14 and boot option EFI, a failure may be seen when you upgrade Windows 10 machine to v2004 with an error “We can’t tell if your PC is ready to continue installing Windows 10. Try restating the setup”
[TPV-2703]
Installing the latest VMWare tools 11.0.0.x before attempting to upgrade to v2004 resolves this issue.
Issue 4
Issue Description
On Windows 10 v2004 end point with Receiver/Workspace App, when a network interruption is caused by disabling the Network Interface from Control Panel, Session Reliability feature fails to work.
[RFWIN-15116]
Problem Cause
Changes in Windows 10 v2004 Operating System is making the Session Reliability to fall back to Auto Client Reconnect when the network is disrupted.
Solution
This issue has been fixed in Citrix Workspace App.
- Users on Current Release of Workspace App are advised to upgrade to version 2002 or its replacement that contains the fix.
- Users on the LTSR version of Workspace App are advised to upgrade to version 1912 or its replacement that contains the fix.
Issue 5
Issue Description
On Windows 10 v2004 end point with Receiver/Workspace App, when a network interruption is caused using Firewall, Session Reliability feature fails to work.
[RFWIN-15263]
Problem Cause
Changes in Windows 10 v2004 Operating System is making the Session Reliability to fall back to Auto Client Reconnect as soon as the the network is disrupted.
Solution
This issue has been fixed with KB4571744. Install this KB OR its replacement on end-points to resolve this issue.
Issue 6
Issue Description
ICA launch of Citrix VDA installed on Windows 10 Virtual Desktop v2004 fails OR ICA session disconnects within 2 minutes with error message “Idle Timer Expired “ or “Logon timer Expired”.
[TPV-3025]
Problem Cause
Changes in Windows 10 v2004 Operating System is causing this issue.
Solution
For Citrix VDA version 2006 and above:
Issue is resolved in KB4586853, Install this KB OR its replacement on your VDAs to resolve this issue.
For Citrix VDA versions before 2006:
ICA launch still fails and Citrix is working on fixing it. Please use the below workaround.
Workaround
The WDDM graphics display driver for Remote Desktop Connection which is enabled by default in Windows 10 v2004 and above needs to be disabled as it is not supported by the Citrix VDA. To disable, set the below policies through the group policies for your OU:
- Browse to Administrative Templates (Computers) -> Windows Components – > Remote Desktop Service -> Remote Desktop Session Host.
- Disable the setting “Use WDDM graphics display driver for Remote Desktop Connection”
Issue Description
A failure during component initialization may be seen when 7.15 LTSR VDA (with any CU) is upgraded to CU6 on Windows 10 v2004. This issue is not seen with a fresh install of CU6 VDA on Windows 10 v2004.
[LCM-7909]
Problem Cause
An error “Failed to configure component ‘ICA for workstation services’ because it is not installed” is seen. Changes in Windows 10 v2004 is causing this issue.
Solution
Citrix is working with Microsoft to resolve this issue.
Workaround
- Uninstalling the existing CU and installing CU6 resolves this issue.
- Upgrading 7.15 LTSR VDA to CU6 prior to upgrading VDA OS to Windows 10 v2004 is advised.
Issue 8
Issue Description
Following upgrade to Windows 10 v2004, user personalization layer (UPL) services will no longer be able to start during logon. This prevents user layer disks from attaching or being created when users log into their desktops. Note, this issue does not impact App Layering User Layers, it only affects user personalization layer for Virtual Apps and Desktops
[UNI-78456]
Problem Cause
During upgrade to Windows 10 v2004 Microsoft is removing the UPL service key and service from the Winlogon chain.
Solution
This issue is fixed in Citrix Virtual Apps and Desktops 2009 or newer. This issue has also been fixed with the latest updates of 20H1/20H2.
Issue 9
Issue Description
App Layering fails to import a new OS Layer for Windows 10 v2004 with the error: “A failure occurred while importing the OS: Cannot handle more than two partitions on a disk.”
[UNI-79067]
Problem Cause
Importing Windows 10 v2004 as a new OS Layer fails due to Windows creating a recovery partition during installation which results in their being a total of three partitions for the image. This is greater than the maximum two partitions allowed for OS Import.
Solution
This issue is fixed in Application Layering 2009 or newer. Citrix recommends to upgrade the Enterprise Layer Manager (ELM) and do the import again.
Issue 10
Issue Description
Published images from App Layering running Windows 10 v2004 can take 5 minutes or longer to log into Windows and/or for the Start Menu to appear after login.
[UNI-79147]
Problem Cause
The issue is caused by missing dependencies between the App Layering uniservice, and the Windows Delivery Optimization Service (dosvc) and Storage Service (StorSvc).
Solution
This issue is fixed in Application Layering 2011 or newer. Citrix recommends to upgrade the Enterprise Layer Manager (ELM) and redeploy any images.
Issue 11
Issue Description
Audio redirection may fail after a reconnect of ICA session on Windows 10 Multi-session editions with Citrix VDA.
[CVADHELP-15804]
Problem Cause
Changes made in Windows 10 v2004 is causing this issue.
Solution
There is no solution. Citrix is working on a fix to resolve this issue.
Issue 12
Issue Description
Upgrade to Windows 10 20H2 OR 21H2 may fail on machines that are configured to have domain administrator profiles managed by UPM
[UPM-3083]
Problem Cause
Changes made in Windows 10 v2004/21H2 is causing this issue.
Solution
There is no solution. Citrix is working with Microsoft to resolve this issue.
Workaround
Ensure the domain administrator profiles are not managed by UPM before upgrading to Windows 10 20H2 Or 21H2.
Issue 13
Issue Description
Unable to launch publish desktop. Desktop Viewer disappears after it opens.
[CVADHELP-15537]
Problem Cause
Changes made in Windows 10 v2004 is causing this issue.
Workaround
Downgrade OS to Windows 10 v1909.
Issue 14
Issue Description
Following an upgrade to Windows 10 21H1, images running user personalization layer (UPL) will exhibit Start Menu issues, and users will be prompted to reboot the image to fix this issue. Rebooting the image will not fix it.
[UNI-83300]
Problem Cause
During upgrade to Windows 10 21H1 Microsoft is removing a Uniservice depedency for login services.
Solution
There is no solution. Citrix is working on a fix for this issue.
Workaround
When authoring the master image which was upgraded to Windows 10 21H1, the VDA can be uninstalled and reinstalled (including UPL) to resolve the issue.