This article describes an issue that occurs when you use the WSASend function on a Windows Embedded Compact 2013-based device. An update is available to resolve this issue. Before you install the update, all previously issued updates for this product must be installed.
Symptoms
When you use the WSASend function on a Windows Embedded Compact 2013-based device, an access violation occurs. This issue occurs when more than one WSABUF structures are sent. In the structures, there is a certain overlap between two buffers, and this causes an error in buffer copy calculations.
Resolution
Download information
Windows Embedded Compact 2013 Monthly Update (October 2014) 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 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.
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 |
|---|---|---|---|---|
|
Afd.lib |
2,026 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Lib\X86\Retail |
|
Afd.lib |
2,026 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Lib\X86\Debug |
|
Afd.lib |
2,026 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Lib\X86\Checked |
|
Afd.lib |
2,022 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Lib\Armv7\Retail |
|
Afd.lib |
2,022 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Lib\Armv7\Debug |
|
Afd.lib |
2,022 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Lib\Armv7\Checked |
|
Afd.dll |
122,880 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\X86\Retail |
|
Afd.map |
123,985 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\X86\Retail |
|
Afd.rel |
42,011 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\X86\Retail |
|
Afd.dll |
315,392 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Target\X86\Debug |
|
Afd.map |
255,309 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Target\X86\Debug |
|
Afd.rel |
139,451 |
17-Sep-2014 |
09:14 |
Public\Common\Oak\Target\X86\Debug |
|
Afd.dll |
229,376 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\X86\Checked |
|
Afd.map |
251,192 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\X86\Checked |
|
Afd.rel |
139,857 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\X86\Checked |
|
Afd.dll |
110,592 |
17-Sep-2014 |
09:16 |
Public\Common\Oak\Target\Armv7\Retail |
|
Afd.map |
225,044 |
17-Sep-2014 |
09:16 |
Public\Common\Oak\Target\Armv7\Retail |
|
Afd.rel |
23,741 |
17-Sep-2014 |
09:16 |
Public\Common\Oak\Target\Armv7\Retail |
|
Afd.dll |
286,720 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\Armv7\Debug |
|
Afd.map |
626,726 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\Armv7\Debug |
|
Afd.rel |
67,647 |
17-Sep-2014 |
09:15 |
Public\Common\Oak\Target\Armv7\Debug |
|
Afd.dll |
212,992 |
17-Sep-2014 |
09:16 |
Public\Common\Oak\Target\Armv7\Checked |
|
Afd.map |
514,589 |
17-Sep-2014 |
09:16 |
Public\Common\Oak\Target\Armv7\Checked |
|
Afd.rel |
68,227 |
17-Sep-2014 |
09:16 |
Public\Common\Oak\Target\Armv7\Checked |
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 is used to describe Microsoft software updates.
