Application can't receive data in the serialized order through a Bluetooth LE device in Windows 8.1

This article describes an issue that occurs when an application receives characteristic value changed events from Bluetooth low energy (Bluetooth LE) devices in Windows 8.1. A hotfix is available to resolve this issue. The hotfix has a prerequisite.
Cause
The issue occurs because a callback routine registered by the BluetoothGATTRegisterEvent function is called by multiple threads at the same time.

Hotfix information
Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows 8.1 and Windows RT 8.1RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Bluetoothapis.dll6.3.9600.1793179,87210-Jul-201516:52x86
Bthmigplugin.dll6.3.9600.1741580,89629-Oct-201401:33x86
Bthudtask.exe6.3.9600.1741535,84029-Oct-201401:32x86
Wshbth.dll6.3.9600.1741550,68829-Oct-201401:00x86
For all supported x64-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Bluetoothapis.dll6.3.9600.17931104,96010-Jul-201517:46x64
Bthmigplugin.dll6.3.9600.1741595,74429-Oct-201402:11x64
Bthudtask.exe6.3.9600.1741537,88829-Oct-201402:09x64
Wshbth.dll6.3.9600.1741563,48829-Oct-201401:21x64
Bluetoothapis.dll6.3.9600.1793179,87210-Jul-201516:52x86
Bthmigplugin.dll6.3.9600.1741580,89629-Oct-201401:33x86
Bthudtask.exe6.3.9600.1741535,84029-Oct-201401:32x86
Wshbth.dll6.3.9600.1741550,68829-Oct-201401:00x86
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Bluetoothapis.dll6.3.9600.1793571,68015-Jul-201501:45Not applicable
Bthmigplugin.dll6.3.9600.1638474,24022-Aug-201302:45Not applicable
Bthudtask.exe6.3.9600.1638436,86422-Aug-201302:44Not applicable
Wshbth.dll6.3.9600.1723844,03224-Jul-201408:04Not applicable

Additional file information

Additional file information for Windows 8.1
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_c671add4ca6f510bd729c926187abaca_31bf3856ad364e35_6.3.9600.17935_none_c2e645c0d7c11a70.manifest
File versionNot applicable
File size696
Date (UTC)15-Jul-2015
Time (UTC)13:59
PlatformNot applicable
File nameX86_microsoft-windows-bth-user_31bf3856ad364e35_6.3.9600.17935_none_f9f008f4f09e3ee5.manifest
File versionNot applicable
File size9,509
Date (UTC)15-Jul-2015
Time (UTC)14:02
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1
File propertyValue
File nameAmd64_256f9abce0f32956d8a80c27e7e0cef9_31bf3856ad364e35_6.3.9600.17935_none_5ddf740c067884cf.manifest
File versionNot applicable
File size700
Date (UTC)15-Jul-2015
Time (UTC)13:59
PlatformNot applicable
File nameAmd64_963f2998fae03e76fd39538538f9a33b_31bf3856ad364e35_6.3.9600.17935_none_a78a288c97725455.manifest
File versionNot applicable
File size700
Date (UTC)15-Jul-2015
Time (UTC)13:59
PlatformNot applicable
File nameAmd64_microsoft-windows-bth-user_31bf3856ad364e35_6.3.9600.17935_none_560ea478a8fbb01b.manifest
File versionNot applicable
File size9,515
Date (UTC)15-Jul-2015
Time (UTC)14:06
PlatformNot applicable
File nameWow64_microsoft-windows-bth-user_31bf3856ad364e35_6.3.9600.17935_none_60634ecadd5c7216.manifest
File versionNot applicable
File size7,262
Date (UTC)15-Jul-2015
Time (UTC)14:06
PlatformNot applicable
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_5cee3f35583878aef73f0119548516bd_31bf3856ad364e35_6.3.9600.17935_none_f38dd9e30ae1e800.manifest
File versionNot applicable
File size696
Date (UTC)15-Jul-2015
Time (UTC)13:59
PlatformNot applicable
File nameArm_microsoft-windows-bth-user_31bf3856ad364e35_6.3.9600.17935_none_f9f27b4cf09b5dab.manifest
File versionNot applicable
File size9,509
Date (UTC)15-Jul-2015
Time (UTC)13:59
PlatformNot applicable
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3067699 - Last Review: 08/18/2015 16:54:00 - Revision: 1.0

Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows RT 8.1

  • kbqfe kbsurveynew kbfix kbautohotfix kbhotfixserver kbexpertiseinter KB3067699
Feedback