Server 2019 RemoteApp Splash Screen Stuck

Occasional Contributor

Hello all,


We have been transitioning some of our remote servers from 2012 R2 or 2016 to 2019 when we recently saw this issue. We have an application that is installed on the server and published as a RemoteApp for the users. When the application launches, there is a Splash Screen that shows the version and information about the app while it is loading. As the Login dialog box for the app is opened, the Splash Screen is closed several seconds before it opens. The problem is that the Splash Screen is stuck on the screen. If the Advanced RemoteFX setting in Group Policy is active, the screen will remain in full and if it is disabled, it will leave a Black Box in the exact location that the Splash Screen had been. 

There is a thread on Technet about this and there are no answers or responses since May. This is exactly what we are also seeing.


Really do not want to have to pay Microsoft for an incident to get an answer as to why this is not working as it does in 2012 R2 and 2016 without any issues. The version of 2019 is Version 1809 Build 17763.529.


Thank you,


4 Replies

Has no one else seen this happening or is no one in this community using 2019 and Remote Apps?

I am using RemoteApps in Windows Server 2019 but i'm not using RemoteFX. Tbh i thought that technology was replaced by DDA (Discrete Device Assignment).
can I know what GPU you are using and what application is having that issue?

@HotCakeX these are virtuals running on T3 instances at AWS EC2. DDA seems to be for graphic intensive applications that can use a GPU for better performance with graphics using a PCI Express connected device.


The application is our Windows application that we host for some of our customers called Micro Key Millennium that we develop in house. In the link to the TechNet thread, there are people seeing the same issue with Acrobat Reader, so it is in general happening with most applications that have a splash screen.  


I had the splash-screen "hanging" issue too and found that as a workaround I copied the C:\Windows\System32\rdpshell.exe from a 2016 server over to my 2019 server and the issue went away. You have to take ownership of the file on the 2019 before you can delete it or rename it if you want to keep it around for back up.

My 2019 file version was 10.0.17763.404

The 2016 version I replaced it with was 10.0.14393.2828

Hope this helps those who would like to stick with 2019 until a fix is made from Microsoft.

@Stephen Kovacsiss