Skip to main content
Associate
March 14, 2026
Solved

"Unable to launch" error after stm32cubeide update

  • March 14, 2026
  • 1 reply
  • 281 views

Hi all,

I'm having an issue with a pre-existing project. It was initially built a few months ago on version 1.16 of the IDE, and confirmed to be working. I have since updated to stm32cube ide version 2.1, and am having an issue with this project not being able to launch. 

 

The projects builds with zero warnings or errors as expected, but on trying to flash my board I get "Unable to launch. the selection cannot be launched, and there are no recent launches".  

 
 

Screenshot 2026-03-14 145114.png

One change I made (that I'm not sure if it is relevant) is updating the GCC flags to inlcude "-Wno-implicit-function-declaration", as it was having trouble finding a C wrapped extern method. 

 

I have seen a previous thread that resolved this issue by using the example importer (Solved: Unable to launch, The selection cannot be launced ... - STMicroelectronics Community), but I want to avoid that to prevent any unintended changed to the current project structure. Additionally, unless I have a misunderstanding as to how the example importer works, I don't want to re-import all of my projects under a different structure if there is an issue with the correct way to import it.

 

Any guidance much appreciated!

Thank you,

Chris 

Best answer by chris7777

I was able to solve this by opening run -> run configurations, and applying a new configuration

1 reply

TDK
Super User
March 14, 2026

Usually this happens when a project is not imported correctly. You could try removing the project from the workspace and double clicking the ".project" file to open it. A full screenshot of the IDE may also help.

"If you feel a post has answered your question, please click ""Accept as Solution""."
chris7777Author
Associate
March 15, 2026

Thanks for the reply. I've removed the project and reimported it by clicking the ".project" file. Still having the same issue:

Screenshot 2026-03-15 114256.png

chris7777AuthorBest answer
Associate
March 15, 2026

I was able to solve this by opening run -> run configurations, and applying a new configuration