Good evening @Fernando
Thanks for your guidance so far. I think I’m on to something. I’ve come across a video on YouTube on how to integrate the drivers into the two specified .wim files you’ve advised on.
My question on this is: what is the directory destination, or where exactly/what folder or sub-folder name, to integrate them into? I’m hoping there’s a generic answer for this but basically the reason I ask is because when I get as far as to explore what’s in the boot and install .wim files there are tons of folders and sub folders. I want to ensure I inject the drivers into the correct location so that the install is as seamless/smooth as possible.
This is in relation to installing Windows 7 from a USB flash-drive (currently using Rufus on a 2.0 and a 3.0 USB) to a Surface Pro 7 SSD.
I hope this makes sense. Thanks for your patience.
@tutafourabit : Since there is a special thread with a guide within the start post, I have moved your request here.
Hi @Fernando ,
I’ve had a read through your instructions after your diverting of my previous query on integration of drivers to this page. It’s really good - thanks.
The only question I have is how I integrate the hotfixes (x64) as they are .msu files. I obtained these from post #2 of the Recommended AHCI/RAID and NVMe Drivers as instructed by you. I am intending to integrate these to a x64 version of Windows 7.
Please advise if I understand your instructions correctly:
1) I first have to integrate the hotfixes into both boot.wim and install.wim in the iso using NTLite. This will enable an initial install of Windows 7 onto my Surface Pro 7
2) Once the OS is installed I can then integrate the chosen drivers (in my case the OCZ/Toshiba drivers as my SSD in my Surface Pro 7 is a Toshiba BG4). I’m assuming that I’ll have to reinstall the OS again with the Toshiba drivers over the initial OS install? If so, can I not just do one install with the Toshiba drivers? - what will the hotfixes enable me to do?
3) The USB issue is resolved in another post (I haven’t yet got to that step yet).
Am I understanding this correctly? If so, then I’m stuck at the first step in getting the x64 hotfixes integrated.
P.S. I have tried integrating the Toshiba’s ‘ocznmve’ drivers (from step 2) and I see them in the driver queue, but when I try the hotfixes (from step 1) the queue is blank (empty).
Thanks again.
@tutafourabit :
If you are sure, that the latest "pure" 64bit OCZ NVMe driver v1.2.126.843 WHQL supports the NVMe Controller of your Toshiba SSD, you can integrate it according to my guide (start post of this thread). In this case you should not integrate the MS Hotfixes.
This would be the easiest solution.
Good luck!
Hello @Fernando ,
I thought as much. I wouldn’t say I am 100% sure, but I am willing to give it a try as I cannot find any NMVe drivers for this particular model anywhere.
Failing this, I will get back to you about how to get the Hotfixes integrated.
I’ll keep you posted.
Thanks.
Good evening @Fernando ,
I have an update since my last message.
I attempted to integrate the drivers for the Toshiba SSD, however when NTLite had completed the integration process I saw that there were a few of the steps that the software couldn’t complete. I didn’t take a screenshot or regard these at first until I had made an attempt to install Windows 7 to my Surface, and I’ve not been able to get any further with the installation process.
I’ve attached some photos of my Surface desktop to show you what I see when trying to set up Windows 7.
As you can see in the first photo the setup recognises my partition drives but some driver is missing.
As you can see in the second photo the setup specifies the drivers (NVMe).
AS you can see in the third photo there’s an option to browse for the driver.
When I click browse and search for the boot.wim/install.wim iso files with the integrated drivers, I cannot find them.
Is there any particular thing I’m doing wrong?
@tutafourabit :
This thread has been designed for users, who want to integrate a driver (consisting at least of a *.sys, *.inf and *.cat file), and not for users, who want to integrate MS Hotfixes (as *.msu files). The integration procedure is totally different.
You have to integrate the *.msu files as part of the desired OS and not as drivers. After having correctly integrated the MS NVMe Hotfixes the Win7 Setup will automaticly detect your NVMe SSD resp. its NVMe Controller. Since the NVMe driver, which will be used by Win7, is part of the OS and has no digital signature (no *.cat file), it is impossible to integrate it as driver or to load it at the beginning of the OS installation.
Hi @Fernando
Thanks for the update. Do you have a thread that is appropriate for me to look into on how to integrate the .msu Hotfix into the OS? I have not done this before.
Thanks.
@tutafourabit :
If you have a problem regarding the Hotfix integration procedure, please look into the "Support" pages of ntlite.com.
I have only written a guide about how to integrate a real driver.
Hello, I need your help. I have a HP 470 G8 and I created a Windows 10 image with NTLite that does the whole installation automatically. So also the partitioning of the hard disk.
Here I now get the error 0x8030025. So no harddisk is found. Then I added the following driver according to these instructions here.
"intel.com/content/www/us/en/download/19512/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-10th-and-11th-gen-platforms.html"
But unfortunately I still get the same error message.
If I take a standard Windows 10 image and then load the driver manually, then I can create the partition and the installation works.
What am I doing wrong here?
@Marco83 : Welcome to the Win-RAID Forum!
AFAIK the error message you got has nothing to do with the procedure about how to integrate a storage driver into a Win10/11 Image. >Here< you can find some options how to fix the issue.
Questions:
1. Which HDD/SSD (manufacturer and model) is your notebook’s system drive (target for the OS installation and the boot sector) and which data transfer protocol (SATA AHCI or NVMe) does it support?
2. Which are the names and the HardwareIDs of the related AHCI or NVMe Controller (open the “IDE ATA/ATAPI Controllers” or “Storage Controllers” section of the Device Manager)?
3. Which exact driver did you integrate (I need the full name of it).
Regards
Dieter (alias Fernando)
@Fernando Hello, the link belongs to the error 0x80300024, but I have the 0x8030025 
1. I have a Samsung 970 Evo Plus NVME M.2 installed in the laptop.
2. I can not tell at the moment
3. filename: iaStorVD.inf
Revision: 02/18/2021,18.1.6.1039
Abstract: Windows* INF File for VMD Intel(R) Rapid Storage Technology Driver
Installs: RST VMD Controller Miniport + RST Filter Driver
Maybe again for clarification. If I boot a standard Windows 10 image, then I have to partition the hard disk at some point. But there the hard disk is not shown, because a driver is missing. If I now load this driver under point 3 from a USB stick, then the hard drive is recognized and I can partition it and install Windows.
I have integrated the same driver with NTLite, but the Windows installation always aborts at the point where the hard disk is partitioned. Probably because the driver is not found.
@Marco83 :
You have obviously integrated a wrong/not matching storage driver.
Why did you integrate an Intel RST VMD driver, although the NVMe Controller of your Samsung 970 EVO Plus SSD needs an NVMe driver (either the latest Samsung one or the Win10 in-box “standard” NVMe driver from Microsoft)
I bet, that your problem wouldn’t occur, if you would install the OS from an untouched ISO file.
But the problem appears here as well. (Default Windows 10 image).
If this is the wrong driver, why does it work when I install Windows 10 from a untouched ISO file with this driver?
@Marco83 :
Unfortunately you haven’t told me important details of your system (chipset, SATA AHCI/RAID mode and VMD settings within the BIOS).
To be able to answer your questions I need the names and HardwareIDs of all Controllers, which are listed within the “Storage Controllers” and “IDE ATA/ATAPI Controllers” sections of the Device Manager.
You get them by doing a right-click onto the related Controller and choosing the options “Properties” > “Details” > “Property” > “HardwareIDs”.
This is the reason why it does not work: https://www.dell.com/support/kbdoc/de-de…fwerke-gefunden
As I said, with the mentioned driver it works. But not when I integrate the driver in NTLite…
@Marco83 : Thanks for the link.
Did you integrate the driver into both *.wim images (install.wim and boot.wim)?
No only in the install.wim. Probably the drivers must still in the boot.wim under point 2 "Microsoft Windows Setup (x64)" or? Point 1 is with me "Microsoft Windows PE (x64)".
@Marco83 :
No only in the install.wim.
That is the simple reason why the Win10 Setup couldn’t detect the target disk drive and was not able to install the OS onto it. The content of the install.wim can only be used by the Setup after having copied its content onto the target disk drive. At this early point of the procedure the OS Setup has only access to the content of the boot.wim.
That is why all required storage drivers have to be integrated into the boot.wim ("Microsoft Windows Setup") as well.
Okay, then I’ll give that a try. Thanks