BluFang is a PowerShell script that lists all your paired Bluetooth devices, lets you rename any of them, and shows the connection details Windows hides — signal strength, battery, BT version, manufacturer, and device class.
Windows gives every Bluetooth device a name. Sometimes it's the product name. Sometimes it's a model number. Sometimes it's just "LE-Bose AE2" or "Bluetooth Device (RFCOMM Protocol TDI)" and you have no idea what it is anymore.
Pair a dozen devices — headphones, a keyboard, a mouse, speakers, a game controller — and half of them show up in Settings as something unhelpful. You can't rename them from the Bluetooth settings page. You can dig into Device Manager and edit the friendly name in the registry, but that's a multi-step hunt through HKLM that nobody wants to do repeatedly. BluFang wraps it all into one interactive menu.
Run BluFang and you get an interactive menu of every paired Bluetooth device. For each one, BluFang pulls data that Windows has in the registry and WMI but doesn't surface anywhere in the UI:
Select a device from the menu, type a new name, and BluFang writes it to the registry. The change takes effect immediately — no reboot, no re-pairing. Name your headphones "Sony WH-1000XM5" instead of "LE_WH-1000XM5". Call your keyboard "Keychron K2" instead of "Bluetooth Keyboard". Whatever makes sense to you.
BluFang is free and open source — a single PowerShell script with no modules and no dependencies. It needs Windows 10 or 11, PowerShell 5.1 or 7+, and must run as Administrator (registry writes to HKLM require elevation).
Source and documentation: github.com/VAROIndustries/BluFang
Named for Harald Bluetooth — the Viking king who united Denmark and Norway. Just like this tool unites you with your device names.
HKLM, and editing it by hand is a multi-step hunt nobody wants to do repeatedly. BluFang lists every paired device in an interactive menu and writes the new name to the registry for you.HKLM, and registry writes to HKLM require elevation. Right-click PowerShell, choose Run as Administrator, then run the script.