Kinda late to the party (it's now March 2025) and struggled through the same things with my recent purchase of two discovery boards:
board 1: STM32F100RB (aka STM32VLDISCOVERY) STM32VLDISCOVERY - Discovery kit with STM32F100RB MCU - STMicroelectronics
--> this F1 board has ST-LINK (V1), full of trouble with all STM32Cube software tools; Windows 10 only recognized it as mass storage device, no ST-Link showed up as USB device.
board 2: STM32F411VET6 https://www.st.com/en/evaluation-tools/32f411ediscovery.html
--> this F4 board has ST-LINK (V2), working fine so far with all STM32Cube software tools; and Windows 10 showed ST-Link as USB device only, no mass storage device whatsoever.
Here are my footsteps:
1. Read few chapter of "Discovering the STM32 Microcontroller" by Geoffrey Brown listed on
https://www.st.com/content/st_com/en/support/learning/stm32-education/text-books.html
and purchased the STM32VLDISCOVERY as recommended...
bad choice I guess as it's a legacy product; should be removed from board selector (and create an up-to-date F1 discovery board) imo.
2. Followed the tutorial at https://wiki.st.com/stm32mcu/wiki/STM32StepByStep:Step1_Tools_installation
and struggled with the build/run/debug step because ST-LINK (V1) is incompatible with STM32Cube tools (this was not mentioned anywhere until I see this post).
3. Followed Georgy Moshkin's steps above which enabled me to build & run onto the STM32VLDISCOVERY via STM32CubeIDE.
For now, I'll personally abandon the F1 board and focus on the F4 board since my goal is to learn the basics and quickly create a small demo application for Cortex M (via ST's board).
