You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This weekend I tried to work with the usbipd-win library to attach a serial port to WSL2 (archlinux distro) , but got stuck. I tried the following things:
reinstalling usbipd-win
convert the driver to winusb with the zadig [version 2.9] tool (without success, so converted it back to the original driver)
checked firewall settings (incoming rule for uspipd on port 3240 is active)
looked into the following issue and ran sfc /scannow and cleanmgr.exe (and select clean system files + Drivers)
pnputil.exe /enum-drivers returns the following result:
Published Name: oem41.inf
Original Name: vboxusb.inf
Provider Name: Oracle Corporation
Class Name: USB
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Driver Version: 09/10/2025 7.2.2.20484
Signer Name: Microsoft Windows Hardware Compatibility Publisher
look into the error using the included visual studio project in the git-repo. I can confirm that the error (see below) is thrown after 10 seconds. Therefore it looks like the FileNotFoundException is thrown in VBoxUsb.cs (line 66), so something in ClaimDeviceOnce might not work as expected:
public static async Task<(WindowsDevice vboxDevice, DeviceFile deviceInterfaceFile)> ClaimDevice(BusId busId)
{
var sw = new Stopwatch();
sw.Start();
while (true)
{
try
{
return await ClaimDeviceOnce(busId);
}
catch (FileNotFoundException)
{
if (sw.Elapsed > TimeSpan.FromSeconds(10))
{
throw;
}
await Task.Delay(100);
}
}
}
Find enclosed the server and clientlog. The error refers to ConnectedClient class and it seems that is waiting at HandleRequestImportAsync for 10 seconds. Could it be something with the VBoxUsb driver? Does anyone have a suggestion how to fix this or get more insights what could have been go wrong wrong here? Find below the server and client logs
Thank you in advance!
Best regards,
Gerben
clientlog:
PS O:\temp\issue_usbipd> usbipd list
Connected:
BUSID VID:PID DEVICE STATE
2-6 0c45:6732 Integrated Webcam, Integrated IR Webcam Not shared
2-9 27c6:63ac Goodix MOC Fingerprint Not shared
2-10 8087:0033 Intel(R) Wireless Bluetooth(R) Not shared
3-2 0bda:8153 Realtek USB GbE Family Controller #2 Not shared
4-3 1915:521a Serieel USB-apparaat (COM3) Shared
4-5 0bda:4014 Realtek USB Audio Not shared
5-1 1c4f:0002 USB-invoerapparaat Not shared
5-2 0461:4d22 USB-invoerapparaat Not shared
Persisted:
GUID DEVICE
usbipd: warning: USB filter 'TsUsbFlt' is known to be incompatible with this software; 'bind --force' will be required.
PS O:\temp\issue_usbipd> usbipd attach --wsl -b 4-3
usbipd: info: Using WSL distribution 'archlinux' to attach; the device will be available in all WSL 2 distributions.
usbipd: info: Detected networking mode 'nat'.
usbipd: info: Using IP address 172.30.176.1 to reach the host.
WSL usbip: error: Attach Request for 4-3 failed - Device in error state
usbipd: error: Failed to attach device with busid '4-3'.
serverlog:
PS C:\Program Files\usbipd-win> usbipd server Logging:LogLevel:Default=Trace
dbug: Microsoft.Extensions.Hosting.Internal.Host[1]
Hosting starting
dbug: Usbipd.PcapNg[1000]
usbipd:PcapNg:Path = ''
dbug: Usbipd.Server[1000]
usbipd:Port = 3240
dbug: Usbipd.Server[1000]
5.3.0-54+Branch.master.Sha.aa3db8b82c4cb5071fd31bc54211606c70886912
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Program Files\usbipd-win
dbug: Microsoft.Extensions.Hosting.Internal.Host[2]
Hosting started
dbug: Usbipd.Server[1000]
new connection from 172.30.182.249
dbug: Usbipd.Server[1000]
connection close: Unable to read beyond the end of the stream.
dbug: Usbipd.Server[1000]
connection closed
dbug: Usbipd.Server[1000]
new connection from 172.30.182.249
dbug: Usbipd.ConnectedClient[1000]
Received opcode: OP_REQ_IMPORT
fail: Usbipd.ConnectedClient[3]
An exception occurred while communicating with the client:
System.IO.FileNotFoundException: Unable to find the specified file.
at Usbipd.VBoxUsb.<ClaimDeviceOnce>d__0.MoveNext() + 0x668
--- End of stack trace from previous location ---
at Usbipd.VBoxUsb.<ClaimDevice>d__1.MoveNext() + 0x17e
--- End of stack trace from previous location ---
at Usbipd.VBoxUsb.<ClaimDevice>d__1.MoveNext() + 0x2b9
--- End of stack trace from previous location ---
at Usbipd.ConnectedClient.<HandleRequestImportAsync>d__8.MoveNext() + 0x1078
--- End of stack trace from previous location ---
at Usbipd.ConnectedClient.<HandleRequestImportAsync>d__8.MoveNext() + 0x1ae9
--- End of stack trace from previous location ---
at Usbipd.ConnectedClient.<RunAsync>d__5.MoveNext() + 0x32f
dbug: Usbipd.Server[1000]
connection close: Unable to find the specified file.
dbug: Usbipd.Server[1000]
connection closed
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
This weekend I tried to work with the
usbipd-winlibrary to attach a serial port to WSL2 (archlinux distro) , but got stuck. I tried the following things:reinstalling usbipd-win
convert the driver to winusb with the
zadig [version 2.9]tool (without success, so converted it back to the original driver)checked firewall settings (incoming rule for
uspipdon port 3240 is active)looked into the following issue and ran
sfc /scannowandcleanmgr.exe(and select clean system files + Drivers)pnputil.exe /enum-driversreturns the following result:FileNotFoundExceptionis thrown inVBoxUsb.cs(line 66), so something inClaimDeviceOncemight not work as expected:Find enclosed the server and clientlog. The error refers to
ConnectedClientclass and it seems that is waiting atHandleRequestImportAsyncfor 10 seconds. Could it be something with theVBoxUsbdriver? Does anyone have a suggestion how to fix this or get more insights what could have been go wrong wrong here? Find below the server and client logsThank you in advance!
Best regards,
Gerben
clientlog:
serverlog:
Beta Was this translation helpful? Give feedback.
All reactions