STM32F767ZI Nucleo will no longer program after forced ST-Link update

[TonyFocusLCDs]

Hello,

This is now the third Nucleo board that has been "bricked" by a forced ST-Link V2-1 update. I can no longer program the board. Windows 10/11 sees the board as a USB thumb drive (this has always worked) but from within the STM32CubeIDE it will not program the board. It says "waiting on debugger connection" but hits a time out. 

So then using the STM32CubeProgrammer I get the error message "Error: No STM32 target found"

Like I have said this has happened to 3 other Nucleo boards I have and I cannot program them anymore. I am tired of the IDE forcing an update to ST-Link and the update bricks my board making it useless. I tried saying "No" when the IDE asks me to upgrade the ST-Link firmware. But then it says it cannot program the board with out first upgrading the ST-Link firmware. So then I update the firmware and cannot program the boards anymore.

How can ST release such buggy firmware for the ST-Link programmer on their OWN Nucleo boards. I have real production issues to solve but cannot move forward because ST TOOLS DON'T WORK! I am in an industry where I cannot just upgrade my toolchain or it's firmware without having to go back through regulatory compliance. I need stable tools and programmers, but with ST changing it all the time I am looking at switching vendors (away from ST).

ST needs to fix this NOW! All my boards worked in the past but this one and 3 others where the ST-Link firmware was forced to be upgraded are now completely useless. 

Does anyone know how to fix these boards and get them working again?

If I am not able to recover these boards, going forward we are not using ST anymore as their toolchain is unreliable.

[Tesla DeLorean]

I don't even understand WHY the ST-LINK firmware is changing like this, or needs to change.

Especially on boards that have more legacy STM32 that have been working fine, and don't have any particular problems.

SW QA is a serious problem, and degrades the overall experience.

[TonyFocusLCDs]

I do not know if this will solve the issue for anyone else, but I was able to recover my Nucleo boards.

On another computer with the latest versions of STM32CubeIDE and STM32CubeProgrammer I was able to reprogram the Nucleo boards I was having an issue with. I was able to down grade to the firmware version that was working using the STM32CubeProgrammer and tested programming some firmware to the boards. Then I used CubeProgrammer to update the ST-Link firmware to the latest version and test it - worked. 

Went back to the original computer where it first "bricked" my boards. Tried programming them from CubeIDE and CubeProgrammer and they did not work. I received the same errors as I originally posted. I updated CubeIDE and CubeProgrammer and still received the same errors.

I had to completely uninstall CubeIDE and CubeProgrammer, use a cleaning program to remove all traces, then reinstall the latest versions then I was finally able to use the original computer that "bricked" my boards.

Hope this helps someone.