Betaflight not connecting? Fixes for no COM port and USB problems

You plug in the whoop, open Betaflight, and nothing: no port in the list, or Connect spins and gives up. It's almost never the flight controller. Work through these fixes in order. Each one takes a minute, and the first two solve most cases.

Before anything else: props off. Betaflight can spin motors from the Motors tab, and USB is enough to power the board.

1. The USB cable

Many USB cables, especially the ones that came with power banks and earbuds, are charge-only: they carry power but no data. The board's LED lights up, so it looks connected, but your computer never sees it.

• Try a cable you know transfers files, such as the one you use to copy photos off your phone.
• Plug straight into the computer, not through a hub or monitor port.
• Wiggle-test: if the connection drops when you touch the cable, the cable or the socket is worn.

2. The right app and browser

Betaflight now runs as a web app at app.betaflight.com, as well as the older desktop Configurator. The web app talks to your board through Web Serial, which only Chromium browsers support.

Setup	Works?
Web app in Chrome or Edge on Windows, Mac, Linux	Yes
Web app in Firefox or Safari	No: no Web Serial support
Desktop Configurator	Yes, but check it's a recent version for your firmware

If the browser asks for permission to access a serial port, pick the board and allow it. If you clicked away from that prompt, reload and press Connect again.

3. Something else holding the port

Only one program can use the port at a time. Close:

• A second Betaflight tab or window
• The desktop Configurator if you're using the web app (or the other way round)
• ESC tools, 3D-printer software (Cura and similar scan serial ports), Arduino IDE and serial monitors

Then unplug, plug back in and connect.

4. Pick the right port

With the board unplugged, open the port list and note what's there. Plug in and look again: the new entry is your board. On Windows it's a COM number, on Mac something like /dev/tty.usbmodem…, on Linux /dev/ttyACM0.

If nothing new appears, go back to the cable, then to drivers.

5. Drivers (mostly Windows)

Windows 10 and 11 usually recognise flight controllers on their own. When they don't:

Symptom	Likely fix
"Unknown device" or no COM port on Windows	Install the STM32 Virtual COM Port driver
Shows in DFU but flashing fails	Fix the DFU driver with the ImpulseRC Driver Fixer or Zadig (WinUSB)
Board uses a CP210x or CH340 USB chip (rare on whoop boards)	Install that chip's driver
Linux: port appears but won't open	Add your user to the dialout group, log out and back in
Mac	Native USB boards need no driver

6. Stuck in DFU mode

If the port list shows DFU instead of a COM port, the board started in its bootloader. That happens when the boot button is held while plugging in, after an interrupted flash, or when the firmware is missing.

1. Unplug, wait five seconds, plug in without touching the boot button.
2. Still DFU? Open the Firmware Flasher, choose your board's exact target, and flash. The target name is printed on the board or in the seller's listing; for BNFs, the manufacturer's site lists it.
3. After flashing, unplug and replug. It should now connect as a normal port.

Flash the wrong target and the board may not boot at all, so double-check the name before you press Flash.

7. A damaged USB socket

Whoops crash nose-first, and the USB socket on an all-in-one board is often right at the front. Signs it's the socket, not software:

• The board's LED doesn't light from USB at all, but it powers up on a battery
• The connection drops when you touch the plug
• The socket wobbles or sits crooked on the board

A cracked socket can be reflowed by someone handy with a fine soldering tip, but on a cheap whoop board, replacing the board is often quicker. See how to fix a crashed whoop for what else to check after a hard hit.

Connected, but something's off

Problem	Cause
Connects, then disconnects every few seconds	Bad cable or socket, or a USB power-saving setting on a laptop
"Unsupported firmware version"	Configurator older or newer than the firmware; update one to match
Receiver tab shows no stick movement on USB	Receiver not powered on USB alone; plug in a battery with props off
Motors tab won't spin motors	No battery, or the safety switch in the Motors tab not enabled

Bottom line

Cable first, browser second, then close whatever else is holding the port. Drivers, DFU and a damaged socket are the rarer cases. Once you're in, follow the Betaflight setup for beginners or the tiny whoop first-flight checklist.

See also

• How to set up Betaflight for beginners
• Betaflight setup for a tiny whoop: first-flight checklist
• How to arm an FPV drone
• How to bind a whoop to a radio

Bench

Whoop flight controllers and spare boards: the Bench.

FAQ

Why won't Betaflight connect to my flight controller?

Most often it's a charge-only USB cable. After that: another app or browser tab holding the port, the wrong port selected, a browser without Web Serial (use Chrome or Edge for the Betaflight web app), a missing driver on Windows, or a board stuck in DFU mode. Work through them in that order.

Do I need to plug in a battery to connect Betaflight?

No. USB powers the flight controller, so take the props off and connect without a battery. Some boards don't power the receiver or video transmitter on USB alone, so plug in a battery only when you need to test those, with props still off.

My board shows up as DFU instead of a COM port. What now?

DFU is the bootloader, used for flashing firmware. Unplug, wait a few seconds and plug in without holding the boot button. If it only ever shows DFU, the firmware is missing or corrupt: flash the correct target for your board from the Firmware Flasher tab, then it will connect normally.