I used dism++ to load the boot.wim on the flash drive, read only, and tried to find the driver but couldn’t see it. There was something with unknown in the name but not recognizable. So still trying to understand exactly how it started working. Doing some more experiments as time permits. Thanks for the help.
Why?I used dism++ to load the boot.wim on the flash drive, read only,
Because it was working already, I didn’t need to actually change it. Just investigating.
Not because I wanted to bug you, heh.
- - - Updated - - -
So the combination of selecting copy host usb drivers (advanced settings) and using winPE gets the usb3 working, had nothing to do with that txt file. I had made 2 changes at same time.
I can remember back some time though where a test with a working OS and a bootable flash drive was like a false positive. IOW when booting the rescue environment it was actually loading a driver from the HDD. Cause when the HDD was blank later on the usb3 did not work. I eventually solved that. Kind of a pain to test it.
I’m curious though why when I viewed the usb drivers in the boot.wim with dism++ I couldn’t recognize the names of usb3 inf. I’ll have to take another look. That’s it for tonight.
Quote