Remote Desktop window resizes when moved

This article has some useful information.

Read over it.

https://www.makeuseof.com/tag/5-tips-fixing-remote-desktop-screen-settings/

Thanks for the link. It appears I have somewhat isolated the issue. The remote app connections are resizing properly on users with Windows 7 laptops. Those are running RDP version 8.1. The users having issues are all running windows 10 version 1709. All of them are having issues running the .rdp file created by the remote app. It could be a simple issue with the new windows 10 version not wanting to run from the .rdp connection properly, which is similar to the statement from Microsoft on the remote app configuration. They are expressly removing the .rdp option in remote app and you have to go through the rdp gateway. I am going to try going that route to see if the remote apps work on Windows 10 and that may resolve the issue. Not sure how it is going to resolve other issues, though.....

There's a similar windows 10 thread just below yours. I'm also seeing this issue on Windows 10 1709 only

https://community.spiceworks.com/topic/2100680-issues-when-maximizing-rdp-app-in-windows-10-build-17...

I'm having this same issue with both 2008 R2 remote apps and Server 2012

I have found a fix for it, but I would not necessarily call it a fix. I had some users that were on build 1703 of Windows 10. Those users had no issues when using Remote App and all the applications sized correctly and could move from one window to another without issue. I ended up copying the mstsc.exe and mststax.dll files from the C:\Windows\System32 and C:\Windows\SysWOW64 from that computer and then copying them into the machines running 1709 versions of Windows 10. This actually "fixed" the issue as in the windows were able to perform as they did before without any scaling or resizing issues. I am hesitant to call this a long term fix as those files may get written over on the next update. The process for changing the files is rather tedious as well. I had to take ownership of those files in both directories, give myself full permissions, then I could copy the files in. It would be better if I had someone that could use an installer of sorts to copy the files in as Windows 10 has locked down access to the System32 and SYSWOW64 directories to "Trusted Installer" being the only user that can have unfettered access to those folders. As I only had 40 machines to fix, I had to do it manually, but an easier process would have been better. If anyone wants to try it as well, let me know how it goes.

We were having exactly the same problem with Windows 10 1709.

Can confirm the steps given from snoelwest does provide a 'fix' & I can now use both monitors for RemoteApp.

I have an update for this topic. The new 1803 build for Windows 10 has new RDP executable versions, which are 10.0.17134.1. These versions are also as broken as the ones from the 1703 build of Windows 10. I could not create an MSI fix for the issue, but I so have a powershell script capable of taking ownership and copying in the old files. I thought MS would fix the issue with the new version, but I guess not....

Snoelwest would you mind sharing your script? Also, do you have MSTSC files from earlier versions? I have hundreds of workstations affected by this.

The fix: Edit the RDP file in notepad, add the line below to the file and save it. If there's already a line for "use multimon", change the value to 1. Note the user's RDP session will have to be logged off form the server for the change to take effect.

use multimon:i:1

I have created the script as I mentioned earlier in the post. This is a pretty basic Powershell script to take ownership. For the script I created a Temp folder in the root of C: and then put the contents of the 7-zip file in that location. This zip contains the Set-Owner PowerShell function, as well as the 32 and 64-bit rdp files in their respective folders. For this script, it sets the local user "User" (which is an administrtator) as the owner and then gives that user permissions to the file to be able to make the copy. For my network I changed the User value to "mydomain.local\username" and I created a network share, where the script will pull the files from. The link below contains the files necessary. Mt PowerShell skills are minimal at best, so I had to open the PowerShell ISE as Administrator, then Set-ExecutionPolicy unrestricted before running the mstsc.ps1 script. Not as streamlined as I would have liked, but works fine for me. I may improve it in the future. Windows lockdown of the C:\Windows\System32 and SysWOW64 directories made making an MSI or other executable rather difficult and this was the easiest for me. Good luck everyone!

https://westcpa.citrixdata.com/d-s6592f923fb64d7ea

Can't use that option with Remote Desktop Session host server. I've triedspan monitors:i:1 in the RDP settings on the server, but that didn't help either

@ryansenio, did you try "use multimon:i:1" in the client's RDP file?

This is a remote desktop session host, users run apps via a website over RDP. All the RDP settings for these apps are held within the sever. This isn't a valid setting and won't let you save the modified RDP settings

I can also confirm that another client of mine that uses a remote app via a RDP connection WITH THE OPTION use multimon:i:1 still has the issue. So far the only fix has been to replace the files as per the earlier post.

It appears that theKB4340917 released by Microsoft on 7-24-2018 resolves the distortion in remote app. We have tested it with the 1803 build of Windows 10 and it is working without having to do the RDP swap script. Link to the update listed below.

https://support.microsoft.com/en-us/help/4340917/windows-10-update-kb4340917