STM32CubeIDE Debug Launch Stuck at 51% (Affects Multiple Boards, Multiple Users)

[Durgaprasadvalleboina_2001]

 

Dear STMicroelectronics Support Team,

I am writing to report a persistent issue with STM32CubeIDE that is affecting multiple users in our company and blocking our development work.

Issue Description:

When we try to debug any STM32 project, the debugger launch process gets stuck at 51% with the message:

Launching: Initializing debugger services

The issue occurs with different versions of STM32CubeIDE and with multiple target boards.

Steps to Reproduce:

Open STM32CubeIDE and build the project (build succeeds).

Click Debug.

Debugger launch stops at 51% and does not proceed further.

Environment Details:

STM32CubeIDE Versions Tested: 1.9.0 and 1.13.2 (same result)

Operating System: [Windows 10 / Windows 11]

Target Boards Tested:

STM32F429I-DISC1

STM32F407-DISC

ST-LINK Firmware: [if known, mention version]

Actions Taken:

Reinstalled STM32CubeIDE (both versions).

Reinstalled ST-LINK USB drivers.

Verified ST-LINK is detected correctly in Device Manager.

Tried on multiple PCs within our company — all systems show the same behavior.

Despite these actions, the issue persists on all systems and boards.

I have attached a screenshot of the IDE progress bar stuck at 51% for reference.
Could you please investigate this issue and suggest a solution or provide a patch/update if this is a known problem?

This issue is affecting multiple developers in our company, so an urgent resolution would be greatly appreciated.

[rbtmkr42]

Yes - the build command always results with the -1 message, and the debug command always hangs at 51%, whether the automatic build is enabled or not.

[AlisterDsouza]

We are also facing this debug issue, since a very long time. Can someone please help us on this.

Thanks

[TDK]

This feels like a company-specific issue which is going to be difficult to debug externally.

Can you try it on a PC that isn't burdened by company security settings?

[rbtmkr42]

So I have at least 2 other laptops here (one on Windows and one on Linux) that have not had this issue with the same code repository.  I plan to move completely our project dev environment over to Linux going forward, since the build environment just really doesn't like Windows.  It's just frustrating that this computer was fine for about 18 months, and all of a sudden this started happening.  It doesn't make sense, and it was willed that way by the computer gods :laptop_computer::high_voltage::high_voltage::high_voltage:

[Pavel A.]

@rbtmkr42 Before moving to Linux (a good idea generally) consider this:

 - Ask your IT admin to temporary disable the "security" or "management" stuff

 - Try to install the Linux software on Windows under WSL.