2026-01-23 9:07 AM
After updating and restarting my PC with Windows 10, my old version of CubeProgrammer would not open at all. The version number is unknown. Other STM32 software works without any issue such as CubeMX and CubeIDE.
I then tried installing the latest version, 2.21.0. The program launched (even when run as administrator), but it did not function fully. I attached a screenshot for reference. None of the four icons on the top-left responded, and I received error messages when clicking the icons on the right.
I also tried installing previous versions from 2.16.0 to 2.20.0, but none of them worked. Specifically:
Versions 2.16.0, 2.18.0, and 2.19.0 briefly showed the launch logo, then closed immediately.
Versions 2.20.0 and 2.21.0 would open, but the program remained unusable.
Solved! Go to Solution.
2026-01-23 12:28 PM
Open command prompt (cmd) and start CubeProgrammer executable from the cmd window. Observe any error messages or other interesting prints there.
2026-01-23 9:16 AM
What is this icon from?
Maybe something interfering with the GUI.
2026-01-23 9:33 AM
This icon is for my dual-monitor settings. I closed it and reopened the program, but the issue persists. I also performed a Java update and a Windows update this week, though I’m not sure if they are related to the problem. I have never experienced any issues with CubeProgrammer on this PC in the past.
2026-01-23 12:28 PM
Open command prompt (cmd) and start CubeProgrammer executable from the cmd window. Observe any error messages or other interesting prints there.
2026-01-23 1:19 PM
I ran some basic commands, and the programmer appeared to be working correctly via the CMD window.
Surprisingly, after running CubeProgrammer from the CMD, I reopened CubeProgrammer.exe on desktop and the issue was resolved. WOW, no idea how that fixed it, but thank you, mate!
2026-01-27 1:30 AM
Then maybe your menu or desktop shortcut points to a wrong executable or old version?
2026-01-27 8:19 AM
I’m sure that’s not the case. I reinstalled the program multiple times, and the shortcut was regenerated each time. I checked the shortcut properties, and they showed the correct version and installation path.