Error Generic USB Hub in Device Manager

[Meinhard]

Hello,
has anyone an idea about an error within the device manager.
When booting my PC with a connected USB hub I always get the following
error (device status) within the device manager:

Windows cannot load the device driver for this hardware because there is
a duplicate device already running in the system. (Code 42)

No other devices are connected to my USB ports. When disconnecting,
waiting some secondes, then connecting the hub, everything works and the
error in the device manager has gone, but when rebooting I have the
error again and no devices connected to the hub are working.
I already tested different hubs at my PC, always the same error.
Using different USB devices directly connected to the PC is no problem.

My image is based on SP1 components, when using SP2 components I don't
have the error. This is a solution for new images but not for already
deployed images. What I need is may be some missing registry keys or
missing files which to update with DUA.

Has anybody an idea or better a solution to this problem?

Thanks in advance

Meinhard

 

[Slobodan Brcin \(eMVP\)]

Meinhard,

Two long shots:

1. After you get this error commit EWF and reboot computer.
2. Check under critical boot devices if usbhub is set for load as boot
critical driver. This would result in driver being loaded before User Mode
PnP kick in. User mode PnP will try to stop your drivers and load new
instances but it can fail in this so you see your error.

My question is:
What is your boot medium and from which controller (USB/IDE, ....) do you
boot?

Regards,
Slobodan

 

[Meinhard]

Slobodan,
thanks for your suggestions but I don't exactly understand what you mean.

1. I don't use EWF, my hardware is a Standard PC with a IDE harddisk as
boot medium
2. What is "critical boot devices" is it a registry key or an entry in
the Target Designer?

Meinhard

 

[Slobodan Brcin \(eMVP\)]

Meinhard,

Forget then EWF. What happen when you restart computer?

Registry entry HKLM\System\ControlSet001\Control\CriticalDeviceDatabase list
all drivers that should be started during the boot time even if they were
not previously installed by UserMode PnP.

Only way for you to figure out the problem if continue is to delete
setupapi.log and reboot computer. (Increasing log level of setupapi is also
good idea)

New setupapi.log should be created and it should contain the problem
description about your hub.

Regards,
Slobodan

 

[Meinhard]

Slobodan,
thanks for your last suggestion to solve my problem. I checked the
setupapi.log when rebooting with a connected usb hub.
There I found the following lines:

#W025 A newer file "C:\WINDOWS\system32\drivers\usbhub.sys" was
overwritten by an older (signed) file. Version of source file:
5.1.2600.0. Version of target file: 5.1.2600.1106. The existing target
file was signed.
#E249 Failed to apply security to file
"C:\WINDOWS\system32\drivers\usbhub.sys". Error 1307: This security ID
may not be assigned as the owner of this object.

After replacing usbhub.sys (5.1.2600.0) with usbhub.sys (5.1.2600.1106)
in C:\Windows\i386 and C:\Windows\LastGood\system32\drivers the error in
Device Manager didn't come again.

Thanks

Meinhard