Kayaker wrote:That seems useful, on the surface at least.
CM_PROB_NOT_CONFIGURED - There is a device on the system for which there is no ConfigFlags registry entry. This means no driver is installed. Typically this means an INF file could not be found.
Are the BootFlag and other settings in the Registry set and comparable to say those in a working Win10 usbxhci entry?
It's obvious I need to do more research, like comparing W7 to W10 more closely.
I know it's tough for you since you don't have the actual hardware to deal with or even the drivers in the correct context. I think I have other issues related to the actual installation and I can't offer you good info yet till I look into that.
For example, from the installation log, it tells me it cannot decipher the A36D device description. No kidding!! When the INF file was written, the A36D XHCI controller it describes did not exist. So, I have to see if I can track down what info it needs, maybe from the W10 xhci install which does know about the A36D controller.
One problem is knowing where to look in the W10 registry. I am sure I can compare them directly in most cases. Another issue is that the USB 3 implementation seems to have changed between W7 and W10. Apparently W8 retained the USB 2 stack and implemented the USB3 stack in parallel, each with their own drivers. In W10, it seems they are implementing both USB 2 and 3 through the same stack, using only an xhci host controller for both.
That should not really matter since Intel has released drivers for W7 that run on processors and chipsets very similar to my present processor/chipset. Intel has supplied no drivers other than the host controller, the hub driver, and a switch driver that I think serves to switch USB devices between operating modes. For example, sometimes a USB port is strictly an input port but at others it works as a server.
Furthermore, I had W7 on a hard drive running on an ICH9 chipset which is at least 10 years older than my current chipset, and when I plugged the drive into my new mobo, everything on W7 ran fine except for the USB stack. The hard drives, display, etc., all ran fine using the old ICH9 drivers.
I have since updated the W7 drivers to drivers better suited to the new mobo, but even at that, W7 runs happily with drivers designed for a chipset closer to mine than the ICH9.
Furthermore, for some reason, the WOW64 node is being used. There are 32-bit apps being used by Intel, which explains part of that, but on a Russian site I saw a note that the USB3 drivers should be installed in the Windows directory in the SysWOW64 directory.
Have not tried that yet.