User Launch failures may be seen on the VDA version 2303 and VDA version 2305 if the VDA machines are brought up on-demand for the launch. The initial launch may fail but the subsequent launch attempt after a wait succeeds. VDA de-registration event would be seen following the failed launch.

Symptoms / Signature:

• VDA version 2303 and VDA version 2305
• End users may see a “Resource Not Available” message for the failed launch attempt.
• VDA de-registration event would be seen following the failed launch attempt and the reason displayed for the de-registration would be “RegistrationStateMismatch”
• Validate the following is reflected in the track logs from the BrokerAgent module - LaunchManager.PrepareSession(<GUID>): Waited long enough to switch to registered mode, but did not happen

Customers facing this on VDA 2303 are recommended to upgrade their VDAs/BrokerAgent to VDA 2305.1 with the fix below: 

For “Random”  or "Static" VDAs –

• Use the standalone minimal installers available under the Components section of the Citrix Virtual Apps and Desktop 2305 Downloads at this link: 

• Download the brokeragent_x64.msi file in this article.

Problem Cause

Citrix investigation has found that the changes introduced in VDA version 2303 to the CommandQueue’s registration event handling mechanism cause a delay in the registration notifications from getting sent to the listeners, including the LaunchManager. LaunchManager waits for the registration notification to process the launch request, but due to the delay in receiving the notification, VDA is deemed as not registered and the launch fails. In addition, this would cause a re-registration of the VDA, following the failed launch. The issues will be addressed in a future release.