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

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:

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

this post explains what that message means, why it appears, and how to fix it reliably — without just rebooting and hoping for the best.

What Is USBIPD?

USB/IP (USB over IP) allows USB devices connected to one computer to be accessed over a network. The usbipd-win project implements this for Windows, enabling WSL 2 (Windows Subsystem for Linux) to use USB devices like flash drives, Arduino boards, or RF dongles.

Usbipd runs as a Windows service in the background. When that service is stopped or not running properly, you’ll see the warning above.

What the warning indicates

  • usbipd is the service that manages USB device sharing on Windows.
  • The warning means the USBIP daemon service is not running — so commands like usbipd bind, usbipd list, or remote connections will fail.
  • The suggestion to reboot is because a reboot would normally start the service automatically (if it’s set to start automatically).

Frequently Asked Questions

1. Start the Service Manually (Admin Required)

Open PowerShell or Command Prompt as Administrator and run:

net start usbipd

If successful, you’ll see:

The usbipd service is starting.
The usbipd service was started successfully.

Now run usbipd list again—the warning should be gone.

Q: Is it safe to run the usbipd service all the time?

Yes. It consumes negligible resources and only activates when you use usbipd commands.

Conclusion

The warning usbipd warning the service is currently not running a reboot should fix that is rarely a cause for panic. In most cases, a simple reboot resolves it. When it doesn’t, manually starting the service, disabling Fast Startup, or performing a clean reinstallation will get you back on track.

Remember: usbipd-win is an invaluable tool for developers needing USB access in WSL 2—whether for flashing microcontrollers, using security keys, accessing serial devices, or working with external drives. Taking 10 minutes to properly diagnose and fix its service ensures hours of smooth development later.

If you have tried all the solutions above and still face the warning, open an issue on the official GitHub repository with your Windows version, WSL version, and output from:

sc query usbipd
usbipd version

With the steps outlined in this article, you can confidently resolve the "service not running" error and fully leverage USB device sharing between Windows and WSL 2.

Tags: usbipd, WSL 2, USB passthrough, Windows service, troubleshooting, Linux on Windows, developer tools

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 Fixing the “usbipd warning: the service is currently

The service may simply be set to manual start or failed to trigger. Open an Administrator PowerShell or Command Prompt. Run the command: sc.exe start usbipd.

Alternatively, open the Services app (services.msc), locate USBIP Device Host, and ensure its "Startup type" is set to Automatic. 2. Address Driver Interference

A common cause of this error is a conflict with other virtualization software, specifically VirtualBox.

VirtualBox Conflict: usbipd-win uses the VBoxUsbMon driver. If a full version of VirtualBox is installed, its own drivers may interfere.

Force Restart Drivers: You can try stopping and restarting the specific drivers manually: sc stop usbipd sc stop VBoxUSBMon sc start VBoxUSBMon sc start usbipd 3. Reinstall via WinGet

Many users report that standard MSI installers occasionally fail to register the service correctly. A clean reinstall via the Windows Package Manager (winget) often fixes persistent service errors. Uninstall: winget uninstall --id=dorssel.usbipd-win -e Install: winget install --id=dorssel.usbipd-win -e 4. Check WSL Prerequisites

If using this for WSL2, ensure your environment meets the minimum requirements:

Kernel Version: You need Linux kernel version 5.10.60.1 or higher. Check yours with uname -a in WSL.

Update WSL: Run wsl --update from an admin prompt followed by wsl --shutdown to ensure the latest features are active. Troubleshooting Checklist

Check Event Log: If the service crashes on start, check the Windows Event Log under "Application" for specific error codes or crash reports.

Firewall Rules: Ensure TCP port 3240 is open, as the service communicates over this port.

Path Conflicts: Ensure there isn't another sc.exe or usbip executable in your PATH environment variables that might be intercepting commands.

usbipd: error: Server is currently not running. #122 - GitHub

Understanding usbipd and Its Importance

usbipd is a daemon that facilitates the use of USB devices over IP networks. This means you can access and use USB devices connected to another computer on the network as if they were directly connected to your own computer. This can be particularly useful in various scenarios, such as: What the warning indicates

  • Virtualization Environments: In virtualized environments, passing through USB devices directly to virtual machines can sometimes be cumbersome or not straightforward. USB over IP provides a solution to access USB devices within such environments.
  • Remote Access: For remote workers or IT support personnel, being able to access USB devices remotely can enhance productivity and facilitate troubleshooting.
  • Device Sharing: It enables sharing of USB devices across different operating systems and physical locations, making it a versatile tool in networked environments.

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

When you encounter the warning message stating that the usbipd service is not running and suggesting a reboot, it typically indicates that the service has stopped or was not properly started. Several factors can lead to this situation:

  1. System Boot Issues: Sometimes, services fail to start properly during system boot due to dependency issues, configuration errors, or resource constraints.
  2. Software or Driver Conflicts: Conflicts with other software or drivers can cause services like usbipd to malfunction or fail to start.
  3. Configuration Errors: Misconfiguration in the service settings or USB device settings can prevent the service from running correctly.

Resolving the Issue

To resolve the issue of usbipd not running, follow these steps:

  1. Reboot the System: As suggested by the warning, a simple reboot can often resolve the issue, especially if it's a transient problem or a dependency that needs to be started.

  2. Check Service Status: After rebooting, check the status of the usbipd service to see if it's running. You can usually do this with a command like systemctl status usbipd on systems using systemd.

  3. Enable and Start the Service Manually: If the service is not running, you can try to start it manually with systemctl start usbipd and enable it to start on boot with systemctl enable usbipd.

  4. Check Logs: If the service fails to start, check the system logs (e.g., using journalctl on systemd-based systems) for any error messages related to usbipd. These can provide clues about why it's not running.

  5. Reinstall or Update Software: If usbipd was working previously and you've recently made changes to your system, such as updating software, consider reinstalling usbipd or reverting to a previous version if possible.

  6. Consult Documentation and Community Forums: If none of the above steps resolve the issue, consult the documentation for usbipd, as well as community forums or support channels. There might be known issues or specific fixes for your particular situation.

Conclusion

The usbipd service plays a valuable role in enabling the use of USB devices over IP networks. When faced with the warning that the service is not running, a methodical approach to troubleshooting can usually resolve the issue. By understanding the service's role, identifying potential causes for its failure to run, and systematically addressing these causes, users can restore functionality and continue to benefit from the convenience and flexibility that usbipd offers.

This error message typically occurs when the background service for usbipd-win (often including the VBoxUsbMon

driver) has failed to start or was interrupted. While a reboot is the simplest fix, you can often resolve this by manually restarting the service through Windows tools. Immediate Fix: Manual Service Restart Before rebooting, try to force-start the service using an Administrator PowerShell Stop any existing instances: powershell sc.exe stop usbipd sc.exe stop VBoxUsbMon Use code with caution. Copied to clipboard Start the services in order: powershell sc.exe start VBoxUsbMon sc.exe start usbipd Use code with caution. Copied to clipboard If successful, you should be able to run usbipd list without the warning. Common Troubleshooting Steps Check Service Status: services.msc ) and find USBIP Device Host

. Ensure its status is "Running" and Startup Type is set to "Automatic". VirtualBox Interference: If you have VirtualBox installed, its version of the VBoxUsbMon driver might conflict with the one used by usbipd-win usbipd is the service that manages USB device

. Closing VirtualBox or updating it can sometimes resolve the conflict. Repair Installation:

If the service consistently fails to start, the registry entries or driver files may be corrupted. Download the latest official usbipd-win GitHub Run the installer and select Check Windows Event Log: If the service crashes immediately upon starting, check the Windows Event Viewer Windows Logs > Application . Look for "Error" entries from the source for specific crash codes.

Fix: "usbipd warning: the service is currently not running" If you're seeing the error "usbipd warning: the service is currently not running; a reboot should fix that" while trying to attach USB devices to WSL2, you aren't alone. While a reboot often works, there are faster ways to get back to work without a full system restart. 1. Manually Start the Service (Fastest Fix)

The most common cause is that the usbipd Windows service failed to start automatically. You can force it to start using an Administrator PowerShell window: powershell sc.exe start usbipd Use code with caution. Copied to clipboard Alternatively, you can use the Windows Services Manager: Press Win + R, type services.msc, and hit Enter. Find USBIP Device Host in the list. Right-click it and select Start.

Ensure Startup type is set to Automatic to prevent this in the future. 2. Verify for Driver Conflicts

If the service starts but the error persists when you try to attach, check for software conflicts:

VirtualBox Conflict: usbipd-win uses drivers that can conflict with a full installation of VirtualBox. If you have both, try stopping VirtualBox services before using usbipd.

SC Executable Path: Ensure you are calling the official Windows service manager. If you have other sc tools in your PATH, try running the full path: $env:windir\system32\sc.exe query VBoxUsbMon. 3. Reinstall via Winget

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

How to Avoid This Warning in the Future

  • Set usbipd to start automatically (as shown above).
  • Always run USBIPD commands in an admin terminal—even listing devices may trigger the service to auto-start in newer versions.
  • Keep usbipd-win updated to the latest version; newer builds handle service startup more gracefully.
  • If you use WSL frequently, consider adding net start usbipd to a startup script (though automatic startup is cleaner).