Forum Discussion
Server 2019 RemoteApp Splash Screen Stuck
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.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/f64d1d8b-b99b-4e22-95be-38da6ed8f33c/remoteapp-rds2019-splash-screens-stuck-on-client
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,
Stephen
30 Replies
- Hello Stephen,
I have the same issue with Windows Server 2019. Have you found a solution for the problem?
Best regards!I installed KB5003703 and since doing this I have not been able to replicate this issue. I still need to follow up with some additional users, but it is looking like this might have fixed.
https://support.microsoft.com/en-us/topic/june-15-2021-kb5003703-os-build-17763-2028-preview-687c70f6-98ed-4440-9cc7-72c9ef735bfe
It also has the following fixes listed:
- Addresses an issue that causes Remote Desktop sessions to stop responding while the User Datagram Protocol (UDP) is enabled.
-Addresses an issue that causes the images and text that first appear when you open a RemoteApp to remain on the screen indefinitely.
- confirming this patch does fix the issue 🙂
Had the same problem with 1C (https://1c.ru/) on windows server 2019 in remoteapp mode
Fix:
GPO - Computer Settings/Policies/Administrative Templates/Windows Components/Remote Desktop Services/Remote Session Environment
Use advanced RemoteFX graphics for RemoteApp - Enabled
Enable RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1 - Enabled
Configure RemoteFX Adaptive Graphics - Enabled (1. Let the system choose the experience for the network condition)
Apply this policy to RDS server, gpupdate /force, restart server not required, just users full logoff/logon.dmitrypodporinov I tried this and I still have the same issue.
Hi,
I had the same issue and it was related probably with some Windows 10 build.
Solution for me:
- On your Server 2019, open the registry editor and navigate to HKLM\SOFTWARE\Microsoft\Terminal Server Client
- Create a new d-word (32-bit) value and name it UseURCP with decimal value of 0
- Reboot server
The solution i have found here: https://itcalls.net/windows-10-version-1809-black-screen-when-connecting-rdp-to-server-2019/
no change for me sadly.
Soon as you minimize the screen you're left with a black box where the pop up would have been that is on top of everything but the RemoteApp screen
ryan123615 I spoke too soon. The issue is still occurring. However, it definitely seems to have reduced the frequency of it occurring.
KrzysztofSek Just tried this out and so far I have not been able to get the problem to occur since making this change. I was able to get a ghosted screen under my outlook every time I opened the calendar and switched windows. Have not been able to get that to occur since I made the registry change.
Crossing my fingers!
Having the same issue as well. Been looking for a solution over the last year now.
I found a sort of workaround.
i used the remote app for windows 10 here: https://www.microsoft.com/en-gb/p/microsoft-remote-desktop/9wzdncrfj3ps?activetab=pivot:overviewtab
I also had to update the RDP server to use html5 for the RD gateway, sorry i can't find my link to that but it was a few lines of PS
The splash screen doesn't show up anymore but it does mean you have to use Win10 and use the app.
It's not a fix, it's a completely different way of doing it, hope that helps
ryan123615the problem with that is the RemoteApp is very limited in what one can do. You can't redirect local resources for example...
- Us too, as noted we had to remove the Splash from our app. I guess that Microsoft does not read these.
Did you find a way to fix thisStephen Kovacsiss
I am still getting it on the newest updates as of today
ryan123615 I have not seen a resolution from Microsoft. We changed our application to remove the splash screen as we had no way around it. It is a bit ridiculous that there has not been any solutions to this.
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.
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.
