When using usbipd-win, the warning "The service is currently not running; a reboot should fix that" usually indicates that the background service responsible for managing USB/IP connections—often specifically the VBoxUsbMon driver—has failed to start automatically after installation or a system change. Core Issue: Service Failure
The usbipd command relies on a Windows service that should be set to "Automatic Start". If this service is inactive, the software cannot bridge your USB devices to the WSL environment. Common Root Causes
Driver Interference: If you have a full installation of VirtualBox, it may clash with the VBoxUsbMon service used by usbipd-win.
Pending Driver Initialization: Some driver updates, especially after using the --force flag, require a full system restart to properly bind the device to the usbipd stub driver.
Installation Glitches: Standard MSI installers sometimes fail to register the service correctly; users frequently report that a clean install via winget resolves the issue. Recommended Troubleshooting Steps
Verify Service Status: Open an Administrator PowerShell and check if the service is registered and running by using the Windows Service Manager command:sc query VBoxUsbMon or sc query usbipd. Manual Start: Try to force-start the services manually: sc start VBoxUsbMon sc start usbipd.
Check Event Logs: If the service fails to start, check the Windows Event Viewer (Application logs) for crash reports or dependency errors.
Reinstall via Winget: If a reboot fails, a "clean" reinstall is often the most effective fix. Run these commands in an Admin terminal: winget uninstall usbipd winget install usbipd.
Disable Core Isolation: In some cases, Windows "Core Isolation" security features can block the necessary drivers from loading.
If you've already rebooted and the warning persists, would you like the specific Event Viewer path to find the exact error code?
usbipd is the service that manages USB device sharing on Windows.usbipd bind, usbipd list, or remote connections will fail.eventvwr.msc).These logs can reveal the root cause, such as a missing DLL or an access violation.
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
Happy USB sharing!
The usbipd warning "the service is currently not running" is a common roadblock for developers using WSL2 (Windows Subsystem for Linux) who need to bridge physical USB hardware to their Linux environment. While the error message suggests a reboot as a catch-all fix, the issue is usually rooted in the Windows Service layer rather than a deep system failure. The Source of the Error
The usbipd-win tool operates as a background service on Windows. When you run a command like usbipd list or usbipd bind, the CLI attempts to communicate with this service via a local network socket. If the service hasn't started, was interrupted, or crashed, the CLI returns this warning because it has no "server" to talk to. Why a Reboot Isn't Always Necessary
A reboot fixes the problem by forcing Windows to re-evaluate its "Automatic" start services. However, you can usually resolve this in seconds without closing your work by manually triggering the service. Quick Fixes Instead of a full restart, try these steps in order: When using usbipd-win , the warning "The service
Manual Service Start:Open PowerShell as Administrator and run: powershell Start-Service usbipd Use code with caution. Copied to clipboard
Check Service Status:To see if it’s actually running or stuck in "Starting," use: powershell Get-Service usbipd Use code with caution. Copied to clipboard
The "Services" App:Press Win + R, type services.msc, and find usbipd. Right-click it and select Restart. If it is set to "Manual," change the Startup Type to Automatic. Common Pitfalls
Version Mismatch: If you recently updated WSL or the usbipd-win MSI package, the old service instance might be orphaned. A manual stop and start usually clears this.
Execution Policy: On some corporate machines, the service may be blocked from starting automatically by security software.
Port Conflicts: usbipd typically uses port 3240. If another application is camping on that port, the service will fail to initialize.
While the warning points toward a reboot, it is more accurately a prompt to verify that the Windows Service host for USBIP is active and listening. Manually starting the service is the more efficient "pro-user" solution.
How to Fix the USBIPD Warning: "The service is currently not running"
If you are working with the Windows Subsystem for Linux (WSL) and trying to pass through a USB device, you’ve likely encountered the frustrating message: "usbipd: warning: The service is currently not running. A reboot should fix that."
While the error suggests a simple restart, a reboot doesn't always solve the underlying issue. This guide will walk you through why this happens and the most effective ways to get your USB devices connected to WSL without wasting time on unnecessary restarts. Why Is This Error Happening?
The usbipd-win project allows you to share locally connected USB devices with other machines, including WSL2 virtual machines. This process relies on a Windows Service (appropriately named usbipd) running in the background.
When you see this warning, it means the usbipd.exe client cannot communicate with the background host service. This usually happens for three reasons:
The service failed to start automatically after installation. The service crashed or was stopped by a system conflict.
Your execution policy or permissions are preventing the service from initializing. Step 1: Manually Start the Service (The Quick Fix)
Before you follow the prompt to reboot, try starting the service manually via the Windows Services Manager. This is often more effective than a restart. Press Win + R, type services.msc, and hit Enter. Scroll down until you find USBIPD Device Host.
Check the "Status" column. If it’s blank, right-click it and select Start.
Set the "Startup type" to Automatic by right-clicking > Properties, so it persists through future boots. Step 2: Use PowerShell to Force a Restart
Sometimes the service is "stuck" in a pending state where the GUI can't help. You can use an Administrative PowerShell terminal to force-reset the daemon. Run the following commands: powershell What the warning indicates
# Check the status of the service Get-Service usbipd # If it's stopped, start it Start-Service usbipd Use code with caution.
If you get an "Access Denied" error, ensure you are running PowerShell as an Administrator. Step 3: Update usbipd-win
If the service refuses to stay running, you might be using an outdated version that is incompatible with your current Windows build or WSL kernel. Open your terminal and run: usbipd --version Use code with caution. Go to the usbipd-win GitHub releases page. Download and install the latest .msi file.
Important: After updating, you actually should reboot this time to ensure the new drivers are properly initialized. Step 4: Check for Port Conflicts (Port 3240)
USBIPD communicates over TCP port 3240 by default. If another application (like a different USB sharing tool or a strict firewall) is using that port, the service will fail to start. To check if the port is occupied, run: powershell netstat -ano | findstr :3240 Use code with caution.
If you see a result, another process is blocking USBIPD. You may need to identify that software and disable it or change its port settings. Step 5: Reinstall the MSI (Repair Mode)
If the service is missing entirely from your services.msc list, the installation was likely corrupted. Go to Settings > Apps > Installed Apps. Find usbipd-win. Click the three dots and select Modify, then choose Repair.
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.
By following these steps, you can bypass the "reboot loop" and get back to your development work. Most of the time, simply toggling the service in services.msc is all it takes to clear the warning.
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
The "USBIPD Service Not Running" Glitch: Causes and Fixes If you are working with the Windows Subsystem for Linux (WSL) and trying to pass through a USB device, encountering the warning
"The service is currently not running; a reboot should fix that"
is a common roadblock. While the message suggests a simple restart, the underlying issue usually stems from a communication break between the Windows USBIPD-WIN agent and the WSL instance. Why It Happens usbipd is the service that manages USB device
tool operates as a background service in Windows. It acts as a bridge, translating hardware signals from your physical USB ports into a format that the Linux kernel inside WSL can understand. This error pops up when: The Service is Stopped: service failed to trigger during boot or crashed. Version Mismatch:
You’ve updated WSL or the Linux kernel, but the Windows-side tool is outdated. Installation Issues:
The drivers weren't properly registered during the initial setup. The Quick Fixes
Before committing to a full system reboot, try these targeted steps to save time: Restart the Service Manually: PowerShell as Administrator powershell Get-Service usbipd | Restart-Service Use code with caution. Copied to clipboard
This force-starts the background process without needing to shut down your entire PC. Verify the Installation: Sometimes the path isn't recognized. Run usbipd --version
to ensure it’s actually installed and accessible. If it returns an error, you may need to reinstall the latest GitHub releases page Check WSL State:
Ensure your WSL distribution is actually running before attempting to attach a device. Run wsl --list --running to verify. The "Last Resort" Reboot
If the manual restart fails, a reboot often works because it clears the USB host controller's state
and re-initializes the virtual bus drivers. However, if the error persists
a reboot, it is almost certainly a firewall or third-party antivirus software blocking the local network connection (port 3240) that uses to talk to Linux.
In short: Start with a service restart in PowerShell; if that fails, check your updates; and only then hit the restart button. Are you seeing this error while trying to attach a specific device , or does it happen the moment you type the command?
The message "usbipd warning: the service is currently not running, a reboot should fix that" typically appears when using usbipd-win (a Windows tool for sharing USB devices over a network).
Here’s a breakdown of what this warning means and the feature/behavior it refers to:
The message "usbipd warning: the service is currently not running. a reboot should fix that" is more of a gentle nudge than a fatal error. In most cases, manually starting the service (net start usbipd) resolves the issue instantly. For persistent cases, a clean reinstallation or checking service dependencies will restore functionality.
Remember that USBIPD is an essential tool for developers who need full USB access inside WSL—whether for flashing embedded devices, using security keys, or accessing serial adapters. Once you understand how its Windows service operates, you can troubleshoot this warning in seconds rather than losing productivity to unnecessary reboots.
Final tip: Add the following line to your PowerShell profile to automatically attempt to start the service whenever you open a new terminal:
if (-not (Get-Service usbipd -ErrorAction SilentlyContinue).Running) Start-Service usbipd
Now go ahead, attach that USB device to your Linux environment, and keep coding.
While a reboot is the "sledgehammer" fix, try these precision fixes first to save time.
Yes. It consumes negligible resources and only activates when you use usbipd commands.