Scroll down the list to locate (or usbipd ). Check the Status column: If it is blank, right-click the service and select Start .
Compatibility mismatches between outdated WSL kernels and newer versions of usbipd-win frequently cause background service crashes.
If the service is not running, try to start it manually from the same admin PowerShell.
For further technical details or to report persistent crashes, you can check the usbipd-win GitHub Issues or the official Troubleshooting Wiki Did you encounter this warning after a new installation or after a Windows update Scroll down the list to locate (or usbipd )
Because usbipd communicates over local network sockets (typically port ), overzealous antivirus software or strict Windows Firewall rules can block internal loopback traffic. Open Windows Defender Firewall > Allowed Apps .
If you are trying to share physical USB devices with a Windows Subsystem for Linux (WSL 2) distribution or a local virtual machine using usbipd-win , you may encounter this frustrating terminal warning:
Alternatively, use the command to query the service status: If the service is not running, try to
Then start it once manually or reboot at your convenience.
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.
to clear out cached drivers and hung registry entries. If you are trying to share physical USB
This error triggers when the Windows CLI tool ( usbipd.exe ) tries to communicate with the background Windows service ( UsbipdDnsService ), but finds the service unresponsive, stopped, or missing. The primary reasons this happens include:
USBIPD relies heavily on the underlying Windows virtualization stack to bridge hardware down to the Linux layer. Missing dependencies will cause the service to fail silently.