DeviceFailedEnumeration on Anywhere USB 5M

I recently purchased a 5-port AnywhereUSB and when I connect a Verifone MX800 family POS payment terminal I see DeviceFailedEnumeration in the status in the Remote USB Hub Viewer.

The only that shows up in Device Manager is an “Unknown Device” under “Universal Serial Bus Controllers”. However, when I look at the properties of this device the Physical Device Object name has a vendor ID of 1608 which is not the Vid of the Verifone so I’m assuming this is for the USB hub itself.

I should also mention that when connected properly, this device shows up as a COM port in Windows and I have a feeling that this behaviour may have something to do with the problem.

I am testing this on a Windows 7 x86 workstation
Hub firmware: v1.38.1013
Hardware: Rev A - G2

Any suggestions on what to do next?


In most cases when enumeration fails the hub driver will still report the arrival of a device to Windows. In these cases the USB device will appear as “Unknown Device” in Device Manager, and will have a Device ID of “USB\VID_0000&PID_0000” and a Hardware ID and Compatible ID of “USB\UNKNOWN”. The following events will cause the USB hub driver to enumerate a USB device as an “Unknown Device”:

-A port reset request timed out during enumeration.
-The Set Address request for the USB device failed.
-The request for the USB device’s Device Descriptor request failed.
-The USB Device Descriptor was malformed and failed validation.
-The request for the Configuration Descriptor failed.
-The USB Configuration Descriptor was malformed and failed validation.

Try this…

  1. The USB device is “hung”.

The USB device may have encountered an internal error and simply stopped functioning. The device will have a code 43 in Device Manager. Removing all power from the device (e.g. unplugging and re-plugging the USB cable and also the power cable if it has one) will reset the device and allow it to enumerate successfully.

  1. Worn or faulty USB connectors and cables.

Over time USB cables and connectors can fail. Try plugging it into a different USB port, and also using a different USB cable if it is removable. The device will have a code 43 error in Device Manager.

  1. No driver is installed, and the USB device does not report a device description string.

In this case Windows was unable to find a driver for the device, and the device did not report a device description string. The device will have a code 28 in Device Manager. To resolve this problem you will need to find a compatible driver for the device, typically by contacting the device’s manufacturer.

  1. There is insufficient power to start the device.

If the device is downstream of a bus-powered hub, the device can enumerate successfully but may not be able to start due to insufficient power. This a bus-powered hub cannot supply more than 100mA to a port, whereas a self-powered hub can supply 500mA. The device will have a code 28 in Device Manager. To resolve this problem, plug-in the hub’s power supply (if it has one), move the device to a root hub port, or move the device to another hub that is self-powered.

  1. The upstream hub has failed or is “hung”.

If the device is connected to an external hub, try moving the device to a different hub or a root port. If the device enumerate successfully, try power-cycling the hub or removing/replacing it. Device will have a code 28 in Device Manager.

  1. The USB device has failed.

It is possible that the USB device itself has suffered a hardware failure and is no longer functional. You will need to replace the device. Device will have a code 43 in Device Manager.

Just wrapped up the support case with Digi on this and figured I’d share the results in case anyone runs into this in the future. The problem was caused by the Verifone not responding correctly to a query made by the Anywhere USB driver during the phase when it is first querying the device. The solution ended up being a custom driver which eliminated this query and this solved the problem. So a very specific problem confined to this device.