Surface Pro 4 (Windows 10) - Remote desktop, other programs appear too small

I am setting up my SP4 (love it) and am trying to connect via remote desktop to my office.  I have connected but everything is too small to see.  The wallpaper appears right but the icons and all programs are almost illegibly small.

I'm sure this has been answered already but I haven't found it... any help would be apprecited

 

Question Info


Last updated July 18, 2019 Views 55,144 Applies to:
Answer
Answer

Here is what I did to solve the issue.  It also works with older apps that don't handle high dpi scaling well.

First one must tell Windows to look for a manifest file for an application by default – a registry entry. 

Next is to provide a manifest file for a given application – the executable file name followed by .manifest.

Open regedit and navigate to the registry key:

HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide

Right-click, select NEW > DWORD (32 bit) Value

Type PreferExternalManifest, and then press ENTER.

Right-click PreferExternalManifest, and then click Modify.

Enter Value Data 1 and select Decimal.

Click OK. Exit Registry Editor.

The RDP app is %windir%\System32\mstsc.exe so the manifest file is mstsc.exe.manifest.

I can't attach the manifest file so here is the contents:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">

<dependency>
  <dependentAssembly>
    <assemblyIdentity
      type="win32"
      name="Microsoft.Windows.Common-Controls"
      version="6.0.0.0" processorArchitecture="*"
      publicKeyToken="6595b64144ccf1df"
      language="*">
    </assemblyIdentity>
  </dependentAssembly>
</dependency>

<dependency>
  <dependentAssembly>
    <assemblyIdentity
      type="win32"
      name="Microsoft.VC90.CRT"
      version="9.0.21022.8"
      processorArchitecture="amd64"
      publicKeyToken="1fc8b3b9a1e18e3b">
    </assemblyIdentity>
  </dependentAssembly>
</dependency>

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
  <security>
    <requestedPrivileges>
      <requestedExecutionLevel
        level="asInvoker"
        uiAccess="false"/>
    </requestedPrivileges>
  </security>
</trustInfo>

<asmv3:application>
  <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
    <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
  </asmv3:windowsSettings>
</asmv3:application>

</assembly>

Copy the above into notepad and save the file with the appropriate name to the same folder as the executable.

280 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Answer
Answer
I have experienced the same issue, even with RD Connection Manager. Oddly enough, we have discovered that the screens scale properly when using the application, RD Tabs.

5 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.