2025-09-12 7:47 AM
I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.
I was connected via UART and programming option bytes.
Here was the command I used:
& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0
I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.
Thanks,
Daniel
2025-09-15 3:47 PM
2025-09-17 4:16 AM
I'm having the same issue when using API v2.20 on Windows.
2025-09-17 4:44 AM
Looks like this is a Windows-specific bug. The -noreconnect flag was patched for Linux, but the change hasn’t been applied consistently across platforms. On Windows, the CLI still attempts to reconnect regardless.
Workarounds you can try for now:
Run the same sequence but split into two commands (connect → option bytes → disconnect) instead of relying on -noreconnect.
Or add -hardRst=none if your use case allows — it avoids triggering a reconnect.
Best next step is to file it with ST as a Windows bug so it gets the same fix that Linux received.
2025-09-17 6:59 AM
Thanks for the confirmation and work arounds.
I assumed posting here was filing the bug with ST. Is there a different place for that?
Daniel
2025-09-18 5:18 PM
You’re welcome! Posting here is great for community confirmation, but ST usually only tracks/patches issues if they’re logged through their official ST Support Center (my.st.com → Support → Create a ticket). That way it goes directly to the engineers.
I’d suggest opening a ticket there and linking this thread so they can reproduce and align the Windows fix with the Linux one. :thumbs_up:
2025-09-22 12:52 AM
Hello All,
Thank you for posting and for all the details you provided.
I escalated this issue to the relevant team (through internal ticket number 218005) to take a closer look at the problem.
(PS: ticket number 218005 is an internal tracking number and is not accessible or usable by customers).