Something unusual is happening on your system, because the hub (like all standard USB 2.0 hubs) does not require any special driver - it uses the Microsoft drivers already in Windows (usbhub.sys).
So a few quick checks/tips:
* For the device that’s coming up bad in device manager, can you open its properties, go to “Details” tab, select “Hardware IDs” from the drop down, and post the top/long line here?
* Can you post the size and date of the file \windows\inf\usb.inf (which is the file Windows XP should be matching on to get the Windows-supplied hub driver)
We’ll get this figured out! Thanks for your patience!
Thanks for the reply with this good info. Ok, great, those IDs are coming from our 10 port hub.
What’s really interesting is the usb.inf (which is part of Windows itself). With Windows XP SP3, the date on that file should be 4/13/1998 and the size 20623. So it doesn’t appear you have an XP SP3 version of that file.
Let’s also see what the USB drivers in Windows have for date. Can you check
It appears something has overwritten \windows\inf\usb.inf (possibly with the version from the original pre-SP3 Windows XP), which would mean all new USB devices have a good chance of failing to install properly.
We need to replace that file with one from an actual XP SP3 machine. Do you have another around that you could take usb.inf from?
Very glad we could get this interesting case solved! This turned out to be a problem unrelated to the product, with XP’s cryptsvc service and its database. For the benefit of others, the main clue was this error message:
#W239 The driver signing class list “C:\WINDOWS\INF\certclas.inf” was missing or invalid. Error 1168: Element not found. Assuming all device classes are subject to driver signing policy. #E358 An unsigned or incorrectly signed file “c:\windows\inf\usb.inf” for driver “Generic USB Hub” blocked (server install). Error 1168: Element not found.
And that error led to guessing this machine had corruption of XP’s %Systemroot%\System32\Catroot and catroot2 databases (which apparently is not uncommon).
This has a whole bunch of effects, some of which are listed in Microsoft’s knowledge base article. Fortunately, Microsoft has a “fix it” utility which makes cleaning this up easy, listed in the resolution section