This is a very common error when setting up USBIPD on Windows to pass devices (like USB drives or webcams) into WSL2. It is frustrating because it implies a simple restart will solve it, but often it does not.
Since you mentioned a "long post," I will provide a comprehensive troubleshooting guide. This covers why this happens and the step-by-step fixes to resolve it without rebooting every time.
Antivirus, anti-malware, or Windows Defender may block the usbipd service from starting because it interacts directly with hardware (USB controllers).
If you are a developer working with Windows Subsystem for Linux (WSL 2) and need to attach USB devices from your Windows host directly into your Linux environment, you have likely encountered usbipd-win. This open-source project allows you to share USB devices connected to Windows with WSL 2 instances. This is a very common error when setting
However, a common and frustrating roadblock appears when running the command:
usbipd wsl list
Or any other usbipd command, only to be greeted with the warning:
usbipd warning the service is currently not running a reboot should fix thatOr any other usbipd command, only to be
This message can be confusing, especially if you have already installed the software correctly. Is a reboot really necessary? What if rebooting doesn't work? Why is this happening in the first place?
This article will explain what this warning means, why it appears, and—most importantly—how to permanently fix it so you can get back to working with your USB devices in WSL.
C:\Program Files\usbipd-win (if exists).sc delete usbipd
After reinstall and reboot, verify the service is running: usbipd warning the service is currently not running
sc query usbipd
Go ahead and restart your computer. After rebooting, open PowerShell or Command Prompt as Administrator and run:
usbipd list
If the warning persists, proceed to the next fixes.
services.msc.usbipd → Properties → Dependencies tab.Plug and Play, Remote Procedure Call (RPC)).