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.

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 name

File size

Date

Time

Path

Tcpv.lib

4,959,882

24-Nov-2015

12:25

Public\Common\Oak\Lib\X86\Checked

Tcpv.lib

4,731,982

24-Nov-2015

12:25

Public\Common\Oak\Lib\X86\Retail

Tcpv.lib

4,421,626

24-Nov-2015

12:24

Public\Common\Oak\Lib\X86\Debug

Tcpv.lib

4,719,978

24-Nov-2015

12:25

Public\Common\Oak\Lib\Armv7\Checked

Tcpv.lib

4,448,450

24-Nov-2015

12:25

Public\Common\Oak\Lib\Armv7\Retail

Tcpv.lib

5,353,946

24-Nov-2015

12:24

Public\Common\Oak\Lib\Armv7\Debug

Common.reg

552,278

24-Nov-2015

12:16

Public\Common\Oak\Files

Tcpipreg.map

84,615

24-Nov-2015

12:25

Public\Common\Oak\Target\X86\Checked

Tcpipreg.dll

86,016

24-Nov-2015

12:25

Public\Common\Oak\Target\X86\Checked

Tcpipreg.rel

56,105

24-Nov-2015

12:25

Public\Common\Oak\Target\X86\Checked

Tcpipreg.map

48,825

24-Nov-2015

12:25

Public\Common\Oak\Target\X86\Retail

Tcpipreg.dll

40,960

24-Nov-2015

12:25

Public\Common\Oak\Target\X86\Retail

Tcpipreg.rel

20,435

24-Nov-2015

12:25

Public\Common\Oak\Target\X86\Retail

Tcpipreg.map

85,638

24-Nov-2015

12:24

Public\Common\Oak\Target\X86\Debug

Tcpipreg.dll

90,112

24-Nov-2015

12:24

Public\Common\Oak\Target\X86\Debug

Tcpipreg.rel

40,010

24-Nov-2015

12:24

Public\Common\Oak\Target\X86\Debug

Tcpipreg.map

163,737

24-Nov-2015

12:26

Public\Common\Oak\Target\Armv7\Checked

Tcpipreg.dll

81,920

24-Nov-2015

12:26

Public\Common\Oak\Target\Armv7\Checked

Tcpipreg.rel

25,365

24-Nov-2015

12:26

Public\Common\Oak\Target\Armv7\Checked

Tcpipreg.map

84,352

24-Nov-2015

12:25

Public\Common\Oak\Target\Armv7\Retail

Tcpipreg.dll

40,960

24-Nov-2015

12:25

Public\Common\Oak\Target\Armv7\Retail

Tcpipreg.rel

13,794

24-Nov-2015

12:25

Public\Common\Oak\Target\Armv7\Retail

Tcpipreg.map

188,202

24-Nov-2015

12:24

Public\Common\Oak\Target\Armv7\Debug

Tcpipreg.dll

90,112

24-Nov-2015

12:24

Public\Common\Oak\Target\Armv7\Debug

Tcpipreg.rel

24,843

24-Nov-2015

12:24

Public\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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×