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.
View products that this article applies to.
This article describes an issue that causes reconnection to the same RAS (PPP) access point to fail in Windows Embedded Compact 2013. An update is available to resolve this issue.
Before you install this update, all previously issued updates for this product must be installed.
Assume that you have a device that is running Windows Embedded Compact 2013 that becomes disconnected from a RAS (PPP) access point. When the device tries to reconnect to that same access point, the reconnection may be unsuccessful when the server assigns the same IP address to the connection.
Windows Embedded Compact 2013 Monthly Update (July 2017) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.
This update is supported only if all previously issued updates for this product have also been installed.
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
You do not have to restart the computer after you apply this software update.
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.
| File name | File size | Date | Time | Path |
|---|---|---|---|---|
| Tcpipreg.map | 86,129 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\X86\Checked |
| Tcpipreg.dll | 86,016 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\X86\Checked |
| Tcpipreg.rel | 54,307 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\X86\Checked |
| Tcpipreg.map | 49,683 | 19-Jul-2017 | 15:16 | Public\Common\Oak\Target\X86\Retail |
| Tcpipreg.dll | 40,960 | 19-Jul-2017 | 15:16 | Public\Common\Oak\Target\X86\Retail |
| Tcpipreg.rel | 20,667 | 19-Jul-2017 | 15:16 | Public\Common\Oak\Target\X86\Retail |
| Tcpipreg.map | 87,154 | 19-Jul-2017 | 15:14 | Public\Common\Oak\Target\X86\Debug |
| Tcpipreg.dll | 90,112 | 19-Jul-2017 | 15:14 | Public\Common\Oak\Target\X86\Debug |
| Tcpipreg.rel | 40,242 | 19-Jul-2017 | 15:14 | Public\Common\Oak\Target\X86\Debug |
| Tcpipreg.map | 165,687 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\Armv7\Checked |
| Tcpipreg.dll | 77,824 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\Armv7\Checked |
| Tcpipreg.rel | 25,510 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\Armv7\Checked |
| Tcpipreg.map | 85,686 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\Armv7\Retail |
| Tcpipreg.dll | 40,960 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\Armv7\Retail |
| Tcpipreg.rel | 13,881 | 19-Jul-2017 | 15:15 | Public\Common\Oak\Target\Armv7\Retail |
| Tcpipreg.map | 190,233 | 19-Jul-2017 | 15:14 | Public\Common\Oak\Target\Armv7\Debug |
| Tcpipreg.dll | 90,112 | 19-Jul-2017 | 15:14 | Public\Common\Oak\Target\Armv7\Debug |
| Tcpipreg.rel | 25,017 | 19-Jul-2017 | 15:14 | Public\Common\Oak\Target\Armv7\Debug |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.
Keywords: kbfix, kbsurveynew, kbExpertiseAdvanced, ATdownload, kb