Why an application using MS UI Automation does not work in a RemoteApp session on Windows Server 2022 ?

Question

The same application works smoothly in Alternate Shell mode on the same Windows Server 2022.

Here is the screenshot (image above) taken in the RemoteApp session. Note that Command Prompt and Inspect both work in the same RDP RemoteApp session. It is seen that Inspect is unable to identify the UI elements of the Command Prompt's Properties dialog.

Here is the screenshot (image above) taken in the RDP Alternate Shell session. We see that Inspect is quite capable of identifying the UI elements of the Command Prompt's Properties dialog.

For information, the malfunction with RemoteApp does not affect older versions of Windows Server (2019, 2016 and 2012).

Here (image above) is my Windows Server version information.

Answer 1

Hello there,

Please check the System event in Event Viewer to confirm if there is any related event has been logged.

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:

The Run registry entry

The RunOnce registry entry

The startup applications

Try running the startup applications as a part of a user's logon setting.

An application does not start in a Windows Server Terminal Services RemoteApp session https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/application-not-start-in-remoteapp-session

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–