Please go to this page for driver information.
Driver installation is usually not needed on Windows 10, but if you encounter problems relating to drivers on Windows 10, please see this support article.
SKU: USB-BT4LE
List Price : $15.95
Amazon Rating :
(11952 Reviews)
Features
Add Bluetooth Technology to Your PC
The Plugable Bluetooth adapter adds the ability to connect Bluetooth devices to Windows PCs. This dual-mode adapter connects devices using Bluetooth Classic or Bluetooth Low Energy*.
Works with 32-bit and 64-bit editions of Windows 7*, 8.x, 10, and 11.
Connect
Connect devices featuring Bluetooth technology that can be connected to your computer through the Plugable Bluetooth adapter include wireless Bluetooth headphones*, Bluetooth speakers*, Bluetooth mice*, Bluetooth keyboards*, Bluetooth game controllers*, and much more.
Using Steam on a Windows PC simplifies the use of popular controllers like the PlayStation DualShock 4, PlayStation DualSense, and Nintendo Switch Pro Controller. Windows 10 and 11 have native support for Xbox Wireless Controllers featuring Bluetooth while using this adapter.
Range
As a certified Bluetooth Class 2 device, the Plugable Bluetooth adapter has been validated by the Bluetooth Special Interest Group (Bluetooth SIG) to connect up to 32 feet (10 meters) away.
Compact and Sturdy
The adapter's compact size and revised plastic casing means you can leave it in your laptop when you are on the go.
* See the compatibility tab and the FAQ tab on this page for details regarding device compatibility.
Many devices require support for multiple profile to fully pair and function. Software issues are the responsibility of:
See the compatibility tab on this page for details regarding profile support on various operating systems as well as device compatibility.
Item and Quantity | Item Notes |
---|---|
1x USB 2.0 Bluetooth Adapter | |
1x Mini CD-ROM Driver Disk | |
1x Quick Install Guide |
Port | Placement | Power Host / Device | Connection Type | Notes | Voltage | Amperage | Wattage |
---|---|---|---|---|---|---|---|
USB-A to Host | Cable End | Device | 5.0V | 160mA | 0.8W |
Port | Placement | Version and Link Rate | Features |
---|---|---|---|
1x USB-A | Bottom | USB 2.0 (480Mbps) |
Bluetooth Specification | Supported Profiles | Notable Unsupported Profiles | Bluetooth Class and Range | Chipset |
---|---|---|---|---|
Bluetooth 4.0 | See Profile Compatibility Table | Bluetooth Low Energy Peripheral Role HID Proxy Support | Class 2 10m/32ft |
Host Compatibility
Device/Operating System | Works as a Host for the Plugable Bluetooth Adapter? | Can Connect to a Host Using the Adapter? |
---|---|---|
Windows 11 PC | * | |
Windows 10 PC | * | |
Windows 8.x PC | * | |
Windows 7 PC | * | |
Windows Server | * | |
Windows RT, IoT, and 10X | * | |
Linux PC | * | |
Synology NAS | Audio only—refer to Synology's Website | |
QNAP NAS | Audio only—refer to QNAP's Website | |
Mac | * | |
iOS/iPadOS | * | |
Android | * | |
Chromebooks | ||
Chrome OS | ||
Xbox Consoles | ||
PlayStation Consoles | ||
Nintendo Consoles | ||
Car Dashboard Audio Decks | ||
Televisions | ||
Other non-PC Devices | ** |
* While it is possible to connect a smartphone, or a PC, via Bluetooth to a PC that is using the Plugable Bluetooth adapter, there are some things to consider. For the most part, there are not many useful features when connecting a phone to a PC outside of data transfers. However, even for data transfers, there are much better ways to exchange data between devices. Bluetooth, without an optional and rarely used feature to work in tandem with Wi-Fi, has a theoretical maximum throughput of 3Mbps, with a practical performance closer to 1.5Mbps (192KB/s). At this rate, it would take over seven minutes to transfer eight 10MB photos. Wi-Fi and USB are much better options to exchange data between hosts.
** See the next table for details.
Specific Device Compatibility
Please note that the Linux compatibility statements here will almost certainly apply to any Bluetooth adapter connected to a Linux PC, not just the Plugable Bluetooth adapter. This is because if Linux supports the driver for a Bluetooth adapter (the driver for the Plugable Bluetooth adapter is built into modern Linux kernels), the device and Bluetooth profile compatibility is still dependent on BlueZ and Pulseaudio which handle data and audio communicated via Bluetooth.There are currently ongoing issues with the BlueZ project, particularly surrounding audio support. Because of these issues, we currently consider Linux incompatible with the adapter.
Device | Works on Windows | Works on Linux (Linux is not compatible at this time) |
---|---|---|
Headphones w/Bluetooth Low Energy | Windows 7—Requires the 6.5.0.2000 Driver Windows 8.x—Use the 12.0.1.940 driver for best compatibility Windows 10 or 11—Use the driver that installs via Windows Update (check optional updates) |
Dependent on Linux open source projects |
Headset Microphones | Supported | Dependent on Linux open source projects |
Monoprice 8323 Headphones | Unsupported | Dependent on Linux open source projects |
Mice and Keyboards | See this article for details | See this article for details |
Fitness Trackers | Check manufacturer's site for Windows compatibility | Check manufacturer's site for Linux compatibility |
Windows Mixed Reality | Windows 10 and 11 only See Microsoft's documentation for details |
Unsupported |
Bluetooth Xbox One Controller Xbox Elite Controller Xbox Elite Series 2 Controller |
One Controller on Windows 10 and 11 only See Microsoft's documentation for details |
Unsupported See linked article for details |
Sixaxis Controller DualShock 3 Controller |
Supported via Steam. Other methods available, but not recommended. Micro USB Cable Required for Pairing. See linked article for details |
Unsupported See linked article for details |
DualShock 4 Controller DualSense Controller |
Supported via Steam. Other methods available, but not recommended. See linked article for details |
Unsupported See linked article for details |
JoyCons Nintendo Switch Pro Controller |
Supported via Steam. Other methods available, but not recommended. See linked article for details |
Unsupported See linked article for details |
8BitDo Bluetooth Controllers (and GBros Wireless Adapter) |
On Windows 10, most 8BitDo Bluetooth controllers function as an Xbox Wireless Controller. DirectInput operation modes are compatible with Steam | Unsupported See linked article for details |
Apple Keyboards, Mice, and Trackpads | Likely Works See linked article for details |
Likely Works See linked article for details |
Other Devices | Check with device maker for OS compatibility | Check with device maker for OS compatibility |
In an era of devices that offer so much simplicity, Bluetooth wireless technology blurs the line between complexity and simplicity in ways that many users don’t expect.
Bluetooth once served a singular purpose of providing the functionality of a serial cable over a wireless connection, but has since evolved into so much more. How can the same technology that wirelessly communicates audio also be the technology that turns a lamp on and off? The answer is Bluetooth profiles.
To oversimplify a Bluetooth profile, it can be described as an accepted way of using Bluetooth technology to communicate data of a particular type. There are profiles for audio communication, profiles to transmit certain types of information like heart rate and blood pressure, as well as profiles to share images and video.
The Bluetooth Special Interest Group’s (Bluetooth SIG) official explanation of Bluetooth Profiles is (in all its confusing glory):
" Profiles are definitions of possible applications and specify general behaviors that Bluetooth® enabled devices use to communicate with other Bluetooth devices. Profiles build on the Bluetooth standard to more clearly define what kind of data a Bluetooth module is transmitting. The device’s application determines which profiles it must support, from hands-free capabilities to heart rate sensors to alerts and more.
For two Bluetooth devices to be compatible, they must support the same profiles. And while profiles generally describe the same use case behaviors, they are different for Bluetooth BR/EDR and LE implementations. Compatibility between BR/EDR and LE implementations requires a dual-mode controller on at least one device for interoperability. For BR/EDR, a wide range of adopted Bluetooth profiles describe many different common types of applications or use cases for devices. For Bluetooth LE, developers have the option of using a comprehensive set of adopted profiles, or use the Generic Attribute Profile (GATT) to create new profiles. This helps support innovative new applications that maintain interoperability with other Bluetooth devices.
Bluetooth profiles typically contain information such as dependencies on other profiles and suggested user interface formats. For BR/EDR, the profile will also specify the particular options and parameters at each layer of the Bluetooth protocol stack used to perform its task. This may include, if appropriate, an outline of the required service record."
There are clearly a lot of details behind a Bluetooth profile, but for users trying to make use of a particular device, the most important thing is whether or not a profile is supported, and whether or not their device is going to work how they want it to.
In this article we will explore the profiles that are supported by the Plugable USB-BT4LE Bluetooth adapter based on Windows’ built-in support, support added by Broadcom’s WIDCOMM software, and the BlueZ software used in Linux. In addition to this, we’ll offer some explanation about Bluetooth errors such as “Driver Not Found”, and what potential issues you might encounter with profiles.
Profile Compatibility Sheet Key
In an effort to provide more information regarding Bluetooth profiles, we’ve created an in-depth spreadsheet to better detail which profiles are supported in which operating systems.
The data in this sheet is not based on testing conducted by Plugable, but is instead based on software documentation from various organizations, profile definitions that are visible in source code and driver files, as well as Bluetooth SIG qualification summaries.
Color Key for Spreadsheet Data
Compatibility with the Latest Profile Version |
Compatibility with a Version of the Profile |
Conflicting Information, Known Issues, or Uncertainty |
Not Compatible |
Deprecated and/or Unused |
As you can see from the chart, compatibility with certain Bluetooth profiles varies wildly from one Windows version to the next, as well as between Windows and Linux.
These discrepancies can prove especially challenging in situations where a device is using a profile that depends on other profiles to function. A partial lack of profile support can make the difference between a device working, or not working.
What You May See if a Profile Is Missing
On Windows, if a profile is missing, usually the device will still complete the pairing process. Once pairing is completed, Windows will attempt to assign driver functions to the profile identifiers that it detects. Errors like "Driver Not Found" or "Error Installing Driver" are a typical behavior from Windows when profiles are missing.
It is important to note though, that this is not the whole story with driver errors with regards to Bluetooth. A very common issue with Bluetooth profile driver install errors, is the presence of other Bluetooth drivers for a different adapter. Since Bluetooth relies on multiple software components, the driver for a profile may not install if it is already registered to operate with another set of Bluetooth drivers. If you need help with this on your Plugable Bluetooth adapter, please feel free to contact us at support@plugable.com for assistance. We’re happy to help!
Other Aspects of Bluetooth Profiles to Be Mindful Of
When it comes to audio, there are usually a lot of profiles involved to make everything work. Usually these devices have broad support from a profile perspective, but may also include some specialized technology like aptX support (which is now included as part of Windows 10), which is not a profile but rather a coding method to send higher quality audio to devices that support it. You can learn more in-depth information about Bluetooth profiles and codecs for Bluetooth in our article "Understanding Bluetooth® Wireless Audio".
With some profiles, like those used for audio, only one device can use the profile at a time. For example, you wouldn’t be able to have two pairs of headphones use the A2DP profile to listen to music from the same device. Manufacturers like Bose that have a proprietary Bluetooth ‘Music Share’ feature allowing two sets of headphones to listen to the same source aren’t technically both connected to the same source. Instead, one of the headphones acts as a relay to pass the audio to the next pair of headphones. This is also the case with pairs of wireless Bluetooth speakers designed to operate in stereo. One of the speakers connects via Bluetooth while the other connects directly to the other speaker.
For Bluetooth Low Energy, use cases are typically more specialized and don’t operate in the same generalized way that Bluetooth Classic profiles do currently. For example, FitBit requires using a specialized Windows 10 (UWP) application to make use of data from their devices, rather than Windows having a default interface to display information provided by FitBit devices
A Note About WIDCOMM
While there was a WIDCOMM software available for Windows 10, it has since become deprecated as Windows 10 has undergone several major upgrades since it was initially launched. If you are trying to use a profile that is listed as "Supported (WIDCOMM)" for Windows 10, you may need to check if Windows 10 updates have incorporated support for that profile, otherwise they are not supported in current versions of Windows 10.
Where to Learn More About Bluetooth Profiles and What They Do
Wikipedia has a great entry on Bluetooth profiles and a general synopsis of what they do . The Bluetooth Special Interest Group’s webpage on adopted Bluetooth profiles includes more in-depth technical information on profiles as well.
As always, we’re here to help with Bluetooth questions related to your Plugable products. We’re happy to answer customer questions through our support@plugable.com e-mail address.
Before You Begin
Before installing and configuring your Plugable Bluetooth adapter. It is recommended to check if your computer has any configuration issues that may cause problems.
Please review the following items.
Getting Started on Windows
Follow the steps below to install the Plugable Bluetooth adapter on your Windows PC.
Windows 10
Windows 8.x
Windows 7
Getting Started on Linux
The drivers for the Plugable Bluetooth adapter are built into the Linux kernel.
Challenges with Bluetooth connectivity in Linux primarily have to do with the stability and configuration of the BlueZ and Pulseaudio open source projects.
Bluetooth audio, including microphone input. As well as game controllers. Are the devices that most commonly have problems on Linux.
Unlike Windows, it is possible to have more than one Bluetooth adapter connected. However, it can be difficult to select which adapter you're making connections through. Typically it is best to use 'Bluetooth Manager' (package name blueman
) to choose which adapter you're pairing a device with.
Problems?
Most issues with the adapter stem from having conflicting drivers, incorrect drivers, or an existing Bluetooth adapter.
Please evaluate our extensive library of troubleshooting information in the FAQ tab of this product page.
If you need further assistance, please reach out to us at support@plugable.com
Please go to this page for driver information.
Driver installation is usually not needed on Windows 10, but if you encounter problems relating to drivers on Windows 10, please see this support article.
In part, because the higher speed of the USB 3.0 port (also known as USB 3.1 Gen 1 and USB 3.2 Gen 1) offers no advantage if the device itself is USB 2.0. For Plugable's USB 2.0 Bluetooth and Wi-Fi adapters, the performance is far below even the throughput of USB 2.0.
Also, the adapter itself is a USB 2.0 device and there is a critical issue that was overlooked in the design of USB 3.0 specifications. Many USB 3.0 ports leak broad-spectrum radio interference in the 2.4GHz to 2.5GHz range, which is the same radio band used by Bluetooth and Wi-Fi
While this interference can be reduced through heavy shielding, it cannot be entirely avoided as it is inherent to the core design of USB 3.0. USB 2.0 ports do not have this issue. However, a USB 2.0 port that is in close proximity to an in-use USB 3.0 port may also be affected by radio noise leaked by it.
Components inside a tower-style computer case are largely exposed, and there is very little shielding to reduce the radio interference they produce. This is particularly true at the rear input/output panel of a PC. This is why cables that are designed to plug into the back of a computer often have a ferrite bead attached to them, to reduce radio interference. Also, the wireless signal weakens as it travels through the metal and plastic computer case and goes past the noise-producing components.
If you don’t have a port available on the front your PC, consider using a USB 2.0 hub to add ports located away from the back of your PC, or use a USB 2.0 extension cable to move the adapter to a location in line-of-sight with your receiving device.
The Bluetooth icon in the Windows system tray provides an easy way to connect and manage Bluetooth devices on your Windows 7, 8.x, or 10 computer, and many Bluetooth users rely on it. But an accidental click in the wrong place can cause you to lose that icon, leaving no obvious way to access Bluetooth settings. Here is how to restore it.
When Bluetooth is activated in a Windows 7, 8.x, or 10 computer, Windows places a Bluetooth icon in the System Tray—the collection of easily accessible icons near the clock. It will either appear on the task bar or can be accessed by clicking the upward pointing triangle.
Clicking the Bluetooth icon displays a menu with entries for adding and managing Bluetooth devices. At the bottom of the menu, in a location that is easy to click by mistake, there is a 'Remove Icon' entry. This removes the icon and closes the menu with no notification or confirmation. The next time you go to use Bluetooth, the icon is unexpectedly gone. With no icon or other indication that Bluetooth is available, it is easy to assume that Bluetooth is broken or no longer exists on the computer. It is difficult to understand why Microsoft included this, since icons in the System Tray can be easily hidden using the 'Customize' link on the menu.
Although it is extremely easy to remove the icon by accident, Windows provides no easy way to restore it. Despite the importance of Bluetooth these days, especially to tablet users, Windows provides no Bluetooth control applet in the Control Panel. In Windows 8.x, a Bluetooth settings panel is available several levels deep from the Settings icon in the Charms menu, but like most Charms panels, its functionality is limited, and it includes no method to restore the Bluetooth icon.
A detailed Bluetooth control applet does exist. Called Change Bluetooth Settings, it can be opened by searching for it in the Start menu. The procedure is slightly different in Windows 7 and in Windows 8.x/10, but once found, the icon is easy to restore.
change Bluetooth settings
in the 'Search Programs and Files' box directly above the Start buttonchange Bluetooth settings
We hope this guide is useful! If you have any question, and if you are using a Plugable Bluetooth adapter, please reach out to us at support@plugable.com for assistance. If possible, please include your Amazon (or other retailer's) order ID and a PlugDebug log. We're happy to help!
Normally, Windows 10 will automatically install the 12.0.1.750 driver for the Plugable Bluetooth 4.0 USB Adapter. However, there have been some issues with the driver install process in the Windows 10 October 2020 Update (also know as the 20H2 or v2009 update).
First, it is recommended to try manually running Windows Update
update
If the driver does not install through this process, please try the steps below to manually install the 12.0.1.750 driver that is normally installed through Windows Update.
If there are still issues, please contact us for additional support.
There are a few reasons this could be happening, depending on the operating system used on your PC.
On all versions of Windows, it is important to make sure that the Bluetooth audio device is set as your active audio device for sound output/input. Be sure to check our guide on how to do that.
An issue that can occur on Windows 7, and earlier versions of Windows, is that many modern Bluetooth audio devices incorporate Bluetooth Low Energy (BLE) features from the Bluetooth 4.0 specifications. Unfortunately, Microsoft never implemented BLE support into versions of Windows prior to Windows 8.x.
Without support for BLE, earlier versions of Windows can get confused about how to handle BLE features on devices that have them. This can manifest in a variety of ways such as the PC showing that there are devices it cannot find drivers for, or it may simply appear that a device is connected but won't function. On Windows 7, this can be somewhat addressed by installing the 6.5.0.2000 driver version that we have available for download, rather than the one on the CD that comes with the adapter. This should at least correct issues with newer audio devices that have BLE features.
On Linux, the driver that provides support for Linux to use the Bluetooth radio in the adapter is baked into the kernel. However, there is more to Bluetooth than simply making the radio available.
Linux primarily uses two software libraries to support Bluetooth connections, BlueZ and Pulseaudio. BlueZ is the software layer that understands the various types of data that can be communicated over Bluetooth, such as mouse and keyboard input, controller input, audio, etc. BlueZ itself interfaces with Pulseaudio to provide audio playback and recording.
Unfortunately, the BlueZ and Pulseaudio open-source projects tend to introduce bugs on a regular basis that cause issues with certain devices. Given the added complexity of BlueZ interfacing with Pulseaudio for audio features, there tends to be more issues with Bluetooth audio in particular versus other types of Bluetooth hardware.
It is recommended to check the community forums for your Linux distro to see if there are other users experiencing audio issues on your current version. In addition, here are some other resources you can check for solutions to Bluetooth audio issues in Linux.
In some cases, manually compiling BlueZ and manually updating Pulseaudio components can help. The instructions below were written for Ubuntu 16.x and 18.x, and should be adaptable to other Linux distros by using the appropriate package manager rather than apt.
Note: As of this writing, BlueZ 5.54 is the current version. However, the most recent version that doesn't seem to have significant bugs is 5.52.
wget http://www.kernel.org/pub/linux/bluetooth/bluez-5.52.tar.xz && tar xf bluez-5.52.tar.xz
cd bluez-5.52
sudo apt install pulseaudio-module-bluetooth libusb-dev libdbus-1-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev blueman
sudo /etc/init.d/bluetooth stop
sudo ./configure && sudo make && sudo make install
sudo reboot
Of course, beyond these issues with BlueZ and Pulseaudio, it is important to make sure that you've configured your Bluetooth audio device as the default audio device in your distro's sound settings, once pairing has been completed.
If you are finding that you can't be as far from the Bluetooth adapter as you expected, or if you're having issues with audio skipping or lagging, this is likely due to radio interference.
Below are some common causes of interference to avoid.
The most common cause of audio cutting out or having limited range between a device and the Bluetooth adapter is radio interference.
The most common source of radio interference are USB 3.0 ports. USB 3.0 unfortunately emits broad-spectrum radio interference in the 2.4GHz to 2.5GHz range, which is the same frequency range used by Bluetooth, 2.4GHz Wi-Fi bands, and many other consumer wireless devices.
More information on this USB 3.0 issue can be found in this white paper by Intel .
This issue with USB 3.0 can typically be resolved by plugging the Bluetooth adapter into a USB 2.0 port, whether that be a USB 2.0 port directly on the PC, a USB 2.0 port on an attached USB hub, or USB 2.0 extension cable.
Another common cause of radio interference is having an object that blocks line of site between the Bluetooth adapter and the device being used. Make sure that there is a clear line-of-sight between the adapter and the device you're using.
The last common cause of audio cutting out or having limited range is if the adapter is plugged into the rear input/output panel of a traditional desktop PC. It is recommended to have the adapter plugged into the front or the side of the PC instead, or to bring the adapter away from the PC tower using a USB 2.0 hub or USB 2.0 extension cable.
Some driver packages that were released during the first year or two of Windows 10's availability are not compatible with current versions of Windows 10. In particular, the 12.0.1.940 driver package with the WIDCOMM Bluetooth Software can result in these types of issues.
You can usually check if this is present by looking at your list of installed applications for "WIDCOMM". If you find this, the drivers will need to be removed. Please contact us for assistance with this, be sure to include your Amazon (or other retailer's) order ID and a PlugDebug log with your message so that we can provide steps to resolve this issue.
Please contact us so that we can help!
If you are encountering issues with sound quality when connected through the Plugable Bluetooth adapter, it is usually caused by the audio device being connected in headset mode.
Bluetooth has two primary profiles for handling audio. One of these profiles is referred to as the Headset Profile (HSP ) and the other is the Advanced Audio Distribution Profile (A2DP ).
A2DP is the profile that is most often used for listening to music in stereo at high quality.
HSP allows for microphone input from a Bluetooth device at the expense of reducing audio quality, and limiting sound output from the PC to monaural audio rather than stereo.
In Windows, the headset profile is automatically triggered any time that the microphone is requested by an application. This can include being in the Windows sound properties and viewing recording devices, or if a communication application like Skype or Discord is set to use the microphone on a Bluetooth audio device.
You will want to make sure that:
If the headset profile is active the audio will usually sound compressed and lack punchiness.
If you continue to experience issues with your Plugable Bluetooth adapter or Plugable Bluetooth audio device, please reach out to us at support@plugable.com so that we can help.
Connecting Bluetooth devices can be tricky!
While resolving thousands of Bluetooth issues here at Plugable, we’ve learned that the problem is often something going wrong in the pairing process. As we’ve helped customers with these issues, we’ve developed a step-by-step procedure that should work in any situation where a device isn’t pairing properly. We’ve also put together a database of pairing instructions for a wide range of Bluetooth audio devices.
There are multiple sets of instructions below for different versions of Windows. If you're having troubles connecting, try the instructions. If it fails at any point, contact us at support@plugable.com and tell us which step it failed on, and we’ll already have a good start on the troubleshooting process!
Additional Configuration
In Windows 7, audio devices that are using Bluetooth Low Energy—which Windows 7 does not support—may need some additional configuration, or they may show errors.
Devices With Errors
Devices that appear with a yellow triangle are likely going to work just fine. They may show a yellow triangle due to missing "Bluetooth Peripheral Device" items, which are essentially profiles that Windows 7 doesn't support. This is normal.
Partially Connected Devices
Some devices may complete the pairing process, but won't connect to all services available on the device.
Comments, questions, or suggestions on improving this post? Let us know by contacting us for support.
Use the buttons below to toggle showing pairing instructions for brands beginning with that letter.
Compatibility with modern wireless game controllers is a complex topic. Almost every console controller requires some kind of third-party software to be fully, or even partially, functional via Bluetooth. Due to this, it is important to use the controllers exactly as described in this guide to get the expected results. It is also worth noting that the behavior of third-party software is difficult to trace since we did not design the software, so issues relating specifically to software mentioned in this article is limited.
In this article, you'll find details about how to connect:
Note: Information about third-party software is only provided here for context. We do not officially recommend, support, or endorse these third-party software solutions. If you choose to use these software packages, you are doing so at your own risk.
This Google Sheet provides an at-a-glance view of what controller features are supported, along with notes about issues with particular controllers.
Microsoft introduced XInput in late 2005 as an update to DirectInput. Most PC games produced in the last decade or so have support for XInput. Support for DirectInput is mostly limited to older PC games. It is important to be aware of what protocol your controller is using, as it may cause compatibility issues with certain games or software.
Xbox controllers, since the Xbox 360 controller, have functioned over XInput. There are many other controllers, intended for use with a PC, also map their controls via XInput.
Most console controllers, other than Xbox-branded controllers, map their controls using DirectInput. This means that, even after establishing a connection, controllers intended for PlayStation and Nintendo consoles won't necessarily work with a PC without some additional software. Steam is typically the best choice for getting controllers working, but other options are available in most cases, though many of those alternatives are software that require a license fee to use.
Linux has extensive support for gamepads. However, it requires a great deal of manual configuration. Because of this lack of simplicity in configuring controllers, we do not recommend or provide support for using controllers on Linux.
Please see this article from the Arch Linux Wiki (ArchWiki) for details about manual configuration of various controllers.
Generally speaking, if you want to use a Nintendo or PlayStation controller on a PC, it is best to configure it using Steam. Valve has spent significant resources to easily remap controls to standard XInput controls. Even if you are using games from a store other than Steam, you can add it as a non-Steam game and utilize the built-in input mapper of Steam.
There are a number of reasons to use Steam for input mapping. For one, it is likely that the input mapper in Steam will continue to be supported in the long term. Additionally, Steam is focused on interpreting input data through standard Bluetooth interfaces in Windows, rather than overriding normal Windows Bluetooth profile support. This design makes it far less likely to cause conflicting issues with other Bluetooth devices.
Further instructions on controller remapping for Steam can be found here .
Since the introduction of the PlayStation 3, Sony has used a customized version of Bluetooth to connect controllers to their game consoles. The modifications that Sony uses are primarily to facilitate the way that PlayStation controllers pair with a console and the way they power on a console.
To connect a PlayStation 3 (Sixaxis/DualShock 3) controller to a PC, a USB cable is required to initially pair the controller to a PC. PlayStation 4 (DualShock 4) and PlayStation 5 (DualSense) controllers can pair without the use of a USB cable.
There have been third-party software packages that allow PlayStation controllers to connect, such as 'DS4Windows' and 'ScpToolkit', but these programs cause issues with other normal functions of Bluetooth adapters on PCs. Additionally, with regards to ScpToolkit, the creator of ScpToolkit explicitly notes that there are harmful versions of the software that are distributed with malware and that the software is obsolete , it absolutely should not be installed.
Users of these controllers should check the latest information on PCGamingWiki for details on how to use these controllers.
One way to connect these controllers is to first install the PlayStation Now app—which includes drivers for the controller—and perform pairing of the controller using the instructions for the PlayStation Now app . Once that process is complete, you'll need to map controls using another application (such as Steam).
Sony notes that, when connected to a PC, the following features are not supported:
As of writing this article, the DualSense controller included with the PlayStation 5 connects wirelessly in an unknown fashion. It is assumed that it uses a modified Bluetooth implementation similar to the last two generations of controllers for PlayStation consoles.
Note: The original launch version of the Xbox One controller does not have Bluetooth built-in. Make sure that you are using a later revision of the controller that does have Bluetooth. Images detailing the physical differences between both versions can be found in this article from Xbox .
Microsoft only recommends using a single Xbox Wireless Controller at a time when connecting via Bluetooth.
Windows 10—Has native support for Xbox One controllers via Bluetooth starting from the Windows 10 Anniversary Update. Please see instructions from Microsoft on how to update both Windows 10 and the controller itself .
Microsoft has announced that Xbox Series controllers, will work via Bluetooth . Their current compatibility information mirrors that of the Xbox One Wireless Controllers featuring Bluetooth.
The already-released Xbox Elite Wireless Series 2 controller requires updating Windows 10 to the May 2019 Update (or later) with the latest fixes and updates applied .
As of this writing, all Nintendo-branded wireless controllers, including controllers designed for the Nintendo Switch, map their controls using DirectInput and connect using Bluetooth Classic. Mapping controls via DirectInput causes the controllers to be incompatible with most PC games without additional software.
There isn't much use for this controller outside of console emulation. The Dolphin emulator has support for the Wii Remote, but Dolphin completely takes control of the Bluetooth adapter in order to function , and will typically require a third-party sensor bar that operates without the Wii console. Because Dolphin overrides the default behavior of the adapter, we do not support this configuration.
The Nintendo Joy-Cons will connect via Bluetooth without third-party software. Without using third-party software, the individual Joy-Cons connect as individual DirectInput controllers. Additionally, most features such as motion control and rumble, require third-party software.
The Nintendo Switch Pro Controller will connect for basic functionality via Bluetooth without third-party software, but has poor compatibility due to controls being mapped via DirectInput. Most features such as motion control and rumble require third-party software.
For use with PC games, it is likely best to use Steam to map the controller to XInput for compatibility with most games.
Windows 10—Controllers from 8BitDo that feature Bluetooth connectivity, such as the SN30 Pro and SN30 Pro+ will often have the option of connecting using either XInput or DirectInput. It is recommended to use XInput with the latest updates applied to Windows 10.
In 8BitDo's documentation, they refer to this as 'X-Input' or 'Xbox 360' mode.
This controller is not supported.
There are known issues with this controller with regards to reconnecting to a host using the Plugable Bluetooth adapter after the controller has been powered off. If using this controller, you must go through the pairing process each time you wish to use it when connecting through the Plugable Bluetooth adapter.
The Steam Controller is no longer in production. It can connect via Bluetooth Low Energy on Windows 8.x and above as well as Linux with the most recent firmware updates applied through Steam.
Steam is required for this controller. Instructions from Valve on how to enable Bluetooth Low Energy for the Steam Controller, and use it with Steam, can be found here .
Check with your controller manufacturer regarding the wireless technology that is used, and whether the controller maps its inputs via DirectInput or via XInput.
We do not recommend using the Plugable Bluetooth adapter on systems that have a built-in Bluetooth adapter, or that have used a different Bluetooth adapter in the past.
Windows has a limitation where it cannot manage more than one Bluetooth adapter at a time , and it also struggles with having software for multiple Bluetooth adapters present.
Unlike previous versions of Windows, it is not a viable option to disable a built-in Bluetooth adapter via Device Manager. Roughly every six months a major update to Windows is released by Microsoft, and when those updates are applied, it enables devices that were previously disabled in Device Manager.
The only way to reliably use the Plugable Bluetooth adapter, if your computer has a built-in Bluetooth adapter, is to disable the built-in adapter in your computer's BIOS configuration. This prevents Windows from being able to detect the hardware.
While it is possible to disable the built-in Bluetooth adapter via Device Manager, it is a common problem for drivers not to uninstall cleanly
Unlike Windows, it is technically possible to have more than one Bluetooth adapter without them conflicting with each other. However, most Bluetooth applications do not support selecting which adapter is being used.
A program called Bluetooth Manager (package name blueman), allows you to choose which Bluetooth adapter is the one you're actively configuring with regards to device pairing.
Access Device Manager
devmgmt.msc
then press EnterAnother option is to use PlugDebug. After your computer has run PlugDebug and generated a file on your desktop, open the .zip file and open 'devman.csv'. With that file open, search in the contents for 'BTHUSB'. Any entries including that are a Bluetooth adapter.
Note: It is unlikely that this will be sufficient to remove an adapter especially on Windows 10. Correctly removing all traces of an adapter are far more involved, but we document that here.
We do everything we can to indicate that the adapter should not be used on systems with an existing Bluetooth adapter, or on systems that have a previous Bluetooth adapter. Because of this, our support for complications related to this issue is limited. That being said, please reach out to us at support@plugable.com if you need assistance. When contacting us, please include a file generated by our PlugDebug software and details regarding your order of the Bluetooth adapter.
When the adapter is connected to a PC, the blue LED lights up when the PC communicates with it, showing the adapter is physically connected and responding to the PC.
The light should come on, at least momentarily, even before drivers are installed. If the light does not come on, try a different port or rebooting the machine. If this does not help, please contact us at support@plugable.com.
In recent versions of of iTunes, Apple has made changes that can cause disconnects in Windows 7. This fix usually solves the problem.
C:\Program Files\WIDCOMM\Bluetooth Software\
BtITunesPlugin.exe
BtITunesPlugin.exe
and select 'Rename'Old_BtITunesPlugin.exe
Yes, this is very likely. Many office environments use what is called a Windows Active Directory domain environment that can interfere with the driver install.
We recommend installing the drivers using the domain’s default ‘Administrator’ account to avoid problems. We also strongly recommended disabling antivirus and security software during the installation as these are known to interfere with the driver installer (even if no errors are presented).
Note: This doesn't apply to Windows 10.
Please try the following:
services.msc
in the window that appearsBefore attempting to connect a wireless mouse and keyboard, it is important to determine the wireless technology used by your mouse or keyboard.
There are multiple methods of wireless connectivity that can be used by device makers to connect wireless devices to a computer or mobile device. Some devices are able to connect by more than one method, but most will only offer one connection method. This can be a problem since most wireless connection types are not compatible with each other. We'll start by going over the different types of wireless connectivity available, then discuss how to determine what connection method is being used by your device.
While Bluetooth has become more common in recent years, it used to be much more common for wireless mice and keyboards to use a custom wireless solution. To some extent, it is still quite common to find wireless mice and keyboards that use a manufacturer's own wireless solution.
Most non-Bluetooth wireless mice and keyboards will come with a USB adapter included that is preprogrammed to connect to the device(s) they were bundled with. This is the first sign that the device isn't using Bluetooth.
Though solutions with proprietary 2.4GHz wireless solutions are restricted to connecting to devices with USB ports where their adapter can be connected, there are some advantages to these over Bluetooth solutions. In particular, proprietary wireless keyboards and mice are essentially the same to a PC as a wired version. This allows input devices with this wireless connection method to be used within a PC's BIOS configuration menus and in other situations where Bluetooth isn't working.
It is common for users with devices that use proprietary 2.4GHz wireless solutions to misplace their USB adapter and seek a replacement. Unfortunately, the only viable solution to replace it is to seek a replacement from the original manufacturer.
For Logitech peripherals in particular, their Logitech Unifying Receiver can be configured with software provided by Logitech to connect to multiple Logitech-branded peripherals.
There are two distinct variations of Bluetooth. While it isn't necessarily important to distinguish between these variations on modern Windows and Linux releases, it is important to understand the difference when using Windows 7 and earlier, as well as older Linux distributions.
All versions of Bluetooth and their associated profiles, up to and including Bluetooth 3.0, are considered Bluetooth Classic. Bluetooth Classic is supported on Windows XP and above, and is widely compatible across Linux distros. Bluetooth mice and keyboards with this technology use the HID (Human Interface Device) profile.
With the release of Bluetooth 4.0, a new type of Bluetooth connectivity was released in the form of Bluetooth Low Energy (also branded as Bluetooth Smart). As the name implies, Bluetooth Low Energy connections strive for increased energy efficiency as compared to Bluetooth Classic. This means that devices using Bluetooth Low Energy connections will generally have longer battery life than their Bluetooth Classic counterparts.
The downside of Bluetooth Low Energy is that it must be supported on hosts and devices for them to function. Newer Bluetooth mice and keyboards use the HoG (Human Interface Device over Generic Attribute Profile) profile to connect over Bluetooth Low Energy. Because Bluetooth Low Energy support was never added to Windows prior to Windows 8.x, these devices are unable to connect to systems running Windows 7 or earlier.
Unfortunately there aren't many quick ways of determining what type of connection your keyboard or mouse is using. Here are some of the indications you can use to determine what technology your mouse or keyboard is using.
Most ways of determining the type of connection used for wireless connectivity require knowing the name, manufacturer, and model of the device. If you are unsure of these details, here are some ways of finding this information.
devmgmt.msc
in the window that appears, and press Enter. In the Device Manager window, open the 'View' menu, then enable 'Show Hidden Devices'If you are having problems determining the wireless connection of your keyboard or mouse, it is recommended to reach out to the device manufacturer for details. Alternatively, please reach out to us at support@plugable.com with pictures of your device, including any labels, markings, or other details that may help with identification.
Once you've determined that your keyboard or mouse is using Bluetooth, please follow our pairing guide.
While it is technically possible to transfer files over Bluetooth, there are much better ways to exchange data between devices.
Bluetooth—without an optional and rarely used feature to work in tandem with Wi-Fi—has a theoretical maximum throughput of 3Mbps, with a practical performance closer to 1.5Mbps (192KB/s). At this rate it would take over seven minutes to transfer eight 10MB photos. Wi-Fi and USB are much better options to exchange data between hosts as their transfer rates are many times greater than that of Bluetooth.
Before continuing, it is recommended that you have your phone, or other file source, paired via Bluetooth.
Exchanging files with your phone through Bluetooth in Windows 7 and above is not straightforward, and a number of users have contacted the Plugable support team looking for an easy way to do this. Fortunately, Windows comes preinstalled with a program called 'fsquirt' that fulfills this need.
Methods of launching fsquirt:
fsquirt
in the window that appearsC:\Windows\System32
then launch fsquirt.exe
fsquirt
then click 'Next'. On the next step of the wizard, enter anything you'd like for the name. You'll now have a shortcut with a Bluetooth icon that launches the fsquirt applicationOnce you've launched the fsquirt application, you'll have the option to send or receive files
The Plugable Bluetooth adapter functions as a radio for Windows to communicate via Bluetooth. It is primarily Windows, and the Bluetooth device you're using, that are responsible for reestablishing connections.
That being said, some USB controllers on some computers will aggressively try to save power by turning off USB devices, which leads to the adapter dropping connections.
Check your power configuration (Power Options) in the Windows Control Panel (search for Control Panel in the start menu). Try disabling USB selective suspend.
In Device Manger (right-click the start menu button, then choose Device Manager), check the properties of the adapter (double-click Broadcom BCM20702 Bluetooth 4.0 USB Device) and ensure that the box for allowing the PC to turn off power is unchecked. Do the same thing for your USB root controllers. This option may not be available.
If this does not resolve the issue with your Plugable Bluetooth adapter, please contact us at support@plugable.com.
The Plugable Bluetooth adapter functions as a radio for Windows to communicate via Bluetooth. It is primarily Windows, and the Bluetooth device you're using, that are responsible for reestablishing connections.
That being said, some USB controllers on some computers do not always wake, which leads to the adapter not being initialized to reestablish Bluetooth connections.
Check your power configuration (Power Options) in the Windows Control Panel (search for Control Panel in the start menu). Try disabling USB selective suspend.
In Device Manger (right-click the start menu button, then choose Device Manager), check the properties of the adapter (double-click Broadcom BCM20702 Bluetooth 4.0 USB Device) and ensure that the box for allowing the PC to turn off power is unchecked. Do the same thing for your USB root controllers. This option may not be available.
If this does not resolve the issue with your Plugable Bluetooth adapter, please contact us at support@plugable.com.