Usbipd Warning The Service Is Currently Not Running A Reboot Should Fix That May 2026
Fixing the “usbipd warning: the service is currently not running — a reboot should fix that” on Windows
If you’ve been using USB/IP on Windows (for example, to share USB devices between WSL2 and the host using usbipd-win) and you see the warning:
Step-by-Step Fixes: From Basic to Advanced
Fix 1: The Obvious (But Often Incorrect) Reboot
Go ahead and restart your computer. After rebooting, open PowerShell or Command Prompt as Administrator and run: Fixing the “usbipd warning: the service is currently
The "usbipd: warning: The VBoxUsbMon driver is currently not running" error indicates that the service for sharing USB devices with WSL2 has failed or a dependency is unresponsive, often caused by VirtualBox conflicts, upgrade issues, or required driver binding reboots. A manual service restart via PowerShell, or in some cases a re-installation of the software, generally resolves the issue. For comprehensive troubleshooting steps, visit the usbipd-win GitHub Wiki Ensure WSL is installed and updated: wsl --update
If you are using usbipd-win for WSL2, ensure your environment is ready: Update usbipd-win to a version compatible with your
3. Reinstall the DriverIf the service is running but WSL still can't see devices: Uninstall USBIPD from Settings > Apps. Reinstall the latest version. 💡 Pro Tip: WSL Check
Are you having trouble binding a specific device once the service is actually up and running?
- Ensure WSL is installed and updated:
wsl --update wsl --status - Update usbipd-win to a version compatible with your WSL2/Windows build.
- If the driver failed to load, Device Manager may show unknown devices or driver install failures—reinstall the driver or run:
and check for usbip-related drivers, then remove/reinstall as needed.pnputil /enum-drivers
This content is structured to explain the "why," provide the immediate solution, troubleshoot persistent issues, and offer best practices for developers and sysadmins using USBIPD-WSL.