Microsoft Bluetooth Le Enumerator Driver Download

If you have had recent power outages, viruses or other computer problems, it is likely that the drivers have become damaged. Browse the list above to find the driver that matches your hardware and operating system. To see more matches, use our custom driver search engine to find the exact driver.

  1. Microsoft Bluetooth Le Enumerator Driver Download Windows 7
  2. Microsoft Bluetooth Le Enumerator Driver Download
  3. Reinstall Microsoft Bluetooth Le Enumerator

Tech Tip: If you are having trouble deciding which is the right driver, try the Driver Update Utility for Microsoft Bluetooth LE Enumerator. It is a software utility that will find the right driver for you - automatically.

Argentina Australia Austria Bangladesh Belarus Belgium Bolivia Brazil Bulgaria Canada Chile Colombia Costa Rica Croatia Cyprus Czech Republic Denmark Dominican Republic Ecuador Egypt El Salvador Estonia Finland France Germany Greece Guatemala Honduras Hong Kong S.A.R. Of China Hungary India Indonesia Ireland Israel Italy Japan Latvia Lithuania. Microsoft Bluetooth Enumerator Software 33 DOWNLOAD (Mirror #1) Microsoft Bluetooth Enumerator Software 33 DOWNLOAD (Mirror #1) Home. Bluetooth LE Devices connectivity issues. Some users complained on Microsoft Answers Forums that the Bluetooth LE Devices are not connecting as expected after installing the Creators Update. Products Home Drivers & Software Intel® Wireless Bluetooth® Driver for Windows® 10 64-Bit for Intel® NUC Version: 21.120.0 (Latest) Date: 9/30/2020. Microsoft Bluetooth Enumerator free download - Microsoft Silverlight, Microsoft Word, Bluetooth Software, and many more programs.

DriverGuide maintains an extensive archive of Windows drivers available for free download. We employ a team from around the world which adds hundreds of new drivers to our site every day.

Adele 21 free album download

How to Install Drivers

Once you download your new driver, then you need to install it. To install a driver in Windows, you will need to use a built-in utility called Device Manager. It allows you to see all of the devices recognized by your system, and the drivers associated with them.

Open Device Manager

  • In Windows 10 & Windows 8.1, right-click the Start menu and select Device Manager

  • In Windows 8, swipe up from the bottom, or right-click anywhere on the desktop and choose 'All Apps' -> swipe or scroll right and choose 'Control Panel' (under Windows System section) -> Hardware and Sound -> Device Manager

  • In Windows 7, click Start -> Control Panel -> Hardware and Sound -> Device Manager

  • In Windows Vista, click Start -> Control Panel -> System and Maintenance -> Device Manager

  • In Windows XP, click Start -> Control Panel -> Performance and Maintenance -> System -> Hardware tab -> Device Manager button

Install Drivers With Device Manager

  1. Locate the device and model that is having the issue and double-click on it to open the Properties dialog box.

  2. Select the Driver tab.

  3. Click the Update Driver button and follow the instructions.

In most cases, you will need to reboot your computer in order for the driver update to take effect.

Visit our Driver Support Page for helpful step-by-step videos


If you are having trouble finding the right driver, stop searching and fix driver problems faster with the Automatic Driver Update Utility. Many computer problems are caused by missing or outdated device drivers, especially in Windows 10. If your deskttop or laptop is running slow, or keeps crashing or hanging, there is a good chance that updating your drivers will fix the problem. Automatic updates could save you hours of time.



This topic is for programmers. If you are a customer experiencing Bluetooth device installation issues see Pair a Bluetooth device in Windows

There are two installation types for Bluetooth profile drivers:

  • Client-side installation 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 installation 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

A user that wants to use a Bluetooth-enabled device will bring the device within range of the computer and initiate a connection from the computer to the remote device using the following installation sequence for a client-side profile driver.

  1. Launch Bluetooth Devices in Control Panel to find all devices within range of the computer.

  2. Select the device to pair with.

  3. Pair (or bond) the device with the local radio. This may or may not involve a PIN exchange.

  4. The local radio issues an SDP inquiry to identify the services supported on the remote device.

  5. The Found New Hardware Wizard searches for appropriate drivers on the local hard disk drive, and/or on Windows Update.

  6. 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).


The Guidgen.exe tool provided with the Microsoft Windows SDK can be used to create custom GUIDs.

A user-mode installation application must be written to expose computer functionality that remote Bluetooth devices can use.

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.

The installation application must call the user-mode API BluetoothSetLocalServiceInfo. 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 that 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

Microsoft Bluetooth Le Enumerator Driver Download Windows 7

The Bluetooth driver stack generates compatible IDs according to the following template:

  • BTHENUM{ ServiceGUID}

Microsoft Bluetooth Le Enumerator Driver Download

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.

Reinstall Microsoft Bluetooth Le Enumerator

  • 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:


The Bluetooth driver stack can be restricted 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

The Bluetooth driver stack can be restricted 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:

BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_LOCALMFG& nnnn