stlinkserver.exe failing/exiting silently on Windows 11 (CubeProgrammer works fine)

[adelmgadmi]

Hi everyone,

I'm facing a really frustrating issue where my STM32CubeIDE can no longer detect my ST-LINK, and I've narrowed the problem down specifically to stlinkserver.exe failing to launch. This problem appeared completely randomly on my PC.

Here are the symptoms and what I have already ruled out:

The Problem: When I try to manually execute stlinkserver.exe via PowerShell to see what's wrong, it exits instantly without printing any output, errors, or logs. Even forcing the help menu or debug mode does absolutely nothing:

PowerShell

PS C:\Program Files (x86)\STMicroelectronics\stlink_server> .\stlinkserver.exe
PS C:\Program Files (x86)\STMicroelectronics\stlink_server> .\stlinkserver.exe -d 5
PS C:\Program Files (x86)\STMicroelectronics\stlink_server> .\stlinkserver.exe -h

Running Get-Process stlinkserver confirms the process is not running in the background at all. It just dies immediately upon execution.

What DOES work (Hardware & Drivers are fine):

• STM32CubeProgrammer works perfectly. It detects the ST-LINK and flashes the board without any issues.

• The board and ST-LINK work perfectly fine on another PC, so the hardware is not broken.

• My USB drivers are definitely fine and up to date (STSW-LINK009), confirmed by Device Manager and CubeProgrammer working.

What I have already tried:

• Reinstalling ST-LINK Server and STM32CubeIDE completely.

• Running PowerShell/IDE as Administrator.

• Replacing the libusb-1.0.dll file in the stlinkserver.exe folder with latest version and other older version but still same issue.

My System:

• Windows 11 (64-bit)

Has anyone experienced this specific silent crashing behavior with stlinkserver.exe? Are there any hidden dependencies (like specific C++ redistributables) or registry keys I should check? Any help would be greatly appreciated, as I am currently stuck!

Thanks in advance.

[S C]

Hello,

The stlinkserver dependencies expected on Windows are libusb-1.0.dll, libgcc_s_sjlj-1.dll, libwinpthread-1.dll. If one is missing, a system error message is expected (I checked for each of them). 32bits versions are expected, I have not checked what happens if one of them is patched by a 64bits version (could be an issue if you replaced libusb-1.0.dll by a 64bits version, but my understanding is that you had the issue before the replacement). I may suggest to reinstall from another source to compare, in case of corruption somewhere: ST-LINK-SERVER | Software - STMicroelectronics.

The file is digitally signed, I suggest to check if all certificates are installed on the machine (right click-properties-digital signature-details-view certificate-certificate path, status should be OK). In case of issue there, I also expected a status message from the system, but ...

The fact that it fails before the "-h" command execution is an interesting clue excluding issue with ST-Link hardware and driver, not involved in this stage of execution (if we exclude the loading of libusb.dll). There is however at this stage the initialization of the Winsock API which is perhaps somehow locked ? I have never heard about such kind of issue but it could also be a track to follow, perhaps linked to an anti-virus system not trusting the executable despite its signature ?

[Pavel A.]

>  When I try to manually execute stlinkserver.exe via PowerShell to see what's wrong, it exits instantly without printing any output, errors, or logs.

What is the exit status in these cases? use powershell command echo $LASTEXITCODE  or cmd command echo %ERORLEVEL%

Also, check whether another instance of stlinkserver.exe is not running in background, stuck for whatever reason.

[adelmgadmi]

I think it is a Winsock API error, 

I have this in winsock show catalog which is from another app I did uninstall it before. (LabView from National Instruments)

I tried deleting it from regedit and the moment I reboot, windows crashes and wont boot, I had to recover from a restore point.

Also, I found a dll file with the name nimdnsNSP.dll which I did delete it (only been able to inside safe mode)

>Also, check whether another instance of stlinkserver.exe is not running in background, stuck for whatever reason.

There isnt any.

[adelmgadmi · Accepted solution]

It's FIXED !!!!!!!!

It was indeed a winsock problem and I fixed it by installing a simple app called "complete internet repair" from Rizonesoft.

I selected these options and when it's done I rebootedmy pc and IT WORKED ! 

Thank you for trying to fix it with me, the winsock hint was very helpful.