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

  • Inspect the event log for errors

  • Check dependencies and privileges

  • Reinstall or repair usbipd-win

  • Confirm kernel-mode driver and WSL integration (if using WSL2)

  • Check antivirus or endpoint protection

  • Use system file checks if corruption is suspected

    sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

  • As a last resort — reboot

    • If you are working with USBIPD-WSL (USB over IP for Windows Subsystem for Linux), you have likely encountered the frustrating yellow warning:

    "The service is currently not running. A reboot should fix that." Inspect the event log for errors

    This message typically appears when you attempt to list (usbipd list) or attach (usbipd attach) a USB device from a PowerShell terminal. While the error message suggests a simple reboot, simply restarting your computer every time you need to plug in a USB device is an inefficient workflow.

    In this guide, we will break down exactly why this service fails to start, how to fix it without a reboot, and how to prevent it from happening in the future.

    Sometimes the warning appears because you are running usbipd from within WSL instead of Windows. Remember:

    Correct usage:

    # In Windows (Admin recommended)
usbipd wsl list
usbipd wsl attach --busid <busid>

    If you mistakenly run usbipd inside WSL, you will get a "command not found" or this misleading warning.

    You can start the service immediately without restarting Windows.

  • Once running, set its startup type to Automatic (right-click > Properties).

    • Alternative via Command Line (Admin):

    net start usbipd

    Or using PowerShell:

    Start-Service -Name usbipd

    After starting, verify:

    usbipd list

    You should now see connected USB devices instead of the warning.