This took me at least 30 minutes given the many websites and YouTube tips around this that are confusing and/or wrong (example: 'Q: How to program BetaFlight? A:Press boot button' is incorrect in many cases) Both of these modes require a different driver and both of these drivers can only be installed/configured when both of these modes have been 'shown' to Windows. I don't consider myself a beginner on Windows/drivers/programming, but to me it was unclear, when I started using a quadcopter & BetaFlight, that the FC can be in two modes. I also don't think it is something useful to learn to all BetaFlight users. I think that the fully automated method of driver installation is the way to go, because that would be most user friendly. Instead the BFC Installer would need to do the inf-file modifications and possibly also registry modifications itself, replacing the Win/STM default driver with the 'WinUSB' driver. Both requires the bootloader device being connected. Downloading and running Zadig or ImpulseRC DF is not a solution. The BOOTLOADER USB device interface is slightly different matter. For the USB VCP and CP210x drivers, you only need to download and make the files available in the right places, Windows PnP will then do the final installation when the device is connected. Please also remember the two different procedures needed. Hi all commented on Jan That sounds as a very reasonable solution, having options for the user to bypass the driver installations. However, I think it would be good if there was still an option for the user to re-do or repair the driver installations. In that case, the bypass checkbox could be pre-set, or driver install part completely hidden. The BFC Installer could/should first of all check if all those driver issues has already been done.

That sounds as a very reasonable solution, having options for the user to bypass the driver installations.

Impulse rc driver fixer stuck searching