Usbipd Warning The Service Is Currently Not Running A Reboot Should Fix That

Understanding and Fixing the USBIPD Warning: "The service is currently not running"

If you’ve started using usbipd-win (a popular tool for sharing USB devices from Windows to WSL 2 or other virtual machines), you may have encountered this warning when running the usbipd list command:

The warning "usbipd: warning: The service is currently not running; a reboot should fix that" typically indicates that the usbipd (USBIP Device Host) service or its required drivers failed to initialize properly. While a reboot is the recommended first step, several alternative fixes can resolve the issue without a full system restart. 1. Manually Start the Service Understanding and Fixing the USBIPD Warning: "The service

If Repair fails, Uninstall it completely, reboot, and perform a fresh installation. Summary Table: Troubleshooting Checklist Why it works Start usbipd in Services.msc Fixes a service that simply failed to trigger at boot. Admin PowerShell Restart Overrides standard user permission blocks. Update to latest release Fixes bugs related to Windows/WSL kernel updates. Check Port 3240 Ensures no network conflicts are killing the host. Uninstall usbipd via Windows Settings > Apps >

Fix 2: Manually Start the USBIPD Service (No Reboot Required)

You can start the service immediately without restarting Windows. (If it says no drivers found, that is fine)

1. Uninstall usbipd via Windows Settings > Apps > Installed Apps.
2. Open Device Manager again (View > Show hidden devices).
3. Right-click and uninstall any device listed under "USB/IP" or "USBIP". Check the box that says "Attempt to remove the driver for this device" if available.
4. Crucial Step: Open PowerShell (Admin) and check the system driver store. Run:

   pnputil /delete-driver usbip_vhci.inf /uninstall /force
   

   (If it says no drivers found, that is fine).
5. Restart your computer. (I know, I know, but this is the last time).
6. Install the latest version of usbipd-win (using winget install --interactive --exact dorssel.usbipd-win is the recommended method).
7. Open a fresh PowerShell (Admin) and run usbipd list.

: If the service fails with "Error 1068," it means a dependency (like the driver) failed to start. Registry Corruption