Windows 10 esp-prog libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

I have the debugger working on my windows 11 laptop but it fails on Windows 10.
pio upgrade shows PlatformIO 6.1.6 is currently the newest version available.
Zadig shows WinUSB (v6.1.7600.16385) installed.
platformio.ini shows

platform = espressif32
board = az-delivery-devkit-v4
framework = arduino
monitor_speed = 115200
lib_deps = marvinroger/AsyncMqttClient@^0.9.0
debug_tool = esp-prog
debug_init_break = tbreak setup
Builds without errors
but debug console shows:-

Open On-Chip Debugger v0.11.0-esp32-20220706 (2022-07-06-15:48)
Licensed under GNU GPL v2
For bug reports, read
adapter speed: 20000 kHz
WARNING: boards/esp-wroom-32.cfg is deprecated, and may be removed in a future release.
adapter speed: 5000 kHz
Info : tcl server disabled
Info : telnet server disabled

Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

Info : clock speed 5000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: esp32.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Unexpected OCD_ID = 00000000
Warn : target esp32.cpu0 examination failed
Error: Unexpected OCD_ID = 00000000
Warn : target esp32.cpu1 examination failed
Info : starting gdb server for esp32.cpu0 on pipe
Info : accepting ‘gdb’ connection from pipe
Error: Target not examined yet
Error executing event gdb-attach on target esp32.cpu0:
Warn : No symbols for FreeRTOS!
Error: Target not halted
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use ‘gdb_memory_map disable’.
Error: attempted ‘gdb’ connection rejected
Error: error during select: Unknown error
.pioinit:11: Error in sourced command file:
Remote communication error. Target disconnected.: Success.
Anybody got any ideas?

That doesn’t really matter because it does find the right USB interface afterwards. It tries all matching VID/PIDs and reports this error even if it find the right devic ein the next iteration.

Your real problem is

This usually indicates wrong wiring, debug_speed = .. to high in the platformio.ini or not set, too long / bad cables or power problems. Please try and do everything exactly as Low-cost ESP32 In-circuit Debugging | by Manuel Bl. | Medium.

Thanks Max that article you pointed me to was very usefull. The explanations are great. After double checking everything reducing speed still no joy but I thought I might give it a bit more power using a power adaptor and a hub on the USB line to the ESP32 and that was it. Not enough power. I got stuck on why it would work from my laptop but not the desktop. All good now thanks amillion