Troubleshooting Windows Server 2016 Terminal Services Manager Issue with Splash Screen

As an administrator, it can be frustrating to encounter issues that prevent you from providing a seamless experience for your users. One such issue is the stuck Splash Screen in Windows Server 2016 Terminal Services Manager, which has been reported by several users, including yourself, and remains unresolved since May. In this article, we will explore the problem and possible solutions to help you resolve it.

The issue appears when attempting to publish a RemoteApp from your server to users, specifically when using Advanced RemoteFX settings in Group Policy. Enabling this setting results in a full-screen display, while disabling it leaves a black box where the Splash Screen was previously located. However, there is no clear explanation as to why this is occurring.

To better understand the problem, let's break down the sequence of events that lead to the stuck Splash Screen:

1. The user initiates login for the RemoteApp.

2. The Splash Screen appears, displaying version information and loading details about the application.

3. Several seconds later, the Login dialog box opens, causing the Splash Screen to close prematurely.

This sequence is critical in understanding why the issue arises. It seems that the Splash Screen is not properly closing before the Login dialog box opens, resulting in the stuck screen.

To troubleshoot this issue, you can try the following steps:

1. Review your Group Policy settings and ensure that Advanced RemoteFX is enabled or disabled correctly.

2. Check for any recent changes to your server configuration, particularly those related to RemoteApp publishing.

3. Verify that all necessary dependencies are installed and functioning properly.

If none of these solutions resolve the issue, it may be worth exploring further by reviewing event logs, system configurations, and potential compatibility issues with the application or operating system.

As you continue to work on resolving this problem, remember that patience and persistence are key. You can also try reaching out to Microsoft support for assistance or seeking guidance from other administrators who have encountered similar issues.

By following these steps and understanding the sequence of events leading up to the stuck Splash Screen, you should be able to identify and resolve the root cause of the issue. Remember that troubleshooting is an iterative process, and it may take some trial and error to find the solution that works for your specific environment.

Windows server 2016 terminal services manager