Usbipd Warning The Service Is Currently Not Running A Reboot Should Fix That (Full Guide)

A Complete Guide to Understanding, Fixing, and Preventing the USB/IP Service Failure

If you are a developer, system administrator, or advanced Windows user working with the Windows Subsystem for Linux (WSL 2), you have likely encountered the usbipd tool. This powerful utility allows you to attach physical USB devices from your Windows host directly into a Linux distribution running under WSL.

However, a common and frustrating error message can appear when you try to list or bind USB devices:

"usbipd warning: the service is currently not running. a reboot should fix that"

While the message itself suggests a simple reboot, the underlying issue can be more nuanced. This article will dissect the warning, explain why it occurs, provide step-by-step solutions beyond a simple restart, and teach you how to prevent it from recurring.

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."

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. A Complete Guide to Understanding, Fixing, and Preventing

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.

If none of the above works, the installation may be corrupted.

Once you resolve the issue, prevent it from recurring with these best practices:

The message “The service is currently not running; a reboot should fix that” is a bit misleading—it’s a safe, generic suggestion, but not the fastest. In most cases, manually starting the service with net start usbipd as Administrator will resolve the issue in seconds.

Only reboot if the service refuses to start or you’re about to restart anyway. Understanding this will save you time and frustration when working with USB passthrough on WSL 2.

Quick reference
Fix without reboot:
net start usbipd (as Admin)

Fix permanently:
Set-Service -Name usbipd -StartupType Automatic "usbipd warning: the service is currently not running

Happy USB sharing!

The warning "usbipd: error: The service is currently not running; a reboot should fix that"

usually indicates that the Windows background service responsible for sharing USB devices is stopped or was never started after installation

. While a reboot is the simplest fix, you can often resolve this immediately by manually starting the service. Quick Fix: Restart the Service Manually You can start the service using Command Prompt PowerShell

with Administrator privileges to avoid a full system reboot. Open Terminal as Admin : Right-click the button and select Terminal (Admin) PowerShell (Admin) Start the Service : Run the following command: sc.exe start usbipd Verify Status : Ensure it is running by typing: sc.exe query usbipd should show 4 RUNNING Step-by-Step Troubleshooting Guide

If the service fails to start or the error persists, follow these steps to identify and fix the underlying issue. 1. Check Service Startup Type

service is designed to start automatically on Windows boot. If it is disabled, it will trigger this error. services.msc USBIP Device Host in the list. Right-click it and select Properties Startup type . If it is "Stopped," click 2. Resolve Driver Conflicts usbipd-win tool relies on drivers like VBoxUsbMon . If you have a full installation of VirtualBox , it may conflict with the usbipd-win : Try a "Repair" installation. Download the latest official GitHub releases and run the installer again, selecting 3. Update WSL and Drivers While the message itself suggests a simple reboot,

This warning typically appears when using usbipd-win, a tool often used to pass through USB devices from Windows to the Windows Subsystem for Linux (WSL2).

While a reboot sometimes resolves temporary driver conflicts, it often doesn't solve the underlying issue if the service fails to start automatically or is blocked by other software. Understanding the Warning

The error "usbipd warning: the service is currently not running" means the USBIP Device Host service on your Windows host has stopped. Without this service, the command-line tool cannot communicate with your USB hardware or share it with your WSL instance. Immediate Troubleshooting Steps

If a reboot did not fix the problem, follow these steps to manually restore the service: 1. Manually Start the Windows Service

The service is designed to start automatically, but you can force it to run via the Services app: Press Win + R, type services.msc, and hit Enter. Look for USBIP Device Host in the list. Right-click it and select Start. If it’s already running, try Restart. Pro Tip: Ensure the "Startup type" is set to Automatic. 2. Reinstall Using Winget (Recommended Fix)

Many users find that a "clean" installation via the Windows Package Manager resolves persistent service issues where standard MSI installers fail. Open PowerShell as an Administrator. Run the following commands: powershell winget uninstall usbipd winget install dorssel.usbipd-win Use code with caution.

This often fixes broken paths or driver registration issues that a reboot cannot touch. 3. Resolve VirtualBox Conflicts

If you have VirtualBox installed, it may conflict with the VBoxUsbMon driver used by usbipd-win. Check if VirtualBox is running and try closing it.

Some users report that reinstalling VirtualBox or updating to the latest version of usbipd-win resolves this specific driver clash. 4. Update the WSL Kernel