Hope this helps someone else who might hit the same error (could happen on any hardware). Fortunately, Microsoft has a “fix it” utility which makes cleaning this up easy, listed in the resolution section This has a whole bunch of effects, some of which are listed in Microsoft’s knowledge base article. Error 1168: Element not found.Īnd that error led to guessing this machine had corruption of XP’s %Systemroot%\System32\Catroot and catroot2 databases (which apparently is not uncommon). #E358 An unsigned or incorrectly signed file “c:\windows\inf\usb.inf” for driver “Generic USB Hub” blocked (server install). Assuming all device classes are subject to driver signing policy. The parent driver creates a separate PDO for each function of a composite device. For more information, see USB Generic Parent Driver (Usbccgp.sys). For a composite USB device that exposes multiple functions and does not have a parent class driver, Windows loads the USB generic parent driver (Usbccgp.sys) between the hub driver and the client driver layer. Usbccgp.sys is a parent driver for composite devices that supports multiple functions. #W239 The driver signing class list “C:\WINDOWS\INF\certclas.inf” was missing or invalid. Microsoft-provided driver and INF Windows support Description USB: Usbccgp.sys. For the benefit of others, the main clue was this error message: Let’s try simple troubleshooting steps and check if. This could be due to the USB port driver is outdated. None of the attached devices, except for the USB 2.0 hard Drives work. After a review of the Device Manager I discovered that the Generic SuperSpeed USB Hub was not working. 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. Generic SuperSpeed USB Hub stopped working on Windows 10.
0 kommentar(er)
