I know that this is an old topic, but one that has plagued me since switching to Windows 10, and I just solved it last night. So I'm answering this to possibly help other folks.
First, my situation. I manage about 16 servers from my home office. I have created saved RDP connections for each server to my desktop. Each day, I log onto each server using these connections to check logs, hardware status, etc. I do them all at once, so at least once a day, I have 16 RDP windows open at once. The constant downsizing, and snapping to the screen edge, was driving me insane!
Here is what I did to fix it...
By right-clicking each saved RDP connection, and selecting 'open with' and then choosing Notepad, you can get to a plain text file that defines the RDP connection (as opposed to the typical GUI RDP properties panel). On each of my saved connections, I changed the following 4 parameters: screen mode id, desktopwidth, desktopheight and winposstr! Here is what they look like on one of my typical saved RDP connections:
screen mode id:i:1
desktopwidth:i:1280
desktopheight:i:1024
winposstr:s:0,3,1575,160,2900,1230
Screen mode id must be set to 1. That makes the remote session appear in a window.
Desktop width and height are self explanatory...but they can be anything so long as they're smaller than the screen you're viewing them on.
Winposstr is the important one. When you open your saved RDP connection file, the fifth and sixth values of this parameter will be much smaller in comparison to the third and fourth parameters than they are in my example. You have to edit those last two values...make them bigger! To get your RDP window to open full size, you have to add your desired vertical and horizontal resolution (plus a bit extra) to the third and fourth numbers respectively. So, 1575+1280=2855
. If you put that number in for the fifth value, exactly, you'll still get scroll bars. So in this case on my system, I put 2900. Likewise, 160+1024=1184. 1200 still gave me scroll bars, so I tried 1230, and it worked.
I haven't taken the time yet to figure out exactly what the third and fourth numbers represent. It's obvious they're somehow defining the position of the window on my screen, but I just haven't figured out that exact relationship. And those numbers will probably be different for you...when you save your own RDP connection file, they'll probably vary because you have a different setup than I do. But the point is, you have to add the horizontal and vertical resolutions of your desired RDP window to the third and fourth number, whatever they are, PLUS a bit extra, and then replace the fifth and sixth number with the results you get!
Once you've made the change, save the file, and close it. Then when you double click that RDP connection, it should open full size, and be able to be dragged to whatever position you want, without automatically downsizing!!!!
On my system, the upper left corner of the RDP session defined by the parameters above will be 0 pixels down from the top of my screen, and 3 pixels from the left edge. You can change the initial position by editing these values...for example, 10,10 would put it 10 pixels down and ten from the left. But if you add to these values, you ALSO have to add to the 5th and 6th values as well. Like I said, I haven't figured out the exact relationship yet...just know that if you change these, you may have to increase the 5th and 6th values as well to avoid scroll bars.
Finally, on my system, I have the 'Prevent Windows from being Automatically Arranged when moved to the edge of the screen' parameter UNchecked (this is in the 'make mouse easier to use' section of the Ease of Access Center).
I seem to be able to drag fixed-size windows without a problem on my Windows 10 machine. Are you using a single monitor per-chance? Because I am using multiples. – Arthur Kay – 2015-08-10T17:39:42.133
This is a triple monitor setup arranged horizontally (as it was under Windows 8.1). I'm welcome to suggestions on stuff to try. Be aware, that fixed-sized issues aren't the issue, it's specifically an issue with windows that are maximized. – psouza4 – 2015-08-10T17:45:12.480
Just to chime in. Windows 10 maximizing RDP to its restricted size I am able to move it around. – Unfundednut – 2015-08-12T17:19:29.370
This is a clean Windows 10 install (not an upgrade) from a freshly-formatted drive with mostly default settings and nVidia display drivers via GeForce experience using default settings. If you can suggest a setting I can adjust that will fix this, please provide an answer so I can verify and award the bounty. – psouza4 – 2015-08-12T17:24:50.553
Does it matter whether or not Tablet Mode is enabled (if applicable)? – GuitarPicker – 2015-08-17T20:00:52.663
I haven't enabled (or looked for to disable) tablet mode. This occurs on both my desktop PC with a fresh install of Windows 10 Pro x64 as described above (tri-monitors) as well as a Windows 7 Home x64 to Windows 10 Home x64 upgrade on my laptop (obviously single monitor). As of yet, I still have no idea how to work around this behavior change in Windows 10. – psouza4 – 2015-08-17T21:16:48.597
1FYI I created a .NET Windows Forms Application with
MaximizedBounds = new Rectangle(500,500, 500, 500); WindowState = FormWindowState.Maximized;
and I am able to drag it from maximized mode. The window immediately gets reduced to normal and moves where I want it to. (.NET 4.6) – Mik – 2015-08-18T07:31:09.270Mik, that's not what we're after here, unfortunately. Yes, with AeroSnap enabled, you can drag maximized or pseudo-maximized windows around and they will de-maximize. In Windows 8.1 and 7, I could drag around these windows without that undesired behavior. Turning off AeroSnap (as I did in 8.1) should still allow me to drag a maximized window, but now in Windows 10 I can't on any system, without AeroSnap and even then, they drop out of their maximized state. Thank you for your comment, though, and let me know if you come up with any other ideas. – psouza4 – 2015-08-18T18:01:45.750
Clearly you haven't read through the comment thread. This is neither desired nor original behavior in Windows 7, 8, nor 8.1 and was changed with Windows 10. The pop-down behavior you experienced are likely from using different Aero settings than I did, however there are no Aero settings that restore the desired behavior in 10. I'm looking for (a) data on a reason for the change and (b) any work-around, including the use of third-party software to restore the desired behavior. – psouza4 – 2015-09-20T19:40:00.140