Forum Discussion
Remote Desktop Connection (Remote App) behavior problems
Hello, running 1803 (build 17134.1) and have been running into a "Remote App" behavior problem for a while (not sure what version it started on).
We have a remote app installed on our desktop that is connected to an application we use hosted by someone else. It is hard to describe the behavior, but when other windows are open on our host machine (Edge, Teams, MS Office, etc.) and when a user has multiple screens (remote app only using one), when we call for something to happen in the remote app (like run a report), the remote app appears to freeze, and the only way to get it to refresh, is by clicking on one of the other programs that are open on our host machine (on the task bar) and then back to the remote app.
Right clicking (trying to call a right click command) also is not working in this scenario.
My gut tells me it is something related to the insider build of Windows and not the company that is hosting the application, because it is working fine on all the machines running the currently released version of windows and it is showing this behavior in 2 machines I have running the insider build.
Any ideas?
My device did an update this morning to Windows 10 Pro Insider Preview - 17677.rs_prerelease.180520-0940.
I think the issue has been resolved with this Windows Insider release! Not sure when the GA of this update will be. My guess is that Microsoft will issue a separate update to fix this problem fairly soon.
38 Replies
The late June update seems to have fixed the RDS context menu problem in 1803.
I'm not sure if these are related but My problem with win 10 remote app is when minimising and maximising windows the rendering gets all screwy.
outlookIEexcel
I've only seen this problem if RemoteFX is disabled.
If you don't want to wait for the next Insider Preview version https://social.technet.microsoft.com/Forums/windowsserver/en-US/f3e9852b-393c-4aa0-9d2f-961a82cfc603/remoteapp-after-windows-10-update-1803-are-slow-and-right-mouse-button-is-not-responding-it-reacts?forum=winserverTS TechNet thread offers a community provided powershell script that'll apply the 17677 build version of the RDP client components on Win10 1803, which appears to address some of the issues people are seeing with RDP.
If you don't want to read the whole thread (it's quite long), skip down to posts starting on 5/30 where you'll see the first offer of a solution.
As highly recommended, you should install in a test environment first to see if it fixes your problem.The June 1803 Cumulative Update seems to have fixed this for me.
Update: It worked for a minute, then quit. Weird...
Actually, it seems to work for the first little while and then quits. Strange...
This is VERY disruptive to my work as a server administrator. I built the RDS environment here at work and now it's practically unusable! This needs full attention!
My device did an update this morning to Windows 10 Pro Insider Preview - 17677.rs_prerelease.180520-0940.
I think the issue has been resolved with this Windows Insider release! Not sure when the GA of this update will be. My guess is that Microsoft will issue a separate update to fix this problem fairly soon.
June updates are coming fast. Let's hope this gets in the cumulative!
Obviously there is a problem going on here if multiple people are having the same problem.
Microsoft, do you have any comment, solution or a possible date that a fix will be issued?
Thanks,We're seeing this on Windows 10 v1607, v1703, v1709, v1803
Uninstalling the latest update seems to fix the issue. When we uninstall the update nd reboot a Security update is automatically installed and the RDP connections are restored.
Believe that MS is pushing something behind the scenes.
- Which update?
The Security update dated after May 8, 2018
If there is no Security update listed do the Cumulative update , same date.
This is for all versions of Windows 10
You can get it work again
Change the following group policy either locally or via GPO in an AD environment on all Terminal Servers/Remote Session Hosts:
Set the following to Disabled
Computer Configuration/Policies/Admin Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment: Use advanced RemoteFX graphics for RemoteApp – Disabled
This worked, but I'm having some issues with window rendering now. I don't think the rendering problem is an 1803 issue, but a product of turning off the advance Remote FX features.
Hi Ryan,
what kind of rendering problem do you have? We do have some too. Can you describe your environment?
We are also having this problem. 1803 also.
When right clicking inside of a remote app, it is difficult to make the contextual menu appear. You have to try many many times. It looks like a displaying issue.
If you do it in a remote desktop window, it all works fine.
Only with 1803. Works fine with other versions of Windows 10.
The TS is running on W2012.
I am not sure what version the server is running on.
This helped! Thanks a bunch! (Originally, I was going to do a clean install, but I knew there had to be a few "quick fixes: before I started the LOOOOONG process of a clean install) AND your fix was it!!!
- Nope... Problem exists even with a fresh install of the insider build and then creating the connection to the remote app.
