none
RemoteApp RDS2019 - splash screens stuck on client RRS feed

  • Question

  • Hi!

    I am testing RDS 2019 with RemoteApp, and I have problems with startup splash screens. Each splash screen creates a button on the client’s taskbar and does not disappear from desktop and taskbar after the appearance of the main window. For example, I run three RemoteApp and I have three splash screens and three program windows on my desktop. And even if I close these windows, the splash screens will still remain on desktop and cannot be closed. This happens only in RemoteApp and does not occur with a remote desktop mode. I tried to recreate an RDS farm again, but it does not help.

    This does not happen with all programs (having splash screen), but with many. At the same time, there were no such problems at RDS 2012R2/2016. 

    As RDCB and RDSH used Windows Server 2019 with latest cumulative update (2019-01). As clients used Windows 10 1709/1809 with same update.

    Thursday, February 7, 2019 7:12 PM

All replies

  • Hi,

     

    >> Each splash screen creates a button on the client’s taskbar and does not disappear from desktop and taskbar after the appearance of the main window.

     

    Is there any screenshots of this issue? And have you checked if any relevant event logs?

     

    I have found a previous post that the cause is related to the specified remote app and program.

     

    Attached for your reference :https://social.technet.microsoft.com/Forums/lync/en-US/8e94d2f2-ed01-4ff6-8ad3-d0ab4f2c02b1/ts-web-remote-app-program-exiting-after-splash-screen?forum=winserverTS

     

    Thanks,

    Jenny


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, February 8, 2019 5:53 AM
  • The post you proposed did not help. And it is about a completely different situation.

    My situation looks like the screenshot. In normal situation (RDS2012R2/2016) when the main window has opened the splash screen should disappear from desktop and taskbar. But splash screen does stucks (RDS 2019). Of course I can set the main window on top and work in it, but all of this confusing. If I close the main window, the splash screen will still remain on the screen.

    Nothing interesting in logs. They hasn't any relevant errors or warnings. The farm and collection have default settings. The farm has been recreated several times and I tried different combinations of collection options.

    By the way this problem does not happen with Word/Exel/PowerPoint 2016. In these programs splash screen has correct behavior.

    RemoteApp spalsh screen stuck


    • Edited by Yuriy Kuzmin Friday, February 8, 2019 10:29 AM typo
    Friday, February 8, 2019 10:26 AM
  • Silence...

    Does everyone normally have RemoteApp in RDS2019?

    Monday, February 18, 2019 7:42 AM
  • Hi,

     

    When the splash screens stuck, please manually restart the explore.exe: close it in task manager and recreate, which would resolve the stunk.

     

    And you can use process monitor to capture logs and analyze what process have been stunk at the same time then dig further.

     

    Last but not least, kindly check and install the latest patch to see if the issue persisted.

     

    Thanks,

    Jenny


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 19, 2019 2:07 AM
  • Manually restarting explorer.exe on client side not resolve issue. After running explorer.exe i have identical situation (both desktop and taskbar).

    Process monitor cannot help, because the processes on the RDSH side do not stuck. For example, if I close main window of RemoteApp, the process on RDSH side will be correctly terminated, as expected. But on client side splash screen will remain both on desktop and taskbar while RDP connection is alive.

    This situation looks like bug in interaction between client and server. As if server doesn't inform client that splash screen window should be closed. And this happens not only with splash screens, but also with some pop-up windows (with progress bar etc).

    All available updates from Microsoft Update are installed on RDSH and on client.

    Tuesday, February 19, 2019 8:50 AM
  • Hi,

    >>By the way this problem does not happen with Word/Exel/PowerPoint 2016. In these programs splash screen has correct behavior.

    Do you mean that only third party app encounter this issue? Have you ever compared the workable remoteapp and problematic ones by checking parameters on notepad.

    Thanks,

    Jenny


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, February 20, 2019 8:49 AM
  • Yes, only some of third party enterprise applications encounter this issue on RDS2019. But these applications good working on RDS2012R2/2016 with identical parameters.

    I want to draw your attention to the fact that the splash screens and pop-up windows do not disappear EVEN when the process is terminated on the RDSH side. I can run the application and terminate its process 10 times. As a result, there are 10 splash screens, but there are no processes on the RDSH side.

    I am sure that RDSH should not display windows that actually no longer exist. And no matter what these applications are (from MS or third-party).

    By the way, I noticed such an interesting moment. If I launch the RemoteApp, which requires elevated permissions and appear UAC confirmation, then all ghost windows disappear. Thus, every UAC appearance (in the same remote session) immediately remove the stuck windows.

    Wednesday, February 20, 2019 12:59 PM
  • Hi,

    As a workaround, please Disable Use advanced RemoteFX graphics for RemoteApp group policy setting on your Windows Server 2019 RDSH server(s), disconnect any active RemoteApp sessions, then test to see if the issue still occurs.  Please note the client taskbar thumbnail previews and some other features will not function.

    Below is the path to the group policy setting:

    Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Remote Session Environment\

    Please reply back with your results.

    Thanks.

    -TP

    Wednesday, February 20, 2019 2:12 PM
    Moderator
  • It did not help. But there is a difference. Now the stuck splashscreen turns into a black rectangle at the moment when it should have disappeared. The rest of the behavior remains the same as before.
    • Edited by Yuriy Kuzmin Thursday, February 21, 2019 4:58 PM typo
    Thursday, February 21, 2019 4:54 PM
  • We have the same issue at our one and only client that has migrated to Server 2019. Still looking for a solution.
    Monday, March 4, 2019 12:07 PM
  • Silence...
    Monday, March 25, 2019 1:18 PM
  • There was an update that went out the last week of March that fixed some RemoteApp-related issues. This doesn't quite look like one of them, but it might be worth installing just in case.

    Do you by any chance know if the splash screen responds to WM_GETMINMAXINFO messages? We've been investigating an issue with how RemoteApp handles applications that don't.

    Thanks,
    Daniel

    Tuesday, April 2, 2019 7:45 PM
    Moderator
  • Hi, we've got the same error on our new farm of RDS2019, but just with 1C, we get the splash screen. Did you resolve your problem?
    Tuesday, May 28, 2019 8:06 AM
  • Hello all,

    Has anyone solved this? I just found out we are having the same problem as this. It only occurs on RDS 2019. If Use advanced RemoteFX graphics for RemoteApp is enabled, the splash screen stays visible and if it is disabled the splash screen turns into a black box as noted in above comments.

    On of our customers brought this up yesterday and I confirmed it on each of the Server 2019 installations.

    If anyone has any additional information, it would be appreciated. If I find something else, I will update here also.

    Thank you,
    Stephen

    Friday, July 19, 2019 11:14 AM
  • Hello TP,

    There were several responses to your suggestion and yet there is no response from your side. How do we get Microsoft to look at this without paying $500 for a support ticket? I have several customers that this is happening too and no course of correction except to go back to 2016 (which has it own set of issues with Windows Updates that take forever to complete).

    Thank you,
    Stephen

    Monday, July 22, 2019 1:53 PM
  • There is still a problem...

    RemoteApp on Windows Server 2019 build 17763.652

    Client - Windows 10 1903 18362.267

    Thursday, August 1, 2019 11:31 PM
  • Do you only see this with Windows 10? Have you had any experience with Windows 7 trying it? I have not tried Windows 7 to see what happens (need to get to a Windows 7 machine).

    I cannot believe that this had not had any attention yet!

    Saturday, August 3, 2019 11:28 AM
  • Today we experienced the same issue with our software on a customer's system.
    With Windows Server 2019 different kind of dialogs (not just splash screen, also regular dialogs) get stuck after they have been closed in the RemoteApp.
    But on the client's computer they are still visible, although they don't exist on the server anymore.

    They are always above of the main window. If we minimize the main window they become minimized too, but they are restored too if we restore the main window.
    If we close the RemoteApp, the windows will close too.

    What to do? Shall I tell the customer not to use Windows Server 2019?!
    The customer also has an older Windows Server with our application as RemoteApp. Everything is fine there.


    Kind Regards
    David Gausmann

    Thursday, August 15, 2019 1:07 PM
  • I have same problem =:(

    My remoteapp users cant working normally with this...

    Monday, August 19, 2019 1:04 PM
  • I have same problem =:(

    My remoteapp users cant working normally with this...

    Add me to the list!  I have a customer that isn't terribly impressed that their shiny new (expensive) RemoteApp server project is still not ready for production use.

    Is this issue being investigated by Microsoft at all?  I just tried to place a support call about it and was told that as long as it was related to "third party" software, Microsoft won't do anything about it.  The support rep tested "Calculator" and "MS Paint" and said that we would have to take the issue up with the application developers.

    Anything we can do to get this issue addressed?


    David Moen Small Business Specialist Salmon Arm, B.C. Canada Eh!

    Thursday, September 19, 2019 10:41 PM
  • Done!  I hope they can get this fixed ASAP.  Overall the end user experience with Server 2019 hosted RemoteApps has been fairly disappointing!

    David Moen Small Business Specialist Salmon Arm, B.C. Canada Eh!

    Wednesday, October 9, 2019 4:36 PM
  • I have the same problem, except it's with MIcrosoft Dynamics GP. I don't think this is a 3rd party problem but an issue with Server 2019. This should be escalated by Microsoft. They probably already know about it but haven't prioritized it. 
    Monday, October 14, 2019 3:58 PM
  • We have same bug. 18.12.2019
    Wednesday, December 18, 2019 8:13 AM
  • Same problem( No chance?

    С Уважением, Плотников Дмитрий.

    Monday, January 13, 2020 7:57 PM
  • 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.

    • Proposed as answer by AlexLM75 Wednesday, January 22, 2020 4:58 PM
    • Unproposed as answer by AlexLM75 Wednesday, January 22, 2020 4:59 PM
    • Proposed as answer by AlexLM75 Wednesday, January 22, 2020 5:01 PM
    Tuesday, January 21, 2020 9:52 PM
  • I have the same issue and tried this fix but find the remoteapp signs out straight away after making the connection when using a 2016 version of the file.

    Was there anything else you did to get it going?

    Friday, January 31, 2020 9:29 AM
  • Initially, I got this to work with 2 virtual RDS servers that were setup as a clean Server 2019 install.  However, I'm seeing the problem your mentioning as well with my physical 2016 server that was a in-place upgrade to 2019.  The RemoteApp starts to open and then closes.  I'm thinking its because of the in-place upgrade.

    If I find a (another) workaround I'll come back and post here.  Sorry. @JaiLM


    Monday, February 3, 2020 7:47 PM
  • Thanks Ryan, heres hoping MS are looking at this!

    Friday, February 7, 2020 12:11 AM
  • We have the same issue here, with no resolution yet.  Our two 2019 RDS servers are not in-place upgrades; they are clean installs, and we are still seeing the issue.  This is very annoying and frustrating to our users.

    I have noticed that if the user relaunches the RemoteApp after having (1) closed the app when the splash screen bug occurs, (2) waits for the splash screen to eventually disappear when the app process has died, and (3) does not log out of the underlying RDP session, then the problem the does not reappear on the relaunch.  My best guess is that somehow RDP is not detecting the close event on the splash screen and thus continues to display that rectangle even though the window has actually disappeared according to the running executable.  The issue thus seems to have to do with RDP and not the application.

    Tuesday, February 11, 2020 5:46 PM
  • Hi Mike,

    Did you ever get this resolved? I am working on GP published remotely and facing the same Issue.

    Saad Arslan

    Tuesday, February 18, 2020 4:34 PM
  • Hey All,

    Having the same issue here with ghost windows in Dentrix Enterprise running as a RemoteApp on RDS 2019.  We did not have this issue with RDS 2008.

    We get the same ghosting on Win10 and 7.

    With Dentrix, the initial loading window ghosts and throughout the session other windows will randomly follow suit.

    I have disabled RemoteFX which just turns the windows black as others have mentioned, but at least users aren't trying to interact with a non-existent app window.

    One possible lead... If I remote into the RDS server and kill the rdpshell.exe process on the user's session the ghost windows go away and rdpshell restarts itself.  Maybe an option to create a workaround to get by.

    We too have opened a ticket with MS and they blame our 3rd party app.

    Thanks for keeping this thread alive!

    Wednesday, February 19, 2020 1:06 AM
  • Bump on this one, anyone got a real solution that doesn't require Svr 2016?



    Cheers


    Wednesday, March 18, 2020 5:10 PM
  • Hi

    We struggle with the same problem.

    Windows 2016 remoteapp work like intended.

    Windows 2019:
    - with remoteFX on - popup / splash screen windows stay on top. Never hide.
    - with remoteFx off - black squares instead of popup windows.

    Any ideas ?

    Thursday, March 26, 2020 12:38 PM
  • Just came across this thread as we have also discovered this bug.

    I can report the same issues on Server 2019 RemoteApp for us. Both Sage 50 and Quickbooks are borderline  unusable on the 2019 platform because of "ghost windows" that don't exist yet pop in front of actual active windows, constant window ordering problems, popup dialog boxes hidden behind the main window causing the app to appear unresponsive...

    How does something that fundamentally breaks our ability to use this product not get fixed for over a year?

    We are being forced to revert our customers back to Server 2016 as 2019 simply doesn't work properly.



    Thursday, April 16, 2020 4:38 PM
  • Please share the files you got this working with. Cant find that rpdshell version anywhere.
    Friday, May 1, 2020 7:13 PM
  • I support, it also does not work. Updates are all installed. I am waiting for a response from Microsoft or I will write a claim to compensate for the cost of licensed software.

    Wednesday, May 13, 2020 2:27 PM
  • I ran into this recently and potentially have a resolution.

    On the RD Server I updated the registry to disable transparency for the local user profiles.

    REG_DWORD: EnableTransparency = 0
    HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize

    Before I made the change I had a user log in and confirmed they had the phantom image. I logged him out and made the registry change under his account. He logged back in and it was no longer there.

    Another user didn't confirm it was there immediately before the change, but did confirm it wasn't there after the update. She was seeing it every time prior to that.

    I have added this to our RD Server GPO so all new logins will have it disabled as well.

    Thursday, May 14, 2020 3:13 PM
  • Unfortunately this did not fix it. Our test the same day seemed to look good, but the next day it was back to the ghost image.

    Maybe it will trigger an idea for someone else.

    Monday, May 18, 2020 7:46 PM
  • This is bad news bears. It worked for us too, but we haven't heard back that its happening again for anyone yet. If you fully log the user out, and back in, does it go away again? Maybe by forcing pull logoff for idle users would be the additional piece to this registry work around for now?
    Tuesday, May 19, 2020 2:42 PM
  • We are having a similar problem with a remote app and have been using a workaround when it occurs.

    What happens if the user presses CTRL+ALT+END followed by 'Cancel' on the screen that appears?


    Thursday, May 21, 2020 8:37 AM
  • Not sure, but can try next time we're told about it. Is this your workaround?
    Thursday, May 21, 2020 1:12 PM
  • Does anyone have any update on this? Still happening.

    Michael

    Friday, June 5, 2020 2:28 PM
  • This is bad news bears. It worked for us too, but we haven't heard back that its happening again for anyone yet. If you fully log the user out, and back in, does it go away again? Maybe by forcing pull logoff for idle users would be the additional piece to this registry work around for now?
    I rebooted the server the same night I made the change. Still came back in the morning.
    Monday, June 8, 2020 7:12 PM
  • Same thing. We still have several users having this issue. It helped greatly to apply the registry setting mentioned above, as well as setting Session policies to fully sign out users that are inactive (or sign them off when they disconnect), as it seems it mostly comes back after a user, or several users, have been logged on for some time.

    Michael

    Thursday, June 11, 2020 4:47 PM