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

Resolving the "usbipd Warning: The Service Is Currently Not Running" Error in Windows (WSL 2)

Introduction

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.

Underlying feature causing this message

This is part of automatic service startup behavior in usbipd-win: Resolving the "usbipd Warning: The Service Is Currently

• The service wasn’t started after installation.
• A system update or security software stopped it.
• You’re trying to run usbipd bind or usbipd list before the service is running.

(This attempts to kill any stuck processes). The service wasn’t started after installation

Or download from the official GitHub releases: usbipd-win (This attempts to kill any stuck processes)

Solution 3: Fix Service Dependencies

The usbipd service depends on the Windows USB driver stack and sometimes WinUSB. If these dependencies fail, the service won’t start even after a reboot.

Step 2: Check the Driver (The Likely Culprit)

If Step 1 didn't work, the USBIPD driver is likely installed but failing to start.

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