Microsoft KB Archive Search

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.

  1. Home
  2. FIX: Invalid event handle error in Windows Embedded Compact 2013

FIX: Invalid event handle error in Windows Embedded Compact 2013

View products that this article applies to.

Introduction

This article describes an issue that generates an invalid event handle error 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.

↑ Back to the top

Symptoms

Consider the following scenario:
  • You open a socket from a kernel driver and use an asynchronous IO on the socket in Windows Embedded Compact 2013.
  • You run the WSAEventSelect function together with the FD_CLOSE flag, and then you use the CloseSocket function to close the socket.
  • You call the WaitForSingleObject function that uses the same event handles that are used for the WSAEventSelect function.

In this scenario, the WaitForSingleObject function returns a WAIT_FAILED response. After the call to the CloseSocket function, the WSAEnumNetworkEvents and WSAWaitForMultipleEvents functions fail with a WSA_INVALID_HANDLE error.

Note The nonblocking CloseSocket function starts a graceful socket closure. This process may involve some data exchange. The calling driver must be able to use the WSAWaitForMultipleEvents and WSAEnumNetworkEvents functions in order to wait for a graceful socket closure.

↑ Back to the top

Software update information

Download information

Windows Embedded Compact 2013 Monthly Update (April 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 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.

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
Afd.exp97205-May-201513:25Public\Common\Oak\Lib\X86\Checked
Afd.lib2,02605-May-201513:25Public\Common\Oak\Lib\X86\Checked
Afd.exp97105-May-201513:24Public\Common\Oak\Lib\X86\Retail
Afd.lib2,02605-May-201513:24Public\Common\Oak\Lib\X86\Retail
Afd.exp97005-May-201513:24Public\Common\Oak\Lib\X86\Debug
Afd.lib2,02605-May-201513:24Public\Common\Oak\Lib\X86\Debug
Afd.exp97805-May-201513:25Public\Common\Oak\Lib\Armv7\Checked
Afd.lib2,02205-May-201513:25Public\Common\Oak\Lib\Armv7\Checked
Afd.exp97305-May-201513:25Public\Common\Oak\Lib\Armv7\Retail
Afd.lib2,02205-May-201513:25Public\Common\Oak\Lib\Armv7\Retail
Afd.exp97205-May-201513:24Public\Common\Oak\Lib\Armv7\Debug
Afd.lib2,02205-May-201513:24Public\Common\Oak\Lib\Armv7\Debug
Afd.rel139,91505-May-201513:25Public\Common\Oak\Target\X86\Checked
Afd.dll229,37605-May-201513:25Public\Common\Oak\Target\X86\Checked
Afd.map251,41905-May-201513:25Public\Common\Oak\Target\X86\Checked
Afd.rel42,01105-May-201513:25Public\Common\Oak\Target\X86\Retail
Afd.dll122,88005-May-201513:25Public\Common\Oak\Target\X86\Retail
Afd.map123,98505-May-201513:25Public\Common\Oak\Target\X86\Retail
Afd.rel139,59605-May-201513:24Public\Common\Oak\Target\X86\Debug
Afd.dll315,39205-May-201513:24Public\Common\Oak\Target\X86\Debug
Afd.map255,54305-May-201513:24Public\Common\Oak\Target\X86\Debug
Afd.rel68,25605-May-201513:25Public\Common\Oak\Target\Armv7\Checked
Afd.dll212,99205-May-201513:25Public\Common\Oak\Target\Armv7\Checked
Afd.map514,89605-May-201513:25Public\Common\Oak\Target\Armv7\Checked
Afd.rel23,74105-May-201513:25Public\Common\Oak\Target\Armv7\Retail
Afd.dll110,59205-May-201513:25Public\Common\Oak\Target\Armv7\Retail
Afd.map225,04405-May-201513:25Public\Common\Oak\Target\Armv7\Retail
Afd.rel67,67605-May-201513:24Public\Common\Oak\Target\Armv7\Debug
Afd.dll286,72005-May-201513:24Public\Common\Oak\Target\Armv7\Debug
Afd.map627,03105-May-201513:24Public\Common\Oak\Target\Armv7\Debug

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbfix, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3062879
Revision : 1
Created on : 1/7/2017
Published on : 5/21/2015
Exists online : False
Views : 184