Right-click and select Restart (or Start if it is completely greyed out or stopped).
Run the newly downloaded .msi installer. Ensure you grant administrative permissions when prompted. Step 4: Verify WSL Integration and Linux Tools
If the service fails to start, check the system logs (e.g., using journalctl on systemd-based systems) for any error messages related to usbipd . These can provide clues about why it's not running.
If any items were unchecked, check them, click , and allow Windows to perform a complete system reboot. Verifying the Fix Right-click and select Restart (or Start if it
This comprehensive guide explains why this error happens and provides step-by-step solutions to fix it immediately. Understanding the Error
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?
Look for : If it says Stopped , use the command above. If it says Starting or Stopping , wait a few seconds and retry. Step 4: Verify WSL Integration and Linux Tools
netsh advfirewall firewall add rule name="usbipd" dir=in action=allow protocol=TCP localport=3240
If using third-party endpoint protection (e.g., Kaspersky, Bitdefender), temporarily disable the firewall module to test if it resolves the issue. If it does, create an explicit inbound/outbound exclusion rule for port 3240. 5. Address Hyper-V and WSL Virtualization Conflicts
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. Verifying the Fix This comprehensive guide explains why
Check the column. If it is blank, right-click the service and select Start .
To attach a device to WSL, bind it first using administrative rights: powershell usbipd bind --busid Use code with caution. Then attach it directly to your running Linux environment: powershell usbipd attach --wsl --busid Use code with caution. Conclusion