usbipd: warning: USB filter 'USBPcap' is known to be incompatible -- what is the exact symptom of incompatibility? about usbipd-win HOT 3 CLOSED

The problem is that VBoxUSBMon is not able to dynamically switch the device ID (which is how it "grabs" the device in order to use the stub driver). Technically, it is an incompatibility between USBPcap and VBoxUSBMon. The workaround is to setup the device to permanently use the stub driver (this is what --force does). Downside: Windows cannot use the device anymore (until you unbind).

I think USBPCap does in fact still work when you use --force. If not, you can use usbipd-win itself for the captures, see https://github.com/dorssel/usbipd-win/wiki/Troubleshooting. The resulting captures are Wireshark compatible.

from usbipd-win.

So what you say is that I actually don't need USBPcap in the situation I already have usbipd.
USBPcap can only snoop one root hub at a time, does the trace mode of usbipd trace all hubs at once? I hope it won't result in way too much traced traffic... Does usbipd trace string descriptor requests, unlike usbpcap? I'm afraid the tracing functionality is geared for debugging usbipd, whereas usbpcap is geared for generic usb traffic tracing. Maybe that purpose makes it not trace things that a generic USB traffic analysis would be interrested in. On the other hand, usbpcap doesn't trace everything either... Linux usbmon is probably better for me.

from usbipd-win.

usbipd-win only captures devices that are attached via usbipd-win. It captures all URBs for those devices.

from usbipd-win.