Published application fails to start outside of Desktop session

1 users found this article helpful



The issue is a design behavior of Microsoft Windows. This issue occurs because you try to start an application that relies on the Explorer.exe file. By design, the TS RemoteApp session implements limited functionality. For example, the TS RemoteApp session does not process the following items:

Workaround 1

Create the user profile by first launching a full desktop session.

Workaround 2

Some applications that rely on the Explorer.exe file may run in the TS RemoteApp session if you add the Runonce.exe file to a user’s logon script. To do this, follow these steps:

  1. At the Group Policy Management Editor go to User Configuration > Policies > Windows Settings > Scripts(logon/Logoff) > Logon.

  2. Click Add.
  3. In the Script name box, type runonce.exe.
  4. In the Script Parameters box, type /AlternateShellStartup.

  5. Click OK two times.

Please refer to Microsoft article for more information:

An application does not start in a Windows Server Terminal Services RemoteApp session

Was this article helpful?

Tell us how we can improve it.