I have a large app that we are delaying supporting dynamic DPI for. Currently, when we launch our app via RemoteApp (RDP to our Windows Server 2016 server) on a high DPI screen, the text and controls overlap.
As a work around for our customers with high DPI displays, we found the best solution is to set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\IgnoreClientDesktopScaleFactor to 1. This stops the RemoteApp from using DPI scaling and makes it look decent.
The problem is that the size of the window itself starts off super tiny.
If you change the scaling factor on the local PC and then change it back, it will automatically size the window back up to the correct scaling.
We would prefer to use this workaround instead of adding a mstsc manifest file to our customers' PC's, but we would need to know how to force the scaling to start off with the local PC's settings while still avoiding DPI scaling.
.exe
Properties the possible high DPI settings. Maybe some setting would behave better. But the basic problem is that mstc is not DPI-aware.