Remote Desktop Connection (Remote App) behavior problems

[Derrick Rieke]

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?

[#2]

Try Start > Settings < Apps, find Remote Desktop Connection and select it. Click Advanced settings. Try Reset does that help at all?

[#3]

Nope... Problem exists even with a fresh install of the insider build and then creating the connection to the remote app.

[#4]

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.

[#5]

I am not sure what version the server is running on. 

[#6]

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

[#7]

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.

[#8]

Hi Ryan,

what kind of rendering problem do you have? We do have some too. Can you describe your environment?

[#9]

They are Windows Server 2012 R2 server in an RDS configuration. We have 2 session hosts serving up the remote apps.

All servers are virtual, running on Hyper-V 2012 R2 clusters.

So far, with Remote FX turned off, when I try to maximize the WSUS remote window, I can't see it anymore. It just disappears. I have to guess where the top bar is, and double-click to de-maximize it. Sometimes, I get the same problems when I try to resize the window.

I imagine this won't be the only problem I see.

It is better than trying to guess where the context menu options are when I can't see them. :P Not the best way to authorize updates...

This is on 1803 Education Edition as my workstation.

[#10]

Also, running build 17134.48.

[#11]

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.

[#12]

Which update?

[#13]

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

[#14]

I see KB4103721, which is the only security update I see installed. However, I upgraded on the May 15, which is the same day this update was installed. There may have been an update before the upgrade killing things. I will have to do some more testing.

[#15]

That's what I have seen also. I uninstalled this update and things worked fine after a reboot.

Your mileage may differ :-)

[#16]

KB4103714 seems to be the culprit in 1709, according to some sources, but not in my environment. In fact, I'm not having any problems on anything but 1803.

[#17]

We are finding that all of the cumulative updates for all versions of Windows 10 in May are suspect.

So far uninstalling the following KB's fix the issue - 4103723; 4103731; 4103727; 4103721

We have had to actually delete these updates from our SCCM server to stop re-deployment.

We believe that these updates all have RDP issues

[#18]

Uninstalling KB4103721 did NOT fix the problem for me.

[#19]

KB4100403 was release May 22nd. I don't see anything in the documentation for a fix on this one.

[#20]

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,

[#21]

I installed that update this morning and the RDP is still broken. Uninstalling it again will fix the issue.

MS your May updates are flawed.

[#22 · Accepted solution]

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.  

[#23]

June updates are coming fast. Let's hope this gets in the cumulative!

[#24]

If you don't want to wait for the next Insider Preview version this 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.

[#25]

The June 1803 Cumulative Update seems to have fixed this for me.

Update: It worked for a minute, then quit. Weird...

[#26]

---

@Ryan Cooley wrote:

The June 1803 Cumulative Update seems to have fixed this for me.

---

Unfortunately I just checked on one of our systems and this Rollup did not make a difference here.

[#27]

Same here this patch did not fix our RDP issue.

Will have to pull it from my patching cycle, again. This is now 2 months my network isn't patched.

MS what is going on??????????

[#28]

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!

[#29]

Totally agree on the FULL ATTENTION

We use RDP to access our ERP system. Broken RDP = no access

Rolling back to April and things are fine.

[#30]

I have to roll all the way back to 1709 to get it to work, for some reason. Nothing I do in 1803 helps! 1709, fully patched, works fine for me.

[#31]

I called Premiere Support. They suggested copying the MSTSC.exe and mstscax.dll file from 1709 and registering that dll (Regsvr32).

Of course, there is the whole mess of taking ownership of the files, etc and replacing them, which takes some work, but I got it to work!

[#32]

See the reply from Rob Thayer above, links a (long) post but one poster has a script that does all that, i.e. replaces the driver users rights then puts them back etc.

[#33]

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

[#34]

The late June update seems to have fixed the RDS context menu problem in 1803.

[#35]

I've only seen this problem if RemoteFX is disabled.

[#36]

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!!!