New
#1
Integrate a Driver *Package* into an installation disk
Does anybody know how to either:
a) integrate a Driver *Package* into an installation disk, in particular the MS NVMe Hotfix (Windows6.1-KB2990941-v3-x64.msu)?
OR
b) figure out which internal package (there are 87 of them) inside the Driver Package is the one the system used?
System:
Windows 7 x64 SP1, UEFI/GPT, PCIe SSD (Patriot Hellfire), AMD A88X FM2+, A10-7800
Background:
This all started with simply wanting to replace my bloated BCD file, due to hardware changes and multiple configurations to launch Windows, with a basic one. I also found that all the changes led to instances of bootmgfw.efi being left in memory. Replacing the BCD can't be done within Windows, and I'd like a working installation setup anyway.
My installation setup is on a USB flash drive and it will not recognize the PCIe SSD, which already has Windows installed on it. What I needed the setup for is unrelated to this problem, a problem that I only discovered along the way when trying to run the setup. I used the same flash drive as when I installed Windows, except I replaced the drivers for the OCZ PCIe SSD (which had its own drivers) with the MS standard NVMe drivers that the Hellfire uses. I also tried manually loading the drivers (with a clean boot.wim & install.wim) using both the setup and diskpart. Diskpart *said* the drivers loaded successfully but still neither diskpart nor setup would recognize the drive. I tried every combination of x86 and x64 drivers and launching the system in both UEFI and UEFI+Legacy mode. My system does not have Legacy Only.
Because I had upgraded to SP1 after the original installation, I thought that might have something to do with the problem (it didn't) so I got my hands on a MS (non-pirated) SP1 installation ISO. No difference.
I was getting the 'No signed drivers could be found' message so I set the flag on the setup BCD to accept unsigned drivers. Didn't help.
I had the notion that even though setup would accept the drivers, it still wanted the Security CAT file to be present. That file is not anywhere I could find on the Windows installation itself so I went to examine the actual driver package. That's when I found that there is no 'Drivers' directory, per se, that there are 87 internal packages, and that each package is spread across a variety of files with different extensions, along with some unlabeled entries that number in the hundreds. I tried to figure out which package was installed in system by cross-referencing any code numbers I find in the INF file, the Driver properties, Driver Store, INF directory, CAT directory, and the driver package without success.
Hence, my two questions above. I either need to figure out which internal package is installed or how to integrate the whole package into the setup.
Quote