Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. RemoteApp window is too large or too small when you use RDP to run a RemoteApp application in Windows Server 2012 R2

RemoteApp window is too large or too small when you use RDP to run a RemoteApp application in Windows Server 2012 R2

View products that this article applies to.

This article describes an issue that occurs when you use RDP to run a RemoteApp application in Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite. Additional steps for configuration are required to enable this hotfix after the installation.

↑ Back to the top

Symptoms

This issue occurs because the Dynamic dots per inch (DPI) sync setting for the remote desktop is not configurable. The Dynamic DPI sync feature automatically determines the DPI from the client side, and it ignores any server setting. Therefore, when the DPI of the client is much larger than the DPI of the server, this issue occurs. 

Note RDP represents Remote Desktop Protocol.

↑ Back to the top

Resolution

To disable the feature, we have released a hotfix for Windows Server 2012 R2.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this update, you must have update 2919355 installed in Windows Server 2012 R2.

Registry information

To enable this hotfix, follow these steps:

Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
  1. In Registry Editor, locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations
  2. Right-click WinStations, click New, and then click DWORD (32-bit) Value.
  3. Name the new registry entry as IgnoreClientDesktopScaleFactor.
  4. Double-click the IgnoreClientDesktopScaleFactor registry entry.
  5. In the Edit DWORD Value dialog box, type 1 in the Value data field, and then click OK.
  6. Exit Registry Editor.
Notes 

  • To enable the Dynamic DPI sync feature, set the IgnoreClientDesktopScaleFactor registry entry value to 0, or delete the registry entry.
  • You have to restart the server after the registry is changed.

Restart requirement

You may have to restart the computer after you install this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Rdpcorets.dll6.3.9600.176223,547,64819-Dec-201400:50x64
Rdpudd.dll6.3.9600.17415131,58429-Oct-201402:48x64
Rdpvideominiport.sys6.3.9600.1741527,45629-Oct-201403:56x64
Rfxvmt.dll6.3.9600.1741540,44829-Oct-201402:37x64

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_7f31c3c950eaadb112a2991c886356f1_31bf3856ad364e35_6.3.9600.17622_none_a985a9fcee521c14.manifest
File versionNot applicable
File size729
Date (UTC)29-Dec-2014
Time (UTC)23:31
PlatformNot applicable
File nameAmd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.3.9600.17622_none_208b588cdb9769c7.manifest
File versionNot applicable
File size13,555
Date (UTC)29-Dec-2014
Time (UTC)23:31
PlatformNot applicable

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 3026738
Revision : 1
Created on : 1/7/2017
Published on : 3/10/2015
Exists online : False
Views : 224