Forum Discussion
Reconnected RemoteApp session not showing locked session password prompt
The issue below was observed in v1.2.945 (x64) Windows, I'm unsure if this worked properly in a prior version, or on any other platforms. In this example, Calculator is shared as a RemoteApp on a...
alvinlau
Microsoft
MicrosoftHi sberens! Do you have the WVD side-by-side stack installed on your session host? If so, what is the version? Meanwhile, let me set up a Windows Server 2016 and see if I can reproduce the issue on my side.
Thanks,
Alvin
alvinlau Good day!
When running qwinsta, there's a sessionname of rdp-sxs200326004 on the two Session hosts configured for the Host pool publishing the Apps used in our scenario.
An FYI that the Server 2016 instances were deployed from the Azure portal gallery, and are not custom images, if that helps.
Thanks again, and if you need anything else, please reach out. 
Kind regards,
Sean
- alvinlau
Hello sberens!
I installed the same side-by-side stack on my VM running Windows Server 2016 with all the updates installed.
I could almost reproduce the issue. When auto-reconnect was done, I saw that the title bar of the remote Command Prompt window changed to the old themeless one; However, it turned back to normal in less than a second, and without typing anything on my keyboard, mouse input started working again.
Would you mind if you create a test account on your WVD deployment and let me remote in?
Also, what is the Windows version of your local machine?
Thanks,
Alvin
alvinlau Good day!
Thank you for attempting to repro in your environment, and I'm glad to hear it worked as we would expect.
Unfortunately I cannot provide access to the environment as it is production, but I will try to reproduce in my sandbox and will follow up by Wednesday.
I'm running Windows 10 Pro 1909 (OS build 18363.836), and Remote Desktop v1.2.945.0 (x64).
Kind regards,
Sean
alvinlau Good day!
I was able to validate that my sandbox environment exhibits the same behavior as your environment. Reconnect popup appears, then shortly after reconnecting, the window theme bounces to classic, then it returns to normal and I can interact with the App, and the UI controls (Min/Max/Close). No key presses required! (I also learned that the space bar will return the session to usable, in the original scenario)
I don't know that it would make a difference, but my production host pool has 2 session hosts, but my sandbox only has one.
I'll continue to troubleshoot and compare the two environments for differences, but if you have any recommendations, please don't hesitate to reach out.
Thank you again for your time.
Kind regards,
Sean