I have an issue, that this device is not installed during Task Sequence run. The reason might be, that this device is discovered only after another USB device is installed with driver first. So I understand why this 3.0 root hub is not installed during Auto Apply Drivers step. Here are some facts: 1. Driver files of USB 3.0 root hub are saved in SCCM driver store, they are imported to driver catalog and they are located in driver package correctly with other drivers. 2. In Auto Apply Driver step I have no limitations, all drivers are allowed to install. 3. If I install a computer with USB 3.0 support manually and install USB drivers, right after USB 3.0 extencive host controller, new unknown device appears at device manager, and I can be installed from the same SCCM driver source location as I use to import drivers into driver catalog. One way would be repeat driver installation step, but as I understand, it must be done in OS itself, not in WinPE phase.

Use a driver package instead.

Use a driver package instead. Damn, offcourse... driver package pulls all files included to a machine. Not only which are compatible at the moment during WinPE. Unfortunately my entire Drive Catalog is build with idea of automatic matching, using auto apply drivers. I believe there wouldnt be any issues, if use both?

No there is no problem combining both auto apply and driver packages.