FIX: You cannot start an application on a remote computer when you use Remote Desktop Protocol (RDP) on a Windows Embedded Compact 7 touch screen device

Article translations Article translations
Article ID: 2811886 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You run a Windows Embedded Compact 7-based image on a touch screen device.
  • You use Remote Desktop Protocol (RDP) to connect the device to a remote computer.
  • You double-tap the icon of an application on the remote computer in the RDP session.
In this scenario, the application does not start.

Cause

This issue occurs because consecutive taps are not recognized as double-taps or double-clicks by the remote computer. Specifically, the tap coordinates that are sent from the Windows Embedded Compact 7-based RDP client are not close enough to qualify as double-taps or double-clicks.

Note This issue occurs almost exclusively on touch screen devices on which the precision of touch is less accurate.

Resolution

To resolve this issue, apply the following update. 

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

By default, this update is disabled after you apply it. To enable the update, set the DWORD value of the EnableDoubleClickDetect registry entry to 1. By default, the EnableDoubleClickDetect DWORD value does not exist, and you must create it in the following registry subkey: 
HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client

This update uses the values of the DblTapDist and DblTapTime settings. These values specify the time and space threshold settings that define consecutive taps or clicks as double-taps or double-clicks. The default value for the DblTapDist setting is 20 pixels, and the default value for the DblTapTime setting is 600 milliseconds. You can optimize these settings for platforms that require more accurate tap or click precision. To optimize these settings, change the DWORD value of the following two registry entries:
  • HKEY_CURRENT_USER\ControlPanel\Pen\dblTapDist
  • HKEY_CURRENT_USER\ControlPanel\Pen\dblTapTime



Note By default, these registry entries are not present, and you must create them.

Known issue

After you enable this update, consecutive taps or clicks still do not work as intended in an application if the following conditions are true:
  • The application is running on the RDP server.
  • You want to perform consecutive taps or clicks that are within the values of the DblTapDist andDblTapTime settings in the application.
  • You do not want the consecutive taps or clicks to be considered as a double-click.
For example, you want to click two times (such as when you draw two dots in a Microsoft Paint application). The distance between these clicks is less than the value of the DblTapDist setting, and the time between the clicks is less than the value of the DblTapTime setting. In this case, when the EnableDoubleClickDetect value is set, the two clicks are considered as a double-click (or a drag motion in the Microsoft Paint application), instead of the two single clicks that you intended.

Software update information

Download information

The Windows Embedded Compact 7 Monthly Update (February 2013) is now available from Microsoft. To download this Windows Embedded Compact 7 Monthly Update, go to the following Microsoft Download Center website:
Windows Embedded Compact 7 updates
The kind of processor that each file applies to is visible in the name of each file in the "File information" section.

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

Restart requirement

After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
  • On the Build menu, click Clean Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any other updates.

File information

Collapse this imageExpand this image
assets folding start collapsed
The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Files that are included in this hotfix package
Collapse this tableExpand this table
File nameFile sizeDateTimePath
Tscaxctrl.lib33,719,55013-Feb-201322:35Public\Rdp\Oak\Lib\Armv5\Checked
Tscaxctrl.lib34,558,60213-Feb-201322:33Public\Rdp\Oak\Lib\Armv5\Debug
Tscaxctrl.lib25,346,98213-Feb-201322:32Public\Rdp\Oak\Lib\Armv5\Retail
Tscaxctrl.lib33,720,17013-Feb-201322:50Public\Rdp\Oak\Lib\Armv6\Checked
Tscaxctrl.lib34,552,97813-Feb-201322:49Public\Rdp\Oak\Lib\Armv6\Debug
Tscaxctrl.lib25,347,80213-Feb-201322:47Public\Rdp\Oak\Lib\Armv6\Retail
Tscaxctrl.lib33,609,32813-Feb-201323:06Public\Rdp\Oak\Lib\Armv7\Checked
Tscaxctrl.lib34,439,05213-Feb-201323:04Public\Rdp\Oak\Lib\Armv7\Debug
Tscaxctrl.lib25,273,01413-Feb-201323:03Public\Rdp\Oak\Lib\Armv7\Retail
Tscaxctrl.lib32,119,82813-Feb-201323:21Public\Rdp\Oak\Lib\Mipsii\Checked
Tscaxctrl.lib34,273,49413-Feb-201323:20Public\Rdp\Oak\Lib\Mipsii\Debug
Tscaxctrl.lib24,413,77613-Feb-201323:18Public\Rdp\Oak\Lib\Mipsii\Retail
Tscaxctrl.lib32,135,64213-Feb-201323:36Public\Rdp\Oak\Lib\Mipsii_fp\Checked
Tscaxctrl.lib34,288,88613-Feb-201323:35Public\Rdp\Oak\Lib\Mipsii_fp\Debug
Tscaxctrl.lib24,429,45213-Feb-201323:33Public\Rdp\Oak\Lib\Mipsii_fp\Retail
Tscaxctrl.lib30,053,25213-Feb-201323:51Public\Rdp\Oak\Lib\Sh4\Checked
Tscaxctrl.lib31,872,95213-Feb-201323:50Public\Rdp\Oak\Lib\Sh4\Debug
Tscaxctrl.lib23,203,52613-Feb-201323:48Public\Rdp\Oak\Lib\Sh4\Retail
Tscaxctrl.lib29,789,61214-Feb-201300:06Public\Rdp\Oak\Lib\X86\Checked
Tscaxctrl.lib29,706,69014-Feb-201300:04Public\Rdp\Oak\Lib\X86\Debug
Tscaxctrl.lib22,500,61414-Feb-201300:03Public\Rdp\Oak\Lib\X86\Retail
Collapse this imageExpand this image
assets folding end collapsed

Status

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

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2811886 - Last Review: March 11, 2013 - Revision: 1.0
Applies to
  • Windows Embedded Compact 7
Keywords: 
kbfix kbsurveynew kbexpertiseadvanced atdownload KB2811886

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com