-->
- Microsoft Bluetooth Stack Windows Xp Sp3
- Repair Microsoft Bluetooth Stack Windows 7
- Microsoft Bluetooth Stack Driver Download
The Bluetooth driver stack comprises the core portion of the support provided by Microsoft for the Bluetooth protocol. With this stack, Bluetooth-enabled devices can locate each other and establish connections. Across such connections, the devices can exchange data and interact with one another through various applications.
The following image shows the modules within the Bluetooth driver stack, along with possible custom user-mode and kernel-mode drivers not included in Windows Vista and later. These custom drivers are known as profile drivers.
- User-mode
- User-mode application- A user-mode application that accesses the Bluetooth driver stack through published APIs. For more information, see About Bluetooth in the Windows SDK documentation.Note User-mode applications should link against BthProps.lib, instead of IrProps.lib, in order to use APIs, such as BluetoothSetLocalServiceInfo.
- Examples of profile drivers
- WAP Kernel Mode Driver- The Wireless Application Protocol (WAP) component is an example of a profile driver that communicates between the Windows networking stack and BthPort, accessing the L2CAP interface and, optionally, the SDP interface contained in L2CAP. Other possible profiles include the Advanced Audio Distribution profile (A2DP), A/V Remote Control profile (AVRCP), Generic A/V Distribution profile (GAVDP), and Common ISDN Access (CIP) profile.
- Audio Kernel Mode Driver- An example of a profile driver that communicates between the Windows audio stack and BthPort, accessing the SCO interfaces contained in the latter. Possible profiles include the Hands Free profile (HFP), Headset profile (HSP), Cordless Telephony profile (CTP), and Intercom profile (ICP).Note This profile driver is included with Windows beginning with Windows 8.
- Bluetooth LE Heart Rate Monitor Profile- An example of a Bluetooth LE profile driver that communicates with the Bluetooth Low Energy (LE) API.
- Bluetooth driver stack components
- IrProps- A component that is used for backward compatibility for profile drivers that are created for the first version of the Bluetooth driver stack.NoteIrProps is provided only for backward compatibility. Use the BthProps component for new development.
- BthProps- A component that contains the implementation of the Bluetooth user interface along with implementation of the Bluetooth APIs that user-mode applications access. This component sends inquiries to BthServ through remote procedure calls (RPC). Additionally, BthProps performs pin exchanges with BthPort through private IOCTLs. Note that BthProps runs on any system with a Bluetooth-enabled radio.
- BthServ- A service that is responsible for caching and forwarding inquiry data to Bthport.
- BthCi- The Bluetooth class installer.
- WshBth- The Bluetooth Windows socket helper component. WshBth is called by the Windows sockets layer to perform socket operations. WshBth primarily calls into RfComm through the TDI interface. WshBth also calls into BthServ to perform remote device inquiries and into BthPort to perform local radio inquiries.
- FSquirt- A nonextensible Object Exchange (OBEX) component that allows users to send and receive files across an open Bluetooth connection. OBEX communicates with remote devices through RFCOMM that uses the WshBth component.
- BthPrint- A component that implements the Hardcopy Cable Replacement Profile (HCRP). This component allows the print system to send data to and receive data from Bluetooth-enabled printers. BthPrint communicates with the SDP interface in BthPort to query remote printers and the L2CAP interface in BthPort to send and receive data.
- HidBth- The component that implements the Human Interface Device (HID) profile. HidBth also communicates with the L2CAP and SDP interfaces in BthPort. HidBth connects to the HID stack much like USB HID module does.
- BthPan- The component that implements the Personal Area Network (PAN) profile, providing TCP connections across an open Bluetooth connection. In Windows Vista and Windows XP, BthPan only supports outgoing connections. BthPan is also a client of the BthPort component and uses both the L2CAP and SDP interfaces.
- RfComm- The component that implements the Bluetooth serial cable emulation protocol. RfComm also uses the L2CAP and SDP interfaces found in BthPort. The upper edge of RfComm exposes the TDI interface, allowing this component to appear to be a networking transport. This is how WshBth connects to Bluetooth to send and receive data from user-mode APIs.User-mode applications can access RfComm using the Winsock interfaces described in the Windows SDK.
- BthModem- The component that implements virtual COM ports and dial-up networking (DUN). BthModem directs all I/O and control operations to RfComm through a TDI interface. The upper edge of BthModem communicates with Serial.sys to give the appearance of being a wireless COM port.Note This component is not available in Windows RT.
- BthEnum- The Bluetooth bus driver. BthEnum communicates with the Plug and Play (PnP) manager to create and destroy device objects used to enable Bluetooth services. BthEnum creates a PDO for every service that a connected remote device supports. For example, when a user connects a Bluetooth-enabled mouse, Windows will discover that the mouse supports the Bluetooth HID service and creates a PDO for the HID service that causes the PnP manager to load HidBth.Note BthEnum will not create PDOs for services that appear in the UnsupportedServices registry key as specified in Bth.inf.
- BthLEEnum- The Bluetooth Low Energy (LE) bus driver. BthLEEnum implements the ATT protocol and the GATT profile. It is also responsible for creating PDOs to represent the remote devices and their primary services.
- BthPort- A minidriver loaded by the BthUsb miniport. BthPort provides four components:
- The HCI component communicates to the local Bluetooth-enabled radio through the Host Controller Interface (HCI) defined in the Bluetooth specification. Because all Bluetooth-enabled radios implement the HCI specification, BthPort is able to communicate with any Bluetooth-enabled radio, regardless of the manufacturer or model.
- The SCO component implements the Synchronous Connection-Oriented (SCO) protocol. This protocol supports creating point-to-point connections to a remote device. SCO clients communicate with the SCO interface by building and sending Bluetooth request blocks (BRBs).
- L2CAP implements the Bluetooth logical link control and adaptation protocol. This protocol supports creating a lossless channel to a remote device. L2CAP clients communicate with the L2CAP interface by building and sending Bluetooth request blocks (BRBs).
- SDP implements the Bluetooth Service Discovery Protocol.
- BthUsb.sys- The miniport that abstracts the bus interface from BthPort.
Microsoft Bluetooth Stack. Prior to Windows 8, the Microsoft Bluetooth Stack only supports external or integrated Bluetooth dongles attached through USB. It does not support Bluetooth radio connections over PCI, I²C, serial, PC Card or other interfaces. It also only supports a single Bluetooth radio. Download this app from Microsoft Store for Windows 10, Windows 8.1. See screenshots, read the latest customer reviews, and compare ratings for Bluetooth comm Pro. Turn off Bluetooth, wait a few seconds, then turn it back on. Remove the Bluetooth device, then add it again: Select the Start button, then select Settings Devices Bluetooth & other devices. Under Bluetooth, select the device you’re having problems connecting to, and then select Remove device Yes.
Hi, 1-Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers. 2- Click the Update button next to the flagged Bluetooth device to automatically download and install the correct version of its driver (you can do this with the FREE version). Bluetooth stack for opensolaris v.1.0 This is the bluetooth stack built for opensolaris completely in user space - operational only with usb dongles and capable of transferring files with other bluetooth devices ( mobile phones, pda etc ). Bluetooth Driver Installer v.1.0.0.31 Get Bluetooth to work with the Microsoft Bluetooth stack.
There are two installation types for Bluetooth profile drivers
- Client-side installation
- Server-side installation
Client-side installations are for remote devices where the remote device advertises its services and the computer connects to it. Examples include: mouse devices, keyboards, and printers.
Server-side installations are where the computer advertises services and remote devices can connect to the computer to use those services. For example, a vendor could author a server-side installation to enable a PDA to print to a printer attached to the computer.
These two installation types require different installation procedures.
Installing a Client-side Profile Driver
When a user wants to use a Bluetooth-enabled device, the user should bring the device within range of the computer and initiate a connection from the computer to the remote device. The following is the installation sequence for a client-side profile driver installation.
To Install a Client-side Profile Driver
- Launch Bluetooth Devices in Control Panel to find all devices within range of the computer.
- Select the device to pair with.
- Pair (or bond) the device with the local radio. This may or may not involve a PIN exchange.
- The local radio issues an SDP inquiry to identify the services supported on the remote device.
- The Found New Hardware Wizard searches for appropriate drivers on the local hard disk drive, and/or on Windows Update.
- If the Found New Hardware Wizard does not find an appropriate driver for the device, it prompts the user to insert the profile driver installation media that contains the profile driver's device setup information file (INF file).
Installing a Server-side Profile Driver
The Bluetooth driver stack supports service GUIDs as defined by the Bluetooth SIG, as well as custom GUIDs (that is, GUIDs that are not defined by the Bluetooth SIG).
Note You can use the Guidgen.exe tool that is provided with the Microsoft Windows SDK to create custom GUIDs.
To expose computer functionality that remote Bluetooth devices can use, you must write a user-mode installation application.
The installation application must communicate with the Bluetooth driver stack to create a service GUID for the functionality to expose. Vendors specify the service GUID in the application and in their device installation INF file.
If you need to install or reinstall Windows 8.1, you can use the tools on this page to create your own installation media using either a USB flash drive or a DVD. Use the media creation tool (aprx. 1.41MB) to download Windows. This tool provides the best download experience for customers running. Jul 09, 2018 Windows 8.1 Download ISO 32 / 64 bit Official direct link is now available on PcHippo. Install Windows 8.1 Pro full version without going to the Windows Store or upgrade Windows 8 using Win8 key. Pchippo gives the single-click direct download of free Windows 8.1 Official ISO for 32 bit and 64 bit. May 05, 2014 KB2919442 is a prerequisite for Windows 8.1 Update and should be installed before attempting to install KB2919355 Additional Information Other critical security updates are available: To find the latest security updates for you, visit Windows Update and click Express Install. How to download and install windows 8.1 for free full version 64 bit.
The installation application must call the user-mode API BluetoothSetLocalServiceInfo. However, before the application can call this API, the application must have the SE_LOAD_DRIVER_NAME security privilege. The following code example demonstrates how to obtain this privilege. Note, the example does not demonstrate error handling.
Profile Driver INF file
A profile driver's INF file contains information about a Bluetooth device for client-side installation. For a server-side installation, the INF file specifies a device ID that corresponds to the service GUID created by the installation application. All Bluetooth devices are members of the Bluetooth class. The Bluetooth class installer ( Bthci.dll) assists in installing profile drivers.
For more information about creating and distributing INF files and installing drivers, see Creating an INF File and INF File Sections and Directives.
Plug and Play IDs
The Bluetooth driver stack generates hardware IDs according to the following templates:
- BTHENUM{ ServiceGUID}_VID& nnnnnnnn
- BTHENUM{ ServiceGUID}_VID& nnnnnnnn_PID& nnnn
- BTHENUM{ ServiceGUID}_LOCALMFG& nnnn
The Bluetooth driver stack generates compatible IDs according to the following template:
- BTHENUM{ ServiceGUID}
ServiceGUID is a 16-bit GUID expanded into a 128-bit GUID, as defined by the Bluetooth specification. For example, {00001124-0000-1000-8000-00805F9B34FB} corresponds to an HID device.
The 8 digits following VID& correspond to the vendor ID code.
The 4 digits following PID& correspond to the product ID code.
The 4 digits following LOCALMFG& correspond to the manufacturer of the local Bluetooth radio.
The VID/PID and LOCALMFG tags are independent of each other.
The most generic device ID is a ServiceGUID by itself. For example:
Microsoft Bluetooth Stack Windows Xp Sp3
BTHENUM{00001124-0000-1000-8000-00805F9B34FB}
You can restrict the Bluetooth driver stack to load your profile driver and software to run only on a specific release of a remote device by using Plug and Play IDs in both the remote device and the INF file. Note that the Bluetooth driver stack generates a VID/PID pair only if the device publishes a Plug and Play ID that the stack can detect using SDP. For example:
BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_VID& nnnnnnnn_PID& nnnn
Repair Microsoft Bluetooth Stack Windows 7
You can restrict the Bluetooth driver stack to load profile driver and software to run only on a specific local Bluetooth radio by specifying the LOCALMFG tag in the device ID in your INF file. For example:
Microsoft Bluetooth Stack Driver Download
BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_LOCALMFG& nnnn