ST-LINK USB driver for Windows 11

[Mparikh06]

Is there ST-Link V2 driver for Windows 11? I am using Microsoft Surface Pro + Copilot and trying to load code on STM32L476.

[S C]

Unfortunately you are not the only one suffering (I am suffering too, and I would say, perhaps at first ?). Maybe it's precisely because of big companies involving legal and business aspects over technical ones that the issue occurs and is still not solved ? The first point is that the digital signature through a third-party certificate is not accepted by Windows ARM machines to install drivers, while it works for all previous systems. Microsoft support confirmed me that it is a voluntary policy change. So the ST-Link "drivers" updated for Windows ARM64 and signed with a Digicert cross-certificate are not accepted (trusted) by Windows. The irony is that we don't install a real driver, only descriptors for a device relying on WinUSB (=Microsoft driver natively present on those machines). Then the hell is in the details of the new procedure ...

"Fortunately" this issue impacts "only" the old generations of ST-Link (V2 and V2-1). "Unfortunately" we still produce lots of boards with it. Since V3 generation we implemented another solution, but which can't be retro-actively applied to V2 and V2-1. The topic here shows also the difficulties to maintain something over decades (ST-Link/V2 = 2010) while things evolve around

[KhPaul]

Fortunately, I don’t use st-link v2 at all, my devices is st-link v3, v3 mini and v3 pwr. Have I understood you correctly, there are windows 11 arm drivers for them?

[S C]

No "driver" is required for ST-Link/V3 generation on Windows (even ARM versions). More precisely, it is not necessary to install the .inf descriptors to have the device recognized. WinUSB is expected to be natively present on Windows 11 even on ARM64 machines. The only impact is that without the .inf files, the COM port names are not customized with ST names (and keep their system-attributed standard name, which makes them more difficult to identify, I admit, but functional anyway). If you are not asking for ST-Link/V2 drivers for Windows ARM, please precise the issues you face with ST-Link/V3, most probably they are not related with the initial description of this topic

[SNish]

Thanks s c
At this moment I am using Nucleo-board for teaching seminar.
And I can use ST-LINK/V2 of this parts with ARM64/Windows11 note for debug. 
It can use with openocd gdbserver. And WinUSB driver .

I am planning to enhance seminar using with CubeMonitor and CubeProgrammer.
These tools does not accept WinUSB port.
It is current pending issue for me. (Not big issue)

[S C]

@SNish,

I guess you disabled some protections at windows11 level and adapted the inf files to have the ST-Link/V2 enumerated on your machine, didn't you ? If the device enumerated and works with openocd gdbserver, I think it should work also with CubeProgrammer at least (it uses the same USB interface; could be a bug at CubeProgrammer level instead). It looks like there are many different issues in this context ...

[Pavel A.]

@S C I thought as well that ST-Link is simply a winusb device, but the INF files that come with  CubeProgrammer install also a custom device interface. This suggests that CubeProgrammer looks for this device interface GUID. To install it by standard means AFAIK a signed INF is needed anyway. Tricks like zadig won't work on ARM PCs because of tighter signing requirements.

So maybe ST should go forward and do whatever is takes with Microsoft to add the ARM support properly.

; stlink_dbg_winusb.inf
..........
[Standard.NTamd64]
%DeviceName% =USB_Install, USB\VID_0483&PID_3748
%DeviceName% =USB_Install, USB\VID_0483&PID_374A&MI_00
%DeviceNameUsbLoader% =USB_Install, USB\VID_0483&PID_374D
.........

[USB_Install.HW]
AddReg=Dev_AddReg

[USB_InstallRW.HW]
AddReg=Dev_AddRegRW

[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,%STLink_GUID%

[Dev_AddRegRW]
HKR,,DeviceInterfaceGUIDs,0x10000,%STLink_GUID_RW%


[Strings]
DeviceName="STMicroelectronics STLink dongle"
DeviceNameRW="STMicroelectronics STLink dongle RW"
DeviceNameUsbLoader="STMicroelectronics STLink USB Loader"
........
STLink_GUID="{DBCE1CD9-A320-4b51-A365-A0C3F3C5FB29}"
STLink_GUID_RW="{8326506F-7260-4854-9C03-26E416F04494}"

[KhPaul]

Why I should disable protection to make an original ST device I bought work with windows for ARM? It is ridiculous, isn't it? And try to do this trick to stlink-v3-pwr I mostly work with. That respectfull company like ST can't deal with Microsoft?

[S C]

@Pavel A. : the ST Debug interface GUID is integrated into the WinUSB descriptors embedded at device side on STLINK-V3, that's why inf file installation is not mandatory. Moreover it has been validated with CubeProgrammer on Windows ARM. I hope there is not another surprise to discover there, depending on the machine and/or system updates ...

@KhPaul : you don't need to install any driver for STLINK-V3 devices, including STLINK-V3PWR. Please describe in more details the failures you are facing, starting with the versions of tool, firmware and system. There is no evidence with your previous post that you are facing issues related with ST-Link driver for Windows ARM. If you suspect issues with device identification by the system, please precise what you see in the device manager after you plugged it.

[Pavel A.]

Very glad to know this, but the OP has ST-LINK v2.