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

Anonymous
2015-10-27T02:45:39+00:00

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

Surface | Surface Pro | Display and screen

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2016-01-18T15:21:51+00:00

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.

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-12-01T19:48:15+00:00

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.

Was this answer helpful?

7 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Barb Bowman 80,810 Reputation points MVP Volunteer Moderator
2017-01-23T10:31:04+00:00

copy the following between the **** to notepad

********************************

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]

"PreferExternalManifest"=dword:00000001

********************************

save as preferextman.reg

then double click/tap to run and ack yes to the prompt.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2016-02-07T20:12:34+00:00

A manifest file will fix the issue in many, but not all, programs.

See this thread.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2016-01-18T19:13:32+00:00

I found another alternate solution.  Remote Desktop Connection Manager version 2.2 scales quite nicely.  Version 2.2 is no longer available from Microsoft.  The version available from Microsoft, 2.7 does not work and had the same scaling limitations as the latest RDP versions.  Don't waste your time with 2.7 .

I was able to find a 2.2 download by searching via google.  I got mine at download.com

Remote Desktop Connection Manager 2.2

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2015-10-27T03:44:52+00:00

Hi Nate, it sounds like you are referring to remote PC's desktop and not that of your Surface Pro 4. Since the Surface Pro 4 has a very high resolution display, you may need to specify a lower resolution for your Windows 7 remote desktop to use instead of using that of your Surface Pro 4. You can do this in the Remote Desktop options by sliding the Display resolution lower and ideally to the same resolution you have it set to if you are actually sitting in front of it. If you are using the Modern Remote Desktop app, then if you put it in a windowed mode you can drag to scale and also right click the session to open a Zoom control to adjust sizing.

Depending on how things look, you may also need to adjust the "size of text, apps, other items" scaling found on the Surface Pro 4's Settings screen under Display.

Hope this helps,

Greg

Was this answer helpful?

0 comments No comments

134 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-08-12T16:40:18+00:00

    Hello,

    with the manifest file in the %windir%\System32, mstsc will not start.

     Why?

    Windows 10 1511 works perfect, but with Windows 10 anniversary update (1607). When you try to run mstsc.exe, RDP file or Remote WebApp. It just does nothing with the .manifest file in system32 folder. Once you remove the manifest file out of system32, everything works like normal.

    I have tested this on a Surface pro 3 1607 upgrade, a Surface pro 4 1607 upgrade, and a desktop with a clean fresh install of 1607. All suffer from the same issues when the manifest file is placed in the system32 folder. This issue occurs with or without adding the registry entry as well which is a puzzling to me since it should care if that file is there without the registry entry.  There is no error message displayed nor is there any error logged in the event log on any of the systems.

    Someone had said that it was most likely caused by the new version of mstsc.exe in 1607 and the file was built for the older version. The version of on Win8 and Win10 1511 are both different version and the file works with both so I don't think that is the issue. It looks like Microsoft did some changes to how mstsc.exe works in 1607 so I am playing around with it to see if I can figure out what has changed.

    Was this answer helpful?

    0 comments No comments