2026-03-16 12:02 AM - last edited on 2026-03-16 1:13 AM by mƎALLEm
I updated the STM3CubeProgrammer to version v2.22.0, and after restarting the app, it started showing a blank page. I was also not able to close the application directly. I had to end the task from the task manager.
I uninstalled the latest version and installed v2.20.0, but it is also showing a blank page.
Also, in STM32CubeIDE, I am not able to run and debug code. It gets stuck at "Download in progress".
Are both problems related?
Solved! Go to Solution.
2026-03-22 10:14 PM - edited 2026-03-22 10:15 PM
The STM32CubeIDE problem was related to the STLINK-V3MODS debugger's incomplete firmware upgrade. Upgrading the firmware again by changing the type solved the problem.
Reinstalling the STM32CubeProgrammer again solved the problem.
2026-03-16 12:05 AM
Windows version:
Edition Windows 11 Pro
Version 25H2
Installed on 03-Dec-25
OS build 26200.8037
Experience Windows Feature Experience Pack 1000.26100.300.0
STM32CubeIDE versions:
2.0.0 and 2.1.0
2026-03-17 4:38 AM - edited 2026-03-17 4:39 AM
Hello @abhi4,
I have copied your exact setup, did a fresh install of STM32CubeProgrammer v2.22 and tried updating from v2.21 but I was not able to reproduce this behavior.
Can you please try the following and let me know the results?
1) delete config.properties that is located in: C:\Users\"Your_PC"\STMicroelectronics\STM32CubeProgrammer and then launch again.
OR
2) A fresh install of STM32CubeProgrammer v2.22
If you have any additional information, please do not hesitate to mention it and let me know if you still need additional help.
2026-03-17 4:45 AM
@abhi4 wrote:Also, in STM32CubeIDE, I am not able to run and debug code. It gets stuck at "Download in progress".
Are both problems related?
Unlikely - that'll be a problem somewhere between your PC, your debug probe (eg, ST-Link), and your target hardware.
Start a separate thread for that ...
2026-03-22 10:14 PM - edited 2026-03-22 10:15 PM
The STM32CubeIDE problem was related to the STLINK-V3MODS debugger's incomplete firmware upgrade. Upgrading the firmware again by changing the type solved the problem.
Reinstalling the STM32CubeProgrammer again solved the problem.