title: RDP / MSTSC Ignores highdpi manifest fix when launched from windows form application
body: <p>I'm using VS2017 and have made a very simple 'launcher' for various RDP settings files using a Windows Forms application. This just calls Process.Start with a direct link to a .rdp file, or alternatively just straight to mstsc.exe</p>
  
  <p>The application (and RDP sessions) displays and works correctly on standard PCs.  However I have run into a problem on high DPI devices such as Surface Books/pros. </p>
  
  <p>The RDP client not scaling correctly is a fairly well known issue, and we have fixed this problem using the manifest/reg change method.  This is confirmed working.  Double clicking a .rdp config file works correctly too.</p>
  
  <p>( <a href="https://www.blackforce.co.uk/2016/04/18/remote-desktop-rdp-resolution-on-a-surface-book" rel="nofollow noreferrer">https://www.blackforce.co.uk/2016/04/18/remote-desktop-rdp-resolution-on-a-surface-book</a> )</p>
  
  <p>My own application also displays correctly at the correct scale.  However, when I launch RDP using Process.Start, RDP client is scaled badly, as it always was before the manifest fix.  I've tried opening the client alone, and with a .rdp file and result is the same.  I open the same .rdp file manually, not via my app, and the client is scaled correctly.</p>
  
  <p>Can anyone replicate this, or advise why the mstsc manifest file is ignored when started this way? I've also tried the using ProcessStartInfo to set UseShellExecute but still the same result.</p>