If the service is disabled, you need to set it to automatic or manual. Press Win + R , type services.msc , and hit Enter. Locate in the list.
Inside your WSL terminal, ensure you have the latest tools:
Check if the server is now running:
Before reinstalling software or changing configurations, check if the service is present and force it to run. Press Win + R , type services.msc , and press . If the service is disabled, you need to
Note: If these features were toggled off, a system restart is mandatory. Step 4: Resolve Firewall and Network Port Conflicts
You can now proceed to attach devices to your WSL distribution normally using usbipd attach --busid --wsl . If you are still experiencing issues, let me know: Which you currently have installed.
To enable these:
This functionality relies on a Windows Kernel Driver. When you see the warning "The service is currently not running," it usually points to one of three scenarios:
If the Services GUI hangs, force the service to initialize using administrative privileges.
Windows Defender usually configures itself automatically during the usbipd installation, but third-party security suites (like Kaspersky, Bitdefender, or Malwarebytes) may aggressively block the local loopback connection. Open your third-party antivirus/firewall dashboard. Navigate to or Rules . Create an Inbound Rule allowing traffic for usbipd.exe . Inside your WSL terminal, ensure you have the
with Administrator privileges to avoid a full system reboot. Open Terminal as Admin : Right-click the button and select Terminal (Admin) PowerShell (Admin) Start the Service : Run the following command: sc.exe start usbipd Verify Status : Ensure it is running by typing: sc.exe query usbipd should show 4 RUNNING Step-by-Step Troubleshooting Guide
Restart Windows completely (not just shutdown/sleep). After rebooting, open a new terminal and test:
