If you are connecting to an App or Desktop and it takes longer than usual, or if you need to give the applicatioin or Desktop more time to launch – you may consider altering the ApplicationLaunchWaitTimeoutMS registry key on the VDA’s hosting your applications or desktops.
In the situation where you find the initial connection timing out and dissapearing from screen, this may be the necessary action to take.
The ApplicationLaunchWaitTimeoutMS key has a timeout value defined. This object can be found in RegEdit under HKLM -> System -> CurrentControlSet -> Control -> Citrix -> wfshell -> TWI. When changing this value, specify the timeout in miliseconds using decimal. If the value does not exist, create one using DWORD (32-bit).
10 seconds is the minimum value, so you can not set a time lower. If no key exists, this defaults to a timeout value of 1 minute (as of August 2015).
David
April 8, 2020Hello. Well, almost 5 years later and I am finding this helpful. Thanks for documenting this regkey. Just an observation. You accidentally dropped the Citrix out of the key path. Should be:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Thanks,
David
George Spiers
May 22, 2020Thank you! Corrected.
George Spiers
July 11, 2020Thank you.
Musklor
December 10, 2020Hello, if I have some issues with a published desktop (OS Servers), I have to set this key? Or another?
Musklor
December 10, 2020Hello, I have a frozen “welcome screen” when users reconnect to their published desktop. (OS Servers 2016).
We have Ivanti, app layering.
DelayedDesktopSwitchTimeout key?
ApplicationLaunchWaitTimeoutMS key?
Robert
October 20, 2021Musklor, This worked for me. Change the HighDPI setting to use native resolution
obiwan
December 11, 2023Hi George, is this still apply for recent VDA versions like 2308 ?