Attach Request for <busID> failed - Device in error state

[jellyfish-headphones]

Hello there! I'm not sure if this is an error with usbipd, my card reader, or WSL. But I'm hoping I could get some assistance.

My team uses card readers to authenticate across networks to get our work done. Today, Attaching my OMNIKEY 3x21 card reader to WSL via Powershell stopped working. It was working earlier, as well as every day, multiple times a day, for the last several weeks. Not sure what changed. This isn't happening to anyone else on my team, and we all use the same card reader and authentication methods.

I'm using Windows 10, usbipd 4.2.0.

Here's my whole process:
0. Check the device in Device Manager, confirm it is working properly and says its connected.

1. Bind the card reader
2. Attach the card reader
3. Double check that it's in WSL via lsusb
4. Try to use my card reader, I'll get agent refused operation
5. Go back to WSL and unbind, try to bind and attach again, it says Attach request failed ... device in error state. After doing this, the card reader isn't read by Windows or WSL.
6. Unplug the card reader, plug it back in, bind/attach, etc. Attach request failed ... device in error state
7. Try it in a different USB port and try from step 1 with the same results.

Some other things I've tried:

• restarting my machine
• stopping/starting usbipd
• uninstalling/reinstalling usbipd
• trying others' card readers
• saying please, etc.

Please let me know if you need any more information. Thank you.

[dorssel]

First of all, binding is an administrative operation, it doesn't actually do anything with the device. You need to do it only once to tell usbipd-win that it may you the device (with attach) at all. So the unbind/rebind isn't going to help.

Then I have a question: do you need to ever use the device on Windows at all? Or only within WSL?

For now, the best way to go is: reboot, in Windows device manager "uninstall" the device (it will remove the driver), then unplug and replug it in. This should let Windows rediscover the device from scratch and "reset" everything.