Quick Answer
If your flight controller is not showing up in Betaflight, the problem is almost always one of three things: the wrong USB cable, a missing driver, or the board being stuck in bootloader mode. We see this exact issue in at least a quarter of the support emails we get from new builders, and nine times out of ten it takes under five minutes to fix once you know where to look.
Why Your Flight Controller Won't Connect
When you plug a flight controller into your computer via USB, it should appear as a serial device that Betaflight can detect. If the top right corner of Betaflight stays blank or shows "No Serial Port Available," the computer is not recognising the board at all. This is different from your drone not arming, which is a separate issue that happens after connection works.
In our workshop we have plugged in hundreds of flight controllers from our flight controller range. The SpeedyBee F405 V5 uses an STM32 virtual COM port, while boards like the Axisflying Argus use a CP210x chip. Both need the correct driver installed before Betaflight will see them.
The USB Cable Check (Do This First)
Before anything else, swap your USB cable. We are not joking. Roughly 40% of the "my FC won't connect" emails we receive are solved by using a different cable. Many USB-C cables that come with phones and other devices are charge-only cables with no data lines. If you plug in your SpeedyBee F405 V5 and nothing happens, grab a cable you know works for transferring files, not just charging. A proper data cable costs about £3. We keep a bin of known-good cables at every workbench in the shop for exactly this reason.
Installing the Right Drivers
If the cable is good and the board still does not appear, you need to install the right USB driver. We stock the SpeedyBee and Axisflying stacks partly because their driver support is reliable, but Windows does not always load the correct driver automatically. Open Device Manager and look under "Ports (COM and LPT)." A yellow warning triangle means the driver is missing.
For STM32 boards (most modern F4 and H7 FCs), download the STM32 Virtual COM Port driver. For CP210x chips (like the Axisflying Argus stack), get the Silicon Labs driver. For CH340-based budget FCs, use the WCH driver. On macOS, remove the ST driver and rely on native CDC support.
DFU Mode and Bootloader Problems
If your flight controller shows up in Device Manager as "STM32 BOOTLOADER" or "DFU device" instead of a COM port, the board has lost its firmware or the bootloader is stuck. This happens most often after a failed flash or a power interruption during a firmware update.
To fix this, you need to reflash the firmware using DFU mode. On Windows, use the Zadig utility to replace the DFU driver with WinUSB, then use Betaflight's firmware flasher to reinstall the correct firmware for your board. After flashing, the board should reconnect as a normal COM port.
Hold the boot button while plugging in USB to enter DFU deliberately. Most boards have a tiny "BOOT" or "BL" button near the USB port.
Common Mistakes We See
The single biggest mistake is using a USB hub. Flight controllers need a direct connection to the computer. USB hubs, especially unpowered ones, introduce enough latency and power fluctuation to cause dropouts. Plug directly into your laptop or desktop.
Second: having the wrong board selected in Betaflight. Even if the COM port appears, select the correct target (e.g., "SPEEDYBEEF405V5") before clicking Connect. Third: running an outdated Betaflight Configurator version. Always update to the latest release from our flight stacks collection.
FAQ
Q: My flight controller shows in Device Manager but not in Betaflight?
A: This usually means the correct driver is not installed, or you need to select the COM port manually from the dropdown in Betaflight's top right corner. Also check that you are using a data USB cable, not a charge-only one.
Q: Do I need to install drivers on Linux?
A: Most Linux distributions recognise STM32 and CP210x devices automatically. If not, you may need to add your user to the "dialout" group with the command sudo usermod -aG dialout \$USER, then log out and back in.
Q: What does DFU mode mean?
A: DFU stands for Device Firmware Upgrade. It is a low-level programming mode used to flash new firmware to the STM32 chip on your flight controller. You only need it for initial flashing or recovering a board that has lost its firmware.
Q: Can a bad USB-C adapter cause connection problems?
A: Yes. Some USB-C to USB-A adapters do not pass data correctly. If you are using an adapter between your FC's USB-C port and your computer, try a direct cable or a different adapter first.