A Bluetooth dongle should be the dullest thing on a desk. You push it into a USB port, your old PC gains a radio, and you forget it. TP-Link’s UB500 does that for many people, and it’s small enough that you may never unplug it. The story gets more interesting when you look at the number printed on the box, and at which computers TP-Link actually supports.
Owner detail for this model is thin, so I’ll say plainly where I am relying on one report.
Product image from the Amazon listing.
My opinion in one line: this is a sensible cheap fix for a Windows desktop with no Bluetooth, and a much less certain buy for anything else.
Related reading
One Name, Several Radios
The first problem is knowing what you are buying. The listing here points to the UB500, and the name has stayed the same while the hardware moved on. TP-Link’s download page lists three hardware versions, V1, V2 and V3. The V3 driver packages are marked as supporting Bluetooth 5.4. Retailers have sold the same model number as Bluetooth 5.0, 5.3 and 5.4.
TP-Link’s own US product page shows how easy it is to mix these up. The title and spec list say 5.4 while the overview text says 5.3. The datasheet for version 3 says 5.4.
So look at the label on the box when it arrives. Most owner comments online are about older units, and some of the forum trouble below is from V1. Please don’t read an old complaint or an old compliment as a sure guide to a new V3, or the other way around.
Does the version number matter much? Less than the box suggests. A Bluetooth version on a dongle sets what the adapter can do, while your headset or mouse sets what you actually get. An old mouse will not act like a new one because the dongle is newer. If you are buying this for a keyboard, a mouse or a basic headset, I would not lose sleep over 5.3 against 5.4.
Windows Is the Whole Official Story
TP-Link’s page lists Windows 11, 10, 8.1 and 7, and nothing else. There’s no Mac driver and no Linux driver on the download page. For Windows 7 you must install the driver yourself from TP-Link’s site. The company’s troubleshooting guide says that on Windows 10 and 8.1 the UB500 driver installs automatically when the computer is online, and that you should install it by hand if that fails.
That matters for the machine this product is really aimed at, which is an older PC. If the computer has no internet because it has no working network at all, you will want the driver on a USB stick first. Some owners in retailer reviews also said it needed a driver on Windows 10 and 11.
One step in TP-Link’s guide is easy to miss. If your computer already has built-in Bluetooth, the guide says to disable it in Device Manager before using the adapter. It also says to remove third-party Bluetooth drivers and programs. A laptop owner who adds this dongle to replace a weak internal radio and skips this step may be creating the problem they then blame on the dongle.
Product image from the Amazon listing.
Mac and Linux: Possible, Not Promised
Here the reports split. Retailer reviews include an owner who says it works perfectly on a Mac, PS5 and PC, and another who reports it running well on Debian 12. A third said it works well on Windows but sometimes struggled on Linux. One retailer listing goes the other way and says it will not work with Mac or Linux at all.
Related reading
These are short comments, so treat them as hints. What I can say with more confidence is that TP-Link does not offer you any support for those systems. If it works on your Linux box, that’s a bonus, and if it stops working after a system update, you are on your own.
For Mac owners, I would stop and ask why. Every Mac in recent memory has Bluetooth built in, and this is a USB-A plug, so a modern Mac would need a USB-C adapter too. There’s one more warning in TP-Link’s compatibility table. The lab results in its guide list “F” for failure next to MacBook and several iPads in the UB500 table. I read that as pairing a Windows PC with those devices, and TP-Link says the list is not complete, but it’s hardly a reason to buy this for an Apple setup.
Range and the USB 3.0 Trap
Picture your headset across the room, with a wall in the way. A nano dongle has a tiny antenna, and TP-Link’s own advice reflects that. The guide recommends keeping devices “within five meters”. Range also depends on both the transmitter and the receiver. Walls, people and Wi-Fi routers can all cut it down.
If you own a desktop, the line about USB 3.0 matters most. The guide says: “An Intel white paper confirmed that poorly shielded USB 3.0 ports will cause radio interference.” So the port you pick can hurt the signal. TP-Link suggests two fixes. Use a front port or a USB 2.0 extension cable. Keep the adapter away from routers and busy USB 3.0 devices.
That advice is worth following from the start. A dongle pushed into the back of a tower, next to a fast external drive, with the metal case between it and your headset, is the worst place for a small radio. A cheap extension cable that brings it up onto the desk costs little and may fix a problem before you ever see it.
I found no owner measurements of latency, of throughput, or of stability during long video calls, and none tied to work with a NAS. Bluetooth has little to do with NAS traffic anyway, so I’d leave that out of your buying decision. For calls, the honest answer is that I don’t know how it behaves over a full day of meetings.
Product image from the Amazon listing.
When It Refuses to Pair
The most detailed owner report is a TP-Link forum thread from May 2024. A V1 owner on Windows 11 could see nearby devices, but every attempt to pair ended with the message “We did not get any response from the device. Try connecting again”. Driver updates, Windows updates, restarting Bluetooth services and system repair tools all failed.
The fix was heavy. The owner ran the Windows reinstall option that keeps apps and files, then installed the UB500 driver again, and warned that it would take two or three reboots. A later poster asked TP-Link to update its drivers so people would not need to reinstall Windows. Another found success after changing a bandwidth setting on a TP-Link wireless USB adapter, and that answer was marked as accepted. That’s an odd fix, since it’s a Wi-Fi setting, and it suggests the two radios were fighting each other on that machine.
Related reading
One thread is one thread, and I can’t tell you how common this is. It does show what the bad case looks like. If the dongle sees your devices and can’t pair with them, the problem may live in Windows, and a replacement dongle may not help.
A Fair Fix for One Kind of Computer
Say you have an older Windows desktop. You want to add a keyboard, a mouse, a controller or a simple pair of headphones. That is where I like the UB500. It’s tiny. It comes from a company that still publishes drivers. The good reports describe a thing you plug in and leave alone. Turn off any built-in radio first, then use a front port or a short USB 2.0 extension.
Skip it if you run Mac or Linux and want a promise that it will work. Skip it too if you need solid range through walls, because a nano dongle with a five meter guideline will not give you that.
For that older Windows PC, the TP-Link USB Bluetooth Adapter is a low-risk thing to try, as long as you check the hardware version on the box and keep the return window in mind. This is an affiliate link. As an Amazon Associate I earn from qualifying purchases.
One email a month: new articles, reviews and the upcoming live webinar + free recording. No spam, unsubscribe anytime.