|Product Dimensions||1.5 x 0.7 x 1.9 cm; 30 Grams|
|Item model number||UB4A|
|Are Batteries Included||No|
|Item Weight||30 g|
Other Sellers on Amazon
TP-Link Nano USB Bluetooth 4.0 Adapter for PC Laptop Desktop Computer, Long Range Bluetooth Dongle/Receiver for Windows 11/10/8.1/8/7/XP, Plug and Play (UB4A)
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Enhance your purchase
|Item dimensions L x W x H||15 x 7 x 19 millimetres|
|Data link protocol||Bluetooth, USB|
About this item
- Make sure this fits by entering your model number.
- Bluetooth 4.0 – applies the latest Bluetooth 4.0 with low energy (BLE) technology
- Driver free – plug and play for Win 8, Win 8.1, and win 10
- Nano-sized – ultra-small for convenient portability with reliable high Performance
- Supported Operating System – supports Windows 11/10/8.1/8/7/XP
- Backward compatibility – full support for Bluetooth V3.0/2.1/2.0/1.1
Special offers and product promotions
- Buy at least 4 items of your choice and save 5%. Offered by Amazon.co.uk. Shop items
From the manufacturer
Link to Your Computer via Bluetooth
UB4A turns Non-Bluetooth PC or laptop into Bluetooth-capable. Just connect your Bluetooth devices to your computer and enjoy it with ease. It supports 7 Bluetooth devices at most.
Broad Operation Range
With a transmission distance of up to 20 m, you can enjoy lossless music via your Bluetooth headset without hovering around your computer. The data of distance applies in an environment with few shelters
Nano-Sized Plug in and forget
A sleek, ultra-small design means you can insert the nano adapter into any USB port and simply keep it there, no matter when you are traveling or at home.
From the brand
What's in the box?
Reviewed in the United Kingdom on 23 October 2020
Reviews with images
Top reviews from United Kingdom
There was a problem filtering reviews right now. Please try again later.
Windows 10 didn't manage to "Plug n Play" this so there was a bit of messing around to get it to work. This seems to be a common issue so I'll run through what to do to resolve it, since once you get this up and running it's pretty darned good!
Firstly, if yours plugs and plays then woohoo! You're away. DO NOT install the driver as directed by the "Quick Start Guide" unless you are running Windows 7 or earlier. Installing the driver on Windows 8 or later will just screw things up and result in strange behaviour.
If you don't get it working straight from the box then type "Device Manager" in the search bar and have a look for a Bluetooth symbol. If not, look in "Universal Serial Bus controllers", click the little arrow to expand the list in either case and look for "CSR".
Right click and select Update Driver.
Next choose "Browse my computer for driver update"
Take the lower option "Let me pick from a list of available drivers on my Computer"
Select "Generic bluetooth Adapter" from the list of options (If an option for "CSR Bluetooth adapter" comes up DO NOT CHOOSE IT under any circumstances!) and that's it!
Your adapter will work and be accessible from "Settings- Devices" just like a laptop with built in Bluetooth.
1) WHAT HAPPENED TO ME USING WIN10 PLUG AND PLAY: Product installs immediately. All drivers present and correct. Paired an audio speaker successfully. But wouldn't play, and in sound control panel it persistently said the device was 'disconnected'. The internet is absolutely full of people reporting exactly the same problem, and loads of suggested "solutions" that simply don't work - I tried most if not all of them! After further research - likely cause is that it seems until Win 8 Microsoft left it to hardware device suppliers to provide their own Bluetooth stack software, but from 8 onward Microsoft implemented a plug and play driver solution within windows itself. But this is inadequate/incomplete in some respects and they are currently working on completing it - no immediate solution therefore unless manufacturers provide 3rd party drivers.
HOW I SOLVED IT EVENTUALLY: TP-Link claim to provide pre-Win8 drivers for the UB4a but the link on their website doesn't lead to drivers! However they often talk about UB400 at the same time, and UB400 does offer a driver in the support page for Win 7 and below. I decided to risk trying it with this product on Win 10. Result: it installed perfectly first time and the product now works with devices exactly as expected. You just have to right click the Bluetooth icon in the notification area to gain access to the Bluetooth functions, as obviously this software predates win10 and is not integrated into the win10 native bluetooth interface. The driver software is badged as "CSR Harmony Wireless Software Stack" and although it is a bit long in the tooth, it is a perfectly acceptable substitute until Microsoft get round to finally fixing their inbuilt bluetooth software stack driver.
UPDATE: I need to revise the above having just taken delivery of super Bluetooth Headphones which I've reviewed elsewhere. These DID connect to this product when using Win10 plug and play mode without any additional driver. My previous attempts had been with an older Bluetooth cube speaker. So, as other reviewers have said - you might be lucky with plug and play. Seems this may depend on newness of Bluetooth item to be connected. Or, probably for older Bluetooth items, you may need to resort to the older driver as described above. I guess it is down to Windows not recognising/supporting older products - another example of software-driven product obsolescence keeping landfill busy and manufacturers happy. Well I don't give in that easily! My Bluetooth cube speaker lives to fight another day.
This has no such problems, and works on Ubuntu, Fedora, etc. without having to do fiddly things with Windows drivers to get it to work.
It does seem to lose connection when the computer hasn't been used for a few minutes, which I think is something to do with a bug in the Bluetooth software on Linux. Hopefully that will be fixed soon!