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

You do not need to reboot if you can start the service manually.

Instead of rebooting, you can manually start the service:

net start usbipd

Or via PowerShell as admin:

Start-Service usbipd

You can also check its status with:

Get-Service usbipd

The warning message explicitly suggests a reboot. This works in most standard installation cases because: You do not need to reboot if you

Action: Restart Windows completely (not just shutdown/sleep). After rebooting, open a new terminal and test:

usbipd wsl list

If the warning disappears, you are done. If not, proceed below.

These steps should help you diagnose and fix the "service is currently not running" warning without relying solely on reboots. If you want, I can convert this into a full blog post with screenshots, commands formatted as code blocks, and a short troubleshooting flowchart.

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). Or via PowerShell as admin: Start-Service usbipd

Here’s a breakdown of what this warning means and the feature/behavior it refers to:

If you are a developer working with Windows Subsystem for Linux (WSL 2) and need to attach USB devices from your Windows host directly into your Linux environment, you have likely encountered usbipd-win. This open-source project allows you to share USB devices connected to Windows with WSL 2 instances.

However, a common and frustrating roadblock appears when running the command:

usbipd wsl list

Or any other usbipd command, only to be greeted with the warning: You can also check its status with: Get-Service usbipd

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

This message can be confusing, especially if you have already installed the software correctly. Is a reboot really necessary? What if rebooting doesn't work? Why is this happening in the first place?

This article will explain what this warning means, why it appears, and—most importantly—how to permanently fix it so you can get back to working with your USB devices in WSL.

If you just installed it or haven't rebooted in a while, the driver might just be sleeping. Open PowerShell as Administrator and run these commands in order: