Known issues
Notes
-
Known issues that are described in the 2203 initial release, CU1, CU2, CU3, and CU4 sections of this article continue to be present in CU5 unless they are included in the list of fixed issues.
-
If a known issue has a workaround, it is provided after the description of the issue.
-
The following warning applies to any workaround that suggests changing a registry entry:
Warning:
Editing the registry 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.
Known issues in 2203 CU7
Known issue in 2203 CU6
Known issue in 2203 CU5
-
When you already have Citrix Workspace app version 22.03.5000 installed (which is available in Citrix Virtual Apps and Desktops 2203 CU4 VDA and CU4 Update 1) and attempt to upgrade to the latest version, the upgrade might fail due to an auto update pop-up. Use the following workarounds before updating the VDA to CU5:
-
Upgrade to Citrix Workspace app version 2203.1 LTSR CU6 or Citrix Workspace app 2402 LTSR.
-
Disable the auto-update. For more information, see Configure Citrix Workspace Updates using the Group Policy Object administrative template.
-
Known issues in 2203 CU4
-
If you install Windows, IIS and Citrix Director in drives other than C:\ and upgrade Citrix Director to release 2203 LTSR CU4, the Citrix Director icon might appear blank. However, you can click the icon to launch the Citrix Director.You can use the following workaround to help display the icon correctly.
-
Open the command prompt and run the command echo %systemdrive%.
-
Copy the output of the command.
-
Right-click on Citrix Director icon > More > Open file location.
-
Open Notepad and drag the icon from file explorer to Notepad.
-
In the contents, replace “C:” with the output copied in step 2 and save.
-
The Citrix Director icon will now be displayed correctly.
-
Attempt to start resources or app enumeration might fail when you upgrade StoreFront™ to version 2203 LTSR CU4.Note:The issue is fixed in 2203 LTSR CU4 Update 1.
-
VDAs might experience a fatal exception on picadd.sys and display a blue screen with bug check code 0x96.Note:The issue is fixed in 2203 LTSR CU4 Update 1.
Known issues in 2203 CU3
Known issues in 2203 CU2
-
Attempts to upgrade Session Recording from Citrix Virtual Apps and Desktops™ 2203 LTSR CU1 to CU2 might fail. This error message appears:Unable to complete the installation.The installation did not complete because a problem occurred during initialization. The product will operate but performance could be diminished.
Known issues in 2203 CU1
Known issues in 2203 initial release
General
-
When you start an application from StoreFront, the application might not start in the foreground, or the application is in the foreground but might not have focus. As a workaround, click the icon in the task bar to bring the application to the front or in the application screen to bring it to focus.
-
When applications from Microsoft Office 365 build 16.0.7967 and later are published as applications from a Windows Server 2019 host, Office license activation fails. Citrix is working with Microsoft to address this Microsoft limitation. The supported workaround is to install Windows Server 2016 VDAs, which do not have Web Authentication Manager component that is misbehaving.
-
Session Manager terminates session launches when the Group Policy evaluation fails. This is to prevent user access to resources that are restricted through Group Policy. The following user-implemented fix provides a registry toggle for administrators to dismiss the enforcement, which helps end users to connect to sessions even if the Group Policy evaluation fails:HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\GroupPolicyName: EnforceUserPolicyEvaluationSuccessType: REG_DWORDValue: 0 (enables the current fix)
-
Terminal Service running on a multi-session OS VDA might exit intermittently. The Event ID 7011 is logged in the System Event log with the following message:A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TermService service.
-
Your High Definition Experience (HDX) Audio devices disable when you are connecting to a single-session RemotePC or Workstation Virtual Delivery Agent (VDA) on a client that is enabling more than eight HDX Audio devices. As a workaround, choose one of the following:
-
Connect to a single-session RemotePC or Workstation VDA from a client that is enabling less than eight HDX Audio devices.
-
Enable the HDX Audio devices after the single-session RemotePC or Workstation VDA has launched.
-
Connect to a multi-session RemotePC or Workstation VDA.
-
Graphics
-
Some applications are limited to a maximum frame rate of 22 frames per second (FPS) instead of the default maximum of 30 FPS. A fix will be available in 2203 LTSR CU2. As a workaround, set the following registry value on the VDA:
-
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Graphics
-
Printing
-
Universal Print Server printers selected on the virtual desktop do not appear in the Devices and Printers window in the control panel. However, when users are working in applications, they can use those printers. This issue occurs only on Windows Server 2012, Windows 10, and Windows 8. For more information, see CTX213540.
Machine Creation Services™ (MCS)
-
When you create a catalog with custom properties, and use
Set-ProvSchemeto change the provisioning scheme without updating the same custom properties as set during catalog creation, the properties that are not mentioned in theSet-ProvSchemeare set to their default values. Also, if you set any custom property to its non-default value during catalog creation, it is overwritten to its default value after you runSet-ProvScheme.
Third-party issues
-
Chrome supports UI Automation only for toolbars, tabs, menus, and buttons around a webpage. Because of this Chrome issue, the automatic keyboard display feature might not work in a Chrome browser on touch devices. As a workaround, run
chrome --force-renderer-accessibilityor you can open a new browser tab, typechrome://accessibility, and enable Native accessibility API support for specific or all pages. In addition, when you publish a seamless app, you can publish Chrome with the--force-renderer-accessibilityswitch. -
In browser content redirection, after starting a YouTube video using the YouTube HTML5 video player, full-screen mode might not work. You click the icon in the lower-right corner of the video, and the video doesn't resize leaving the black background in the full area of the page. As a workaround, click the full screen button, and then select theater mode.