libwdi does not work under Windows 11 ARM64, but there is a workaround here.
Somehow libusbK does not work with WinUSB driver installed this way under Windows 11 ARM64.
libusbK 3.1.0.0 release.
PS C:\work\libusb\libusbK\libusbK-3.1.0.0-bin\bin\exe\amd64> .\kList.exe
Loading USB ID's maintained by Stephen J. Gowdy <linux.usb.ids@gmail.com>..
No devices found.
PS C:\work\libusb\libusbK\libusbK-3.1.0.0-bin\bin\exe\amd64> .\kBench.exe list
Error:[main] device list empty.
Press any key to exit..
libusbK git
PS C:\work\libusb\libusbK\libusbK\libusbK\bin\Release\kList\ARM64> .\kList.exe
Loading USB ID's maintained by Stephen J. Gowdy <linux.usb.ids@gmail.com>..
No devices found.
PS C:\work\libusb\libusbK\libusbK\libusbK\bin\kBench\ARM64\Release> .\kBench.exe list
Error:[main] device list empty.
Press any key to exit..
libusb-1.0 Windows works fine.
PS C:\work\libusb\libusb> .\build\v143\ARM64\Release-Hotplug-MT\xusb.exe 04b4:8613
Using libusb v1.0.30.12032
Opening device 04B4:8613...
Reading device descriptor:
length: 18
device class: 255
S/N: 0
VID:PID: 04B4:8613
bcdDevice: A001
iMan:iProd:iSer: 0:0:0
nb confs: 1
Reading first configuration descriptor:
total length: 171
descriptor length: 9
nb interfaces: 1
interface[0]: id = 0
interface[0].altsetting[0]: num endpoints = 0
Class.SubClass.Protocol: FF.FF.FF
interface[0].altsetting[1]: num endpoints = 6
Class.SubClass.Protocol: FF.FF.FF
endpoint[0].address: 01
max packet size: 0200
polling interval: 00
endpoint[1].address: 81
max packet size: 0200
polling interval: 00
endpoint[2].address: 02
max packet size: 0200
polling interval: 00
endpoint[3].address: 04
max packet size: 0200
polling interval: 00
endpoint[4].address: 86
max packet size: 0200
polling interval: 00
endpoint[5].address: 88
max packet size: 0200
polling interval: 00
interface[0].altsetting[2]: num endpoints = 6
Class.SubClass.Protocol: FF.FF.FF
endpoint[0].address: 01
max packet size: 0040
polling interval: 01
endpoint[1].address: 81
max packet size: 0040
polling interval: 01
endpoint[2].address: 02
max packet size: 0200
polling interval: 01
endpoint[3].address: 04
max packet size: 0200
polling interval: 00
endpoint[4].address: 86
max packet size: 0200
polling interval: 01
endpoint[5].address: 88
max packet size: 0200
polling interval: 00
interface[0].altsetting[3]: num endpoints = 6
Class.SubClass.Protocol: FF.FF.FF
endpoint[0].address: 01
max packet size: 0040
polling interval: 01
endpoint[1].address: 81
max packet size: 0040
polling interval: 01
endpoint[2].address: 02
max packet size: 0200
polling interval: 01
endpoint[3].address: 04
max packet size: 0200
polling interval: 00
endpoint[4].address: 86
max packet size: 0200
polling interval: 01
endpoint[5].address: 88
max packet size: 0200
polling interval: 00
Kernel driver attached for interface 0: (not supported)
Claiming interface 0...
Reading string descriptors:
Reading OS string descriptor: no descriptor
Reading interface association descriptors (IADs) for first configuration:
nb IADs: 0
Releasing interface 0...
Closing device...
libwdi does not work under Windows 11 ARM64, but there is a workaround here.
Somehow libusbK does not work with WinUSB driver installed this way under Windows 11 ARM64.
libusbK 3.1.0.0 release.
libusbK git
libusb-1.0 Windows works fine.