Unable to load to Nucleo board

[Dabbo]

Scenario:

Windows 11 connected to Nucleo-L476RG.
Fresh install of STMCubeIDE
Version: 1.14.0
Build: 19471_20231121_1200 (UTC)
OS: Windows 11, v.10.0, x86_64 / win32

Ran STLinkUpgrade 3.13.4
Result: Update to Firmware: V2J43M28 STM Debug+Mass storage+VCP Upgrade successful.

File > New STM Project
Selected board L476RG
Project name testtest
Initialised all peripherals with default.

Configurator opened main.c
Project > Build Project
11:30:19 Build Finished. 0 errors, 0 warnings. (took 3s.143ms)

Error in final launch sequence:
Failed to start GDB server
Failed to start GDB server
Error in initializing ST-LINK device.
Reason: (0) Unknown. Please check power and cabling to target.

Failed to bind to port 61235, error code -1: No error
Failure starting SWV server on TCP port: 61235
Failed to bind to port 61234, error code -1: No error
Failure starting GDB server: TCP port 61234 not available.
Shutting down...
Exit.

My question:

The cable is a known good one, and the STLink upgrade was successful, so it seems to me that there is nothing wrong with

[Dabbo]

By the way, I know both my Nucleo board and the cable are good as they work on my Linux machine

[STTwo-32]

Hello @Dabbo 

I suggest you to take a look at this post. It may be helpful.

Best Regards.

STTwo-32 

[Dabbo · Accepted solution]

Solved! And I think I know what the problem might be.

From the Windows "Add & Remove Programs" menu I removed anything with ST in the name and did another fresh installation. This time I got the message "Do you want to allow public and private networks to access this app? Windows Firewall has blocked some features of st-link_gdbserver.exe on all public and private networks".

I have not seen this message before.

I clicked "Allow" and the installation continued, and now it works.

Another Sunday wasted - ho-hum

ADDED LATER: on reflection, in the process of uninstalling I uninstalled 2 versions of STMCubeIDE as well as one STLink file. It's possible the problem was related to that, as per the links above. Either way, a complete uninstall / reinstall fixed it