This article describes an issue that occurs when you try to make a Profile Configuration File (PCF) connection in Windows Embedded Compact 2013. An update is available to fix this issue. Before you install this update, all previously issued updates for this product must be installed.
Symptoms
When you try to make a PCF connection on a Windows Embedded Compact 2013-based device, the rasdial command is called. The call is asynchronous, and it immediately returns a status message to indicate that the current connection is fine. But during the rasdial connection, the IP stack and functionality seem to be deadlocked.
Resolution
Download information
Windows Embedded Compact 2013 Monthly Update (August 2015) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.
More Information
Restart requirement
After you apply this update, you must do a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, select Clean Solution, and then select Build Solution.
-
On the Build menu, select Rebuild Solution.
You don't have to restart the computer after you apply this software update.
Update replacement information
This update doesn't 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 hotfix package
File name |
File size |
Date |
Time |
Path |
---|---|---|---|---|
Ip_intf.c |
44,020 |
02-Sep-2015 |
04:41 |
Private\Winceos\Comm\Ppp2\Ppp\App |
Ndisprot.c |
51,049 |
02-Sep-2015 |
04:41 |
Private\Winceos\Comm\Ppp2\Ppp\Pppndis |
Ppp2ndis.lib |
469,248 |
02-Sep-2015 |
04:49 |
Public\Common\Oak\Lib\X86\Checked |
Ppp2app.lib |
508,668 |
02-Sep-2015 |
04:49 |
Public\Common\Oak\Lib\X86\Checked |
Ppp2ndis.lib |
264,856 |
02-Sep-2015 |
04:50 |
Public\Common\Oak\Lib\X86\Retail |
Ppp2app.lib |
366,360 |
02-Sep-2015 |
04:50 |
Public\Common\Oak\Lib\X86\Retail |
Ppp2ndis.lib |
430,486 |
02-Sep-2015 |
04:49 |
Public\Common\Oak\Lib\X86\Debug |
Ppp2app.lib |
459,836 |
02-Sep-2015 |
04:49 |
Public\Common\Oak\Lib\X86\Debug |
Ppp2ndis.lib |
461,066 |
02-Sep-2015 |
04:50 |
Public\Common\Oak\Lib\Armv7\Checked |
Ppp2app.lib |
491,738 |
02-Sep-2015 |
04:50 |
Public\Common\Oak\Lib\Armv7\Checked |
Ppp2ndis.lib |
235,678 |
02-Sep-2015 |
04:50 |
Public\Common\Oak\Lib\Armv7\Retail |
Ppp2app.lib |
339,682 |
02-Sep-2015 |
04:50 |
Public\Common\Oak\Lib\Armv7\Retail |
Ppp2ndis.lib |
495,170 |
02-Sep-2015 |
04:49 |
Public\Common\Oak\Lib\Armv7\Debug |
Ppp2app.lib |
541,360 |
02-Sep-2015 |
04:49 |
Public\Common\Oak\Lib\Armv7\Debug |
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, see Description of the standard terminology that's used to describe Microsoft software updates.