Most Valuable Professional
Group: Forum Members
You can try looking at the Drivers folder, specifically its 3 subfolders, and moving drivers out of there systematically, but the issue there is that drivers are also baked into the Boot.wim file since some drivers need to load earlier in order to work, which that mechanism achieves. If just tinkering with the easily accessible Drivers folder doesn’t yield promising results, you can use the DISM application to mount and modify that Boot.wim file. I can’t remember offhand whether the driver files in there are just stored within a specific folder or whether you have to use other DISM commands to add/remove drivers from the actual driver store of that image. If you want to attempt it though, I’ll look into it and even post some example commands for you.
The problem you’re going to have in the end though is that even if you find the offending driver, there isn’t a way to have Reflect exclude drivers from Rescue Media builds; it adds what it considers necessary. I’ve even tried deleting unwanted drivers in the middle of the wizard before the build occurs (such as for a Hyper-V Internal network virtual NIC on my host system), but last time I tried that, it caused the build to error out.