FIX: Update to support configuring TCP Receive Window Size and Window AutoTuning in Windows Embedded Compact 2013

Introduction
This article describes an update that lets you set the TCP Receive Window Size variable and the Window AutoTuning feature in Windows Embedded Compact 2013. Before you install this update, all previously issued updates for this product must be installed.
Symptoms
This update supports the configuration of the TCP Receive Window Size variable and the Window AutoTuning feature in Windows Embedded Compact 2013.
More information
After you apply this update, you'll notice that the following two DWORD registry values are added:
  • TcpAutoTuningLevel
  • TcpWindowSize

These DWORD values are added in the following registry location:

HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms


TcpAutoTuningLevel

The TcpAutoTuningLevel registry value configures the window scaling strategy. When this value is set to 0 (TcpAutoTunningOff), the Window scaling feature is disabled. This limits the maximum TCP receive window to 65,535 bytes. If you want the system to use a TCP Receive Window setting that's larger than 65,535 bytes, you should set this value to a value that's greater than 0. The default value is 3 (TcpAutoTuningNormal).
  • TcpAutoTuningOff = 0
  • TcpAutoTuningHighlyRestricted = 1
  • TcpAutoTuningRestricted = 2
  • TcpAutoTuningNormal = 3
  • TcpAutoTuningExperimental = 4


TcpWindowSize

The TcpWindowSize registry value specifies the initial TCP Receive Window size. Be aware that this size isn't the final receive window size. The final receive window size is calculated by considering other parameters such as network adapter link speed. The final size may be more than 10 times larger than the initial receive window size.
  • Valid values for this setting: 0x2000–0x3fffffff

Software update information

Download information

Windows Embedded Compact 2013 Monthly Update (November 2015) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.

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 run 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 don't have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any other updates.

File information

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 update package
File nameFile sizeDateTimePath
Tcpv.lib4,959,88224-Nov-201512:25Public\Common\Oak\Lib\X86\Checked
Tcpv.lib4,731,98224-Nov-201512:25Public\Common\Oak\Lib\X86\Retail
Tcpv.lib4,421,62624-Nov-201512:24Public\Common\Oak\Lib\X86\Debug
Tcpv.lib4,719,97824-Nov-201512:25Public\Common\Oak\Lib\Armv7\Checked
Tcpv.lib4,448,45024-Nov-201512:25Public\Common\Oak\Lib\Armv7\Retail
Tcpv.lib5,353,94624-Nov-201512:24Public\Common\Oak\Lib\Armv7\Debug
Common.reg552,27824-Nov-201512:16Public\Common\Oak\Files
Tcpipreg.map84,61524-Nov-201512:25Public\Common\Oak\Target\X86\Checked
Tcpipreg.dll86,01624-Nov-201512:25Public\Common\Oak\Target\X86\Checked
Tcpipreg.rel56,10524-Nov-201512:25Public\Common\Oak\Target\X86\Checked
Tcpipreg.map48,82524-Nov-201512:25Public\Common\Oak\Target\X86\Retail
Tcpipreg.dll40,96024-Nov-201512:25Public\Common\Oak\Target\X86\Retail
Tcpipreg.rel20,43524-Nov-201512:25Public\Common\Oak\Target\X86\Retail
Tcpipreg.map85,63824-Nov-201512:24Public\Common\Oak\Target\X86\Debug
Tcpipreg.dll90,11224-Nov-201512:24Public\Common\Oak\Target\X86\Debug
Tcpipreg.rel40,01024-Nov-201512:24Public\Common\Oak\Target\X86\Debug
Tcpipreg.map163,73724-Nov-201512:26Public\Common\Oak\Target\Armv7\Checked
Tcpipreg.dll81,92024-Nov-201512:26Public\Common\Oak\Target\Armv7\Checked
Tcpipreg.rel25,36524-Nov-201512:26Public\Common\Oak\Target\Armv7\Checked
Tcpipreg.map84,35224-Nov-201512:25Public\Common\Oak\Target\Armv7\Retail
Tcpipreg.dll40,96024-Nov-201512:25Public\Common\Oak\Target\Armv7\Retail
Tcpipreg.rel13,79424-Nov-201512:25Public\Common\Oak\Target\Armv7\Retail
Tcpipreg.map188,20224-Nov-201512:24Public\Common\Oak\Target\Armv7\Debug
Tcpipreg.dll90,11224-Nov-201512:24Public\Common\Oak\Target\Armv7\Debug
Tcpipreg.rel24,84324-Nov-201512:24Public\Common\Oak\Target\Armv7\Debug
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3082654 - Last Review: 12/15/2015 17:30:00 - Revision: 2.0

Windows Embedded Compact 2013

  • kbqfe kbsurveynew kbfix kbexpertiseadvanced atdownload KB3082654
Feedback