Windows 11 Remote Desktop Client window isn't showing entire remote screen

Question

Windows 11 Remote Desktop Client window isn't showing entire remote screen

David Dos 0

I recently upgraded from Windows 10 to Windows 11, and noticed that mstsc now has a strange (and slightly annoying) behavior that did not happen under Windows 10. When I connect to a remote computer, and specify the resolution on the Display tab, the resulting Remote Desktop "window" isn't the full size of the remote screen - I have to grab a corner of the window and resize it to see the entire remote screen. The "screen" isn't shrunk or scaled or anything, it's just that the window is smaller than the "screen" (and shows scroll bars along the side and bottom). Does anyone know of a way to "fix" this so the client will make the window the size of the remote screen when it connects? It's not a show stopper, but after a couple of months of putting up with it, I wondered if it can be fixed.

3 answers

Your answer

Answer 1

VPHAN 25,000 Independent Advisor

Hello again David Dos,

How is your issue going? Just following up. If you have solved it successfully, please consider accepting the answer, as it helps others sharing the same problem benefit too. Thank you :)

VP

Answer 2

VPHAN 25,000 Independent Advisor

Hello again David Dos,

Thanks to your data, I've identified the root cause, and it's is not a handshake failure, but a mathematical constraint imposed by your display settings.

Your local monitor resolution is 2560x1440 with 125% scaling. In Windows, this scaling factor reduces your effective "logical" screen height to 1152 pixels (1440 divided by 1.25). Since you are explicitly requesting a remote session height of 1200 pixels, the window physically cannot fit within your logical desktop work area (1152 pixels), causing the Windows 11 Desktop Window Manager to constrain the window size and enforce scrollbars. To resolve this and achieve a 1:1 pixel rendering at 1900x1200, you must set your local display scaling to 100% to regain the full 1440 vertical logical pixels. Crucially, after changing the scaling to 100%, you must sign out of Windows and sign back in to force the mstsc.exe process to recognize the new DPI context; simply changing the setting without signing out will often retain the old geometry constraints, which explains why your previous attempt failed.

If the answer helps you get more insight into the issue, please consider accepting it. Thank you.

VP

David Dos 0 Reputation points

2026-02-13T14:36:34.05+00:00

I'm not entirely disputing what you are saying, however, I can manually grab one of the window-resizing handles on the Remote Desktop client window and resize it to show the full 1900x1200 remote screen image with no problems. All I'm looking for is a way to tell Remote Desktop to start out with the window already sized to show the entire 1900x1200 image instead of me having to manually resize the window each time. This wasn't an issue in Win10 - in Win10 the window always opened to show the entire remote screen image.
VPHAN 25,000 Reputation points Independent Advisor

2026-02-13T14:45:31.9066667+00:00

Could you confirm if this happens on a single primary monitor or across a multi-monitor setup with mixed DPI scales? The issue probably stems from how the Windows 11 Desktop Window Manager handles initial bounding box calculations for legacy applications compared to the Windows 10 DWM. When mstsc.exe requests a 1900x1200 client area at 125% DPI, the application's initial launch calculation includes the updated Windows 11 title bar thickness and the invisible snap-layout borders. This combined vertical height momentarily exceeds your logical workspace of 1152 pixels during the execution phase. Consequently, DWM forces a fallback state to prevent the title bar from rendering off-screen, constraining the outer window shell and injecting scrollbars. Your manual resizing simply sends a subsequent WM_SIZE message to the application thread, which successfully bypasses this initial launch constraint.

I must confirm that this is a known architectural behavior within the legacy Windows 11 mstsc.exe client that Microsoft has not yet officially patched to replicate the seamless Windows 10 experience. You will need to wait for an official fix applied directly to the legacy client executable for the default behavior to change. In the meantime, you should avoid continuously modifying the winposstr registry keys, as the DWM will persistently overwrite them during its DPI fallback routine. The most robust, best-practice solution is to right-click your saved .rdp file, open it in Notepad, and append the exact string smart sizing:i:1 to a new line. This official configuration property forces the remote session to dynamically scale and fit within whatever initial dimensions the DWM dictates, eliminating the scrollbars immediately upon launch. Alternatively, transitioning your remote management workflow to the modern Windows App available via the Microsoft Store is highly recommended by Microsoft, as it utilizes modern API hooks for dynamic DPI scaling and entirely avoids the legacy window geometry cache issues inherent to the older executable.

I hope you've found something useful in the answer.

VP

Answer 3

Hello David Dos,

The root cause is likely a High DPI scaling handshake failure between the legacy RDP client and the Windows 11 Desktop Window Manager.

To provide the precise remediation, I need you to confirm your local display's scaling factor (e.g., 125%, 150%) and the specific resolution you are attempting to force, as non-standard integer scaling often triggers this frame misalignment.

The most reliable, non-destructive fix involves purging the corrupted window geometry cache that persists from your previous OS installation. While deleting Default.rdp helps, you must also clear the binary cache in the Registry to force a complete reset of the window chrome. Open regedit.exe, navigate to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers, and delete the subkey matching the IP address or hostname of your remote connection. This wipes the legacy winposstr values and forces the RDP client to renegotiate the window border padding with the Windows 11 DWM upon the next launch.

I hope you've found something useful in the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

David Dos 0 Reputation points

2026-02-12T19:42:44.32+00:00

Thanks for the pointers, VP. I'm playing around with the winposstr values to see if I can jiggle it into working. So far not much luck - it will honor what I put in for the Right and Top values, but no matter what I put in for Bottom and Right, it always starts the windows size at 1584x832 instead of 1900x1200 (the resolution I set for the connection), and saves those dimensions back to the default.rdp file when I exit.

My local monitor is 2560x1440, so it's not like there isn't enough screen space to show it at 1900x1200. However, Windows is set to scale my display/monitor to 125%, so maybe that's somehow causing it. I've tried setting the Windows scaling down to 100% but that didn't make any difference.

So thanks again for pointing me in the right direction. If I figure out a good "solution", I'll try to update this question.

Share via

Windows 11 Remote Desktop Client window isn't showing entire remote screen

3 answers

Your answer