virtualbox.org

Hi,
Having the same problems as here: viewtopic.php?f=2&t=44957

It appears to be only Moxa UPorts, all other USB devices work. Have tried both UPort 1110 and UPort 1150.

Windows 10 Pro 64-bit host
Tried both Windows 7 Pro 32-bit and Windows 10 Pro 64-bit guests
VB Version 6.0.8 r130520 (Qt5.6.2) with extension pack installed
Guest Additions installed on guests

Have tried all the troubleshooting steps - USB filter created, tried both USB 2.0 and 3.0 with 3.0 eXtensible host controller driver installed. The device appears in Device Manager, but has a "This device cannot start. (Code 10)" error.
The second tab of the device properties shows it is COM0, when it should have assigned it a COM port number:

https://drive.google.com/open?id=1k7Q-9 ... opaatbxmMV (Sorry, don't know how to link the image locally, won't let me upload attachments more than 128KB.)

If I try to leave the tab, I get an error pop-up saying "Port 1 (COM 0) Com number invalid !"

Interesting thing is I had it working in an older version of VB, can't remember what version though. Moxa had also updated the driver since then. And obviously it works in the host. So not sure if VB is the issue or the Moxa driver is.

VBox.log: https://drive.google.com/open?id=1Cpgqp ... gmhMQ3bgGk

Let me know if I can provide any other info to help with diagnosis.

Thanks.

I see the VM is configured for xHCI (USB3) support, but the guest is Windows 7 (32bit), which does not support USB3 natively. Did you install the Intel driver?

Once the USB3 controller issue is fixed, I would imagine that the UPort needs its own proprietary Win7 user level driver - that's what a code 10 error usually means.

mpack wrote:I see the VM is configured for xHCI (USB3) support, but the guest is Windows 7 (32bit), which does not support USB3 natively. Did you install the Intel driver?

Yes, I mentioned in my first post that I had tried both USB 2.0 and USB 3.0 with the Intel eXtensible driver.

mpack wrote:Once the USB3 controller issue is fixed, I would imagine that the UPort needs its own proprietary Win7 user level driver - that's what a code 10 error usually means.

I had installed the latest Moxa UPort driver.

I have just tested VMware Workstation 15 Player and it worked straight away using USB 2.0.

Here is what it should look like in Device Manager: https://drive.google.com/open?id=1O_HzH ... XxCjXceRWI

I would much rather use VB though as I've been using it for years.

I see in your linked picture that the device becomes two devices in Device Manager. I vaguely remember a post where the USB device broke into multiple devices in the guest and Virtualbox couldn't filter it correctly. Probably not remembering right, bu I believe the solution was to remove as many items from the guest's USB filter as possible while still allowing the device to be captured. Might have just been the vendor id?

BTW, zipped logs post just fine. Pictures can be posted using the forum's Upload Attachment tab. PNGs are best. Scale to fit under the 128kB limit.

Yes, the device appears as two devices.
I was already using a filter with only Vendor ID and Product ID. I have now tried filters with only Vender ID and only Product ID, same issue.
Even an empty filter with only Name is doing the same thing.