Citrix Self Service applications not appearing in Start Menu or Desktop

Are you finding it takes a long slow time for Citrix applications or desktops to appear in the Start Menu when users subscribe to them using Self Service? Beginning with Citrix Receiver 4.2.100 we were given the ability to place applications and desktops directly on the Start Menu.

To read up on configuring applications to show on the Desktop or Start Menu see

By default applications and desktops that you subscribe for are placed in the root of the Start Menu (by default). You do have the option to use a specific folder of your choice using methods such as:

  1. The STARTMENUDIR= switch when installing Receiver –
  2. Setting the folder location within the StartMenuDir REG_SZ value found in the Dazzle key using RegEdit.1-min
  3. By using the Citrix Receiver receiver.admx Group Policy ADMX file and specifying the Start Menu location.2-min

Nonetheless for the best user experience you will probably want to configure SSO (Single Sign-On) with Receiver so that users can simply click an application within the Start Menu and a successful connection is made to back-end Citrix XenApp/XenDesktop machines.

With Receiver 4.5+ you can use Configuration Checker to run through the SSO requirements such as making sure StoreFront is in the correct zone. This is a good place to start. If applications are not appearing in the Start Meny, read on.So what if you have all this in place yet applications take an age to appear in the Start Menu? The default time is 2 minutes for Receiver to contact StoreFront to retrieve the list of resources but I’ve witnessed a machine sit 10 minutes without applications being enumerated. You can manually force a poll/enumeration using Self Service by:

  1. Opening CMD.
  2. Changing the directory to C:\Program Files\Citrix\ICA Client\SelfServicePlugin\.
  3. Running command SelfService.exe -poll.

Note that if using a 64bit machine the default directory is C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\.  3-min

This however is not reasonable, as users from time will subscribe to new resources and others will be removed. Can we depend on the current default polling setup? Fortunately, we can use the registry to speed polling up.

Firstly set the following registry keys to speed up resource enumeration:

32bit machines – HKLM/Software/Citrix/Dazzle

64bit machines – HKLM/Software/WOW6432Node/Citrix/Dazzle

REG_SZ InitialRefreshMinMs = 1

REG_SZ InitialRefreshMaxMs=14-min

If that doesn’t work have a look at your network provider order list. It could be that another single sign-on network provider is above the Citrix Single Sign-on network provider. If this is the case, move Citrix above and then log off/on to test.

Note: You can change the provider order en masse by modifying the ProviderOrder REG_SZ value under HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order.

If that doesn’t work try ths:

32bit machines – HKLM/Software/Citrix/Dazzle

64bit machines – HKLM/Software/WOW6432Node/Citrix/Dazzle

DWORD MaxSimultaneousFetches = 6 (of decimal value)

DWORD MaxSimultaneousSubscribes = 6 (of decimal value)5-min

If that still doesn’t work you’re really unlucky. Try turning off Automatically detect settings within Internet Explorer or Edge. This seems to have fixed it for a few people.


Additional Notes:

  • Subscribed applications and desktops can be found in the Start Menu root by default or within a folder of your choice that you have specified. The resources are also found in Add/Remove Programs.7-min
  • The resources persist even upon reboots unless the user unsubscribes (removes) the resource or the Windows profile is deleted.
  • If using HTTP stores implement the following registry key or else you will get “Your apps are not available at this time” when launching Receiver and connecting to the store:
    • Add a REG_SZ entry with the name ConnectionSecurityMode and the value Any. This REG_SZ value should be created in:
      • HKLM\Software\Citrix\AuthManager – 32bit machines.
      • HKLM\Software\WOW6432Node\AuthManager – 64bit machines.

Leave a Reply