Published Applications or Desktops not Launching or Disappear during Launch

WARNING! Using Registry Editor incorrectly can cause serious problems that may 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.

Cause 1 – LogoffCheckSysModules registry value incorrectly configured

On the XenApp Server VDA, check the registry for the following key:


Name: LogoffCheckSysModules

Type: REG_SZ

Value : (Applications executable name. For example, MYAPP.exe)

If the LogoffCheckSysModules registry value exists, then make sure that it does not contain the executable for the application that the user is trying to launch. If the executable is present in this registry value, remove the executable name from this registry value.

  • This registry value is meant to close out secondary or child processes that a main application will launch but not close upon exit. Putting the main executable for an application under this key can cause it to close out the application before it launches.

Microsoft Remote Desktop Session Host has a similar registry configuration for the same purpose. Make sure the application executable is not included as a value under this key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerSysprocs

Name: (Application’s executable name. For example, MYAPP.exe)


Base: Hexadecimal value

Data: 0

Note: If a key exists with the executable name of the application having launch issues, backup the registry key, and then delete it.

Cause 2 – Application not launching in a timely manner

There are a couple registry values that can be tweaked to give the application more time to launch. For example, if you are publishing Explorer, then Explorer will not launch unless LogoffCheckerStartupDelayInSeconds is set to 10 seconds (hexadecimal) or higher.


Name: LogoffCheckerStartupDelayInSeconds


Base: Hexadecimal Value

Data: <An integer for the length of time to wait for application start. – Enter the delay time in seconds, up to 10 minutes (600 seconds)>

Note: Start with 10 seconds and move up from there 10 seconds at a time if needed.


Name: ApplicationLaunchWaitTimeoutMS


Base: Decimal Value

Data:<desired additional time-out, in milliseconds >

Note: Start with 10000 milliseconds and move up from there to 30000 milliseconds if needed.

Desktop VDAs have an additional registry value that can be tweaked. If a desktop VDA closes before the logon process completes, you can allocate more time to the process. The default for 7.6 and later versions is 180 seconds (the default for 7.0-7.5 is 90 seconds). On the VDA machine (or the master image used in a Machine Catalog), set the following registry value:


Name: AutoLogonTimeout


Base: Decimal Value

Data: <specify a decimal time in seconds, in the range 0 to 3600>

Note: This setting applies only to VMs with desktop (workstation) VDAs; Microsoft controls the logon timeout on machines with server VDAs.


  • No Related Posts

Leave a Reply