Bluetooth Quick Connect is a lightweight Windows tray utility for quickly connecting, disconnecting, removing, and refreshing paired Bluetooth devices without opening the full Windows Bluetooth Settings page every time.
It is designed mainly for Bluetooth audio devices such as headphones, earbuds, headsets, and speakers. The app stays in the Windows tray and opens a small floating popup near the taskbar when you click the tray icon.
-
Tray-based workflow
Keep the app running quietly in the Windows notification area. -
Floating quick-connect popup
Click the tray icon to open a compact Bluetooth device panel anchored near the taskbar. -
Paired device list
Lists paired, remembered, authenticated, and connected Bluetooth devices detected by Windows. -
Connected device highlighting
Connected devices are visually highlighted in the list. -
Quick actions
- Connect selected device
- Disconnect selected device
- Remove selected paired device from Windows
- Open Windows Bluetooth pairing page
- Refresh device list
-
Keyboard shortcuts
Enterβ connect selected deviceDeleteβ remove selected deviceF5β refresh devicesEscβ hide popup- Double-click a device β toggle connect/disconnect
-
Start with Windows
Enable or disable autostart from the tray menu. The app uses the current user's Windows registry startup key, so administrator rights are not required. -
Modern dark UI
Borderless popup with a custom dark palette and compact controls. -
Update support
Includes support for update checks through the bundled updater helper and local/shared update folder logic.
Windows does not provide a simple public API to generically connect every possible Bluetooth device type. Because of that, Bluetooth Quick Connect uses the Windows Bluetooth API through AutoIt DLL calls and toggles common Bluetooth audio service profiles.
The app currently attempts to connect or disconnect the following Bluetooth service profiles:
| Profile | GUID | Typical use |
|---|---|---|
| Handsfree | {0000111e-0000-1000-8000-00805f9b34fb} |
Headsets, hands-free audio |
| Audio Sink | {0000110b-0000-1000-8000-00805f9b34fb} |
Speakers, headphones, earbuds |
| Headset | {00001108-0000-1000-8000-00805f9b34fb} |
Legacy headset profile |
This approach works well for many Bluetooth audio devices, but it is not a universal Bluetooth connection method.
Bluetooth Quick Connect is intentionally small and focused. A few limitations are expected:
- It works best with Bluetooth audio devices.
- Pure BLE devices, sensors, smart home devices, keyboards, mice, or vendor-specific devices may not connect through this method.
- Some devices may appear in the list but cannot be connected or disconnected by this app.
- Pairing new devices is handled by Windows Settings, not directly inside the app.
- Windows Bluetooth behavior can vary depending on drivers, device firmware, and the Bluetooth adapter.
If a device does not connect from this app but works from Windows Settings, the device probably does not expose one of the supported audio service profiles in a way that can be toggled through BluetoothSetServiceState.
- Windows 10 or Windows 11
- A working Bluetooth adapter
- At least one paired Bluetooth device
- The compiled
BluetoothQuickConnect.exe
To build from source:
- AutoIt v3
- SciTE4AutoIt3 or AutoItWrapper
- Windows SDK is not required; the app calls native Windows DLLs directly
Recommended repository layout:
.\BluetoothQuickConnect
βββ BluetoothQuickConnect.au3
βββ Updater_lib2.au3
βββ Updater.exe
βββ FileUpdate.exe
βββ bt1.ico
βββ settings.ini
βββ README.md
βββ LICENSE
| File | Purpose |
|---|---|
BluetoothQuickConnect.au3 |
Main AutoIt source code |
Updater_lib2.au3 |
GitHub/update helper library used by the main app |
Updater.exe |
Helper executable used to replace the running app during updates |
FileUpdate.exe |
Optional post-build/update helper, depending on your build workflow |
bt1.ico |
Application/tray icon |
settings.ini |
Local configuration file |
README.md |
Project documentation |
LICENSE |
Project license file |
-
Download the latest release package.
-
Extract the files to a local folder, for example:
.\BluetoothQuickConnect -
Run:
.\BluetoothQuickConnect\BluetoothQuickConnect.exe -
The Bluetooth Quick Connect icon should appear in the Windows tray.
-
Right-click the tray icon and enable Start with Windows if desired.
- Install AutoIt v3.
- Clone or download this repository.
- Open
BluetoothQuickConnect.au3in SciTE4AutoIt3. - Run the script from SciTE for testing.
Important: when running the .au3 directly, the automatic GitHub update check is skipped by design. The update check runs only when the script is compiled as an .exe.
Open the project folder:
cd .\BluetoothQuickConnectCompile the main script using SciTE4AutoIt3 or AutoItWrapper.
A typical manual compile command looks like this:
Aut2Exe.exe /in ".\BluetoothQuickConnect.au3" /out ".\BluetoothQuickConnect.exe" /x64 /icon ".\bt1.ico"If you use AutoItWrapper directives, keep paths relative so the project can be built on another machine without editing local installation paths. For example:
#AutoIt3Wrapper_UseX64=y
#AutoIt3Wrapper_UseUpx=n
#AutoIt3Wrapper_Icon=bt1.ico
#AutoIt3Wrapper_Res_File_Add=.\Updater.exe
#AutoIt3Wrapper_Run_After=.\FileUpdate.exeMake sure Updater.exe, FileUpdate.exe, and bt1.ico exist in the project folder before compiling.
The app reads local configuration from:
.\BluetoothQuickConnect\settings.ini
Current update-related setting:
[Update]
path=.\updatesThe path value points to the folder where a newer compiled version of the app may be placed for local/shared-folder updates.
Example local update layout:
.\BluetoothQuickConnect
βββ BluetoothQuickConnect.exe
βββ settings.ini
βββ updates
βββ BluetoothQuickConnect.exe
The updater compares the file version of the local running executable with the file version of the executable found in the configured update folder. If the update folder contains a newer version, the app copies it as a temporary file and launches the updater helper to replace the running executable.
Bluetooth Quick Connect has two update-related paths in the current codebase.
When the app is running as a compiled executable, it calls:
_CheckGitHubUpdate()This function is provided by Updater_lib2.au3. It is skipped when running the .au3 source directly from SciTE or development mode.
The app name used by the update helper is:
Global $GitHubAppName = "BluetoothQuickConnect"The app also checks the folder configured in settings.ini:
[Update]
path=.\updatesIt compares:
Configured update folder executable version
vs.
Currently running executable version
If the update folder version is higher, the app:
- Copies the newer executable to the local app folder as a temporary file.
- Extracts or prepares
Updater.exe. - Runs
Updater.exefrom the temporary folder. - Exits the current running process so the update helper can replace it.
The update logic depends on the executable file version, not only the version displayed in the UI.
Keep these version values aligned whenever possible:
#AutoIt3Wrapper_Res_Fileversion=1.1.2.1
#AutoIt3Wrapper_Res_ProductVersion=1.1.2.1
Global Const $APP_VERSION = "1.1.2.1"Recommended rule:
Every release should increase
Fileversion. The updater will not install a build with the same or lower file version.
If the update is not happening, the first thing to check is whether the available update executable really has a higher Fileversion than the installed executable.
If the app is not updating, check the following items first.
The GitHub update check is intentionally skipped when running the source file directly.
Build and run the .exe to test the full update flow.
The updater compares executable file versions.
Example:
Installed version: 1.1.2.1
Available version: 1.1.1.8
Result: no update
That is expected behavior because the available version is lower than the installed version.
Confirm this value:
[Update]
path=.\updatesThe folder must contain a compiled executable with the same file name as the running app.
Make sure the release package includes:
.\BluetoothQuickConnect\Updater.exe
The running app uses this helper to replace itself during an update.
The app must be able to write to its own installation folder during update. If the app is installed under a protected folder such as Program Files, Windows may block replacement unless the updater is elevated.
For a simple portable installation, keep the app in a user-writable folder.
Because the updater replaces an executable, security tools may block or delay the operation. If updates fail silently, check Windows Security, SmartScreen, antivirus logs, or controlled folder access rules.
Click the Bluetooth Quick Connect tray icon.
- Open the popup.
- Select a paired device.
- Click Connect or press
Enter.
- Select a connected device.
- Click Disconnect.
Double-click a device in the list.
If it is connected, the app attempts to disconnect it. If it is disconnected, the app attempts to connect it.
- Select a device.
- Click Remove or press
Delete. - Confirm the removal.
This removes the paired Bluetooth device from Windows.
Click Pair or use the tray menu option Pair new device....
The app opens the Windows Bluetooth Settings page:
ms-settings:bluetooth
Click Refresh or press F5.
Right-click the tray icon and select Start with Windows.
The app writes a per-user startup entry under:
HKCU\Software\Microsoft\Windows\CurrentVersion\Run
No administrator rights are required.
To disable autostart, right-click the tray icon again and uncheck Start with Windows.
The app checks for another running instance of the same script/executable. If a duplicate instance is detected, the older process is closed and the app restarts from the current path.
Device discovery uses Windows Bluetooth APIs exposed through bthprops.cpl, including:
BluetoothFindFirstRadioBluetoothFindFirstDeviceBluetoothFindNextDeviceBluetoothGetDeviceInfoBluetoothSetServiceStateBluetoothRemoveDevice
The popup is created as a borderless topmost tool window and is automatically hidden when it loses focus. It is not meant to behave like a full desktop application window.
The ListView uses custom draw handling and converts RGB values to Windows COLORREF/BGR format for row highlighting.
Before publishing a new release:
- Update
Fileversion. - Update
ProductVersion. - Update the displayed app version, if applicable.
- Compile the
.exein x64 mode. - Confirm
Updater.exeis bundled. - Confirm
settings.iniuses a generic or relative update path. - Test running the compiled
.exe, not only the.au3source. - Test Connect, Disconnect, Refresh, Pair, Remove, and Start with Windows.
- Confirm the release package does not contain local development paths.
- Publish the release package and version metadata used by the updater.
The device may not expose one of the supported Bluetooth audio profiles. This is common with BLE-only devices, keyboards, mice, sensors, or vendor-specific hardware.
Windows Settings can use internal Windows behavior that is not fully exposed through a simple public API. Bluetooth Quick Connect uses the available Bluetooth service-state API, which is more limited.
The source contains a safety check that skips the GitHub update check when the script name contains .au3. This prevents development sessions from replacing files unexpectedly.
Normally, no. Bluetooth actions and per-user autostart do not require administrator rights. Updating may require write access to the folder where the app is installed.
It may list them, but connect/disconnect is focused on audio service profiles. Non-audio devices are not guaranteed to work.
Possible future improvements:
- Verbose updater log viewer inside the app
- Settings screen for update path and logging options
- Optional toast notifications for update results
- Better detection of unsupported device profiles
- Device pinning or favorites
- Configurable popup size and position
- Installer package
- Signed executable for smoother SmartScreen behavior
Add a LICENSE file before publishing the repository. If you do not have a preference yet, the MIT License is a common choice for small open-source utilities.
Developed by Fabricio Zambroni.
This project is not affiliated with Microsoft. Bluetooth device behavior depends on Windows, Bluetooth drivers, hardware firmware, and supported service profiles.