I found out from Richard today that XP SP2 includes the Microsoft Bluetooth stack which now supports third party radios. Wow, I had no idea, I hadn't even noticed the new icon in the control panel. Tonight I uninstalled the Belkin Bluetooth software and drivers. In the past they worked well enough (usually), but the shell integration with explorer was slow and ugly. Plugging the device back in was enough to get it recognised by the Microsoft stack. This is about where the excitement ends as I realise I now only have support for File Transfer, the Bluetooth Serial protocol and the ability to Join a Personal Area Network. I've lost PIM sync (Contact and Calendar synchronisation with Outlook). I never got the Headset or Autio Gateway protocols to work via the Belkin stack so there's no loss there. OBEX navigation via integration with explorer would have been nice, but file send and recieve is enough for my needs right now. Hopefully in the (near) future we will see third party products plugging in the other standard protocols. The real benefit of the new stack is that developers can finally target a single API. Cool ideas like BlueMonger and btChat will become a lot more accessible. Unfortunately I won't be hacking on bluetooth just yet given that the API is part of the Platform SDK and inherently unmanaged. As much as I would love to write a wrapper with managed C++, I don't have the time. For now I'll have to resort to using Floats Mobile Agent to synchronise my T610. It does the job, but suffers from feature-bloat and goes off on so many tangents that the actual user experience has been completely forgotten. </rant> Update: For all those people who end up here by way of google. The answer to your question is most likely to install the driver stack that came with your bluetooth adapter.