USB-Dongle with Vendor-ID 0000 cannot be attached

[RainerHohn]

I have to connect a USB-Licence-Dongle with Vendor-ID 0000 and Product-ID 9999 to a virtual machine (Windows 7/64 Professional).

This fails with:

Assertion failed: [mData.vendorId] at 'D:\tinderbox\win-4.3\src\VBox\Main\src-client\USBDeviceImpl.cpp' (62) in long __cdecl OUSBDevice::init(struct IUSBDevice *).

Please contact the product vendor!.

Fehlercode:E_FAIL (0x80004005)
Komponente:OUSBDevice
Interface:IUSBDevice {f8967b0b-4483-400f-92b5-8b675d98a85b}

Having a look at this Code-Line shows

ComAssertRet(mData.vendorId, E_INVALIDARG);

It seems there is no reason for failing here besides the fact, that 0000 is not an allowed vendor-id. At least VMware Workstation 10 can handle this. Don't tell me to contact the Vendor, I have to work with what I get, and what I get has Vendor-ID 0000.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.

[sforna]

Same problem with version 5.2.10 USB dongle with vendor-ID 0000 not seen at all even by doing VBoxManage list usbhost

[Socratis]

Replying to RainerHohn:

It seems there is no reason for failing here besides the fact, that 0000 is not an allowed vendor-id.

So, besides that fact that this VID is invalid, you don't see any problems. But that's exactly the problem. Someone breaking the standard and yet you expect everyone to break the standard to follow the bad practices of a rogue vendor. They should register with a proper VendorID and also their products with proper IDs. 9999 is a proper ID BTW...

What does your host PC show when the device is inserted? What do Device Manager, or ​USBDeview, or ​USBView, or ​UsbTreeView have to say about the "thing"? ​USB.ids says nothing about it, for sure.

I'm not saying I don't understand you're between a rock and a hard place. My "frustration" I guess is towards the V in VID for doing something not that smart and forcing everyone to follow bad practices...