Frans van Dorsselaer

You really need to execute the following instructions: https://github.com/dorssel/usbipd-win/wiki/WSL-support#usbip-client-tools. This is also what the error says (and it says it for a reason...)

The specific mention of Windows 11 originates from Microsoft, in their original article https://devblogs.microsoft.com/commandline/connecting-usb-devices-to-wsl/. At the time a) they wanted to push Windows 11, and b) the WSL2 kernel for...

The short answer is: yes, this is possible,

What OS version are you using? Is the user part of the administrator group (and is elevation sufficient), or is it a standard user (which would require a request for...

From https://www.kernelconfig.io/config_joystick_xpad it looks like you need a special driver (xpad), which needs to be enabled in the kernel (which it isn't in the default WSL kernel). Follow https://github.com/dorssel/usbipd-win/wiki/WSL-support#building-your-own-usbip-enabled-wsl-2-kernel and...

And you may also like https://www.kernelconfig.io/CONFIG_JOYSTICK_XPAD_FF

"Device busy" means exactly what it says. Looks like something on the host (service/software/driver) is holding an exclusive lock. Either stop that service/software, or use `usbipd bind --force`.

@Diztruxion Has your problem been resolved?

WSL instances are *per user*. This means that only the original user can access the original distros. If you want your temporary user to use WSL, you will have to...

This is unrelated to `usbipd-win`, which doesn't do anything with your profile. And I've also never heard of WSL messing with the user profile either, but you could ask the...