Win7 Setup only accepts WHQL certified drivers, if you try to load them at the beginning of the OS installation procedure.
That is why I gave you the advice to integrate the driver into the Win7 image by using a tool like NTLite.
Please integrate yourself NVMe driver and USB 3.0 driver to boot.wim (Win7 x64) and send it to me. I believe this will eliminate the possibility of my mistake. If your boot.wim, the installer will refuse to see the SSD so your modified driver is not suitable for him.
M/B: MSI B250M PRO-VDH
No, my friend, this not my task and I will not do that.
Nobody has forced you or any other user
a) to buy an Intel NVMe SSD, which is natively not supported by any available Intel NVMe driver, and
b) to install a Windows OS, which natively doesnāt support NVMe at all.
If you should not suucceed by following my guide (note: you have to integrate the mod+signed driver into the BOOT.WIM and additionally into the INSTALL.WIM), I recommend to contact the Intel and/or Microsoft Support and ask for help. It is not my task to compensate their deficiencies.
I understood whatās the matter. NTLite does not work properly with boot.wim, resulting in a standard NVMe driver from Microsoft not working. If I do everything manually (for example, I used this instruction from the HP website and took the original boot.wim), then the SSD becomes visible. True, you can see that only through Shift + F10 > DiskPart > List Disk, because through the GUI, it does not reach the selection of the partition for installation (it breaks off on the standard message about driver shortage, I suspect that the matter is in the absence of the required USB driverā¦ Although the USB drive through the Browse is visibleā¦ Hmmā¦).
This is simply not true.
NTLite works properly with an untouched BOOT.WIM image. Since Win7 natively doesnāt contain any NVMe driver, NTLite cannot make such driver unusable.
If you have integrated the MS NVMe driver via MS Hotfix into the Win7 BOOT.WIM image, you should not additionally integrate or load any other NVMe driver.
http://imgur.com/a/uxlQO
Iām using NTLite version 1.4.0.5525 64-bit, and am working on an image I created in 2015. I uninstalled a previous version of nLite and discarded the excutable. I then found that the feature to remove drivers no longer wanted was removed. Since I have already removed some MS drivers I guess putting 2 drivers for the USB extensible drivers wonāt cause an issue considering their size. However as in the screenshot I seem unable to remove hotfixes already applied. Since I will be integrating the unofficial sp2 rollup into this slipstream have you got an advice? I have also an untouched ISO of win 7 SP1 64 bit ultimate. If I used that would my integrated updated drivers be installed over the MS defaults?
@EmmaRoyd : Done : https://www.ntlite.com/discussions/#/disā¦64bit-ult-image
megatron, as this is an NTLite question, i kindly ask if you can post on the NTLite forum where Nuhi, myself, or other forum members will happily answer any questions you have over and above basic driver integration. 
@ all:
Due to some minor changes regarding the NTLite processing, which were introduced with the NTLite v1.4, I have updated today the start post of this thread.
Update of the Start Post
Changelog:
- Updated: parts of the guide
- New: all inserted screenshots
Good luck with the revised guide!
Dieter (alias Fernando)
good
Hi,
I have a strange issue regarding the injection of the latest Samsung NVMe drivers (2.3.0.1709) via DISM command line. It works flawlessly with the boot.wim, but is failing with the install.wim. The error return code is 15100. With the previous driver (2.2.0.1703) the issue doesnāt occur. Any suggestions?
Iām using this command line ādism /Image:d:\NVME\temp\mount /Add-Driver /Driver:d:\NVME\temp\drivers /Recurseā with dism 6.3.9600. NTlite seems to have no issue with the driver (green indicator)
@Unikat2000 :
Thanks for your report, although it has not much to do with my NTLite usage guide, which is within the start post.
Which OS did you customize and which one was your host OS?
Hi Fernando, I hope you can answer this question for me ā¦ I got a new laptop, hated windows 10, and desperately wanted to get win7 installed on it in a particular configuration ā¦ I think I am almost there, but something is missing.
I set up intel rst in the UEFI BIOS settings and enabled uefi boot
I modified the install.wim with dism to insert some drivers, but other guides talked about tricking the new i7-7700k cpu into letting win7 install by either inserting the win7 install.wim into a win10 image, OR by inserting the win10 boot.wim and setup.exe into a win7 image ( with modified install.wim ) ā¦ and it almost works
I can get the win10 installer to offer me to install windows 7
I can load the raid drivers to recognise my ssd raid 0
AND it goes ahead, partitions the drive, and seems to install correctly ā¦
BUT when it reboots, I get the same error from the windows boot manager that I got at first until I found a good guide for getting the USB to boot properly, which is that WBM error about not being able to read the \efi\microsoft\boot\bcd ā¦
NOW ā¦ what I am wondering is this:
1 - am i supposed to further modify the install.wim so that the bcd and similar files are copied to a root \efi\boot folder ( just like I did on the USB ), and also copy the bootmgfw.efi file again to some other location inside the install.wim and rename it to bootx64.efi so that when windows 7 installs, it puts these things in the correct places on the partitions of the nvme ( ssd m.2 ) raid, just as I had to get them in the correct places on the USB installer to make that work ā¦
ā¦ OR ā¦
2 - ( if I am reading your site correctly ) am I supposed to forget about tricking the win 7 installer by using win 10 installer components, and instead just modify the boot.wim in addition to the install.wim (?)
ā¦ because the thing is, I thought option 2 was the correct answer from everything I was reading, but I just couldnt get a USB to install it no matter what I tried, until I switched to combining methods with the win 10 components ā¦ but even though it does install, it wont reboot, so i never get to go through that initial process of setting up win7
I tried to fix it by installing win 10 as a dual boot ( on the other sata based raid ), which ( if I again loaded the raid drivers ) would recognise win 7 as a dual boot option, and after instaling win 10 it would allow me to select to boot into win 7, but as win 7 had never done its first boot up, I think it lost whatever information it would usually carry into that process ā¦ so I would get the windows logo with the words "windows is starting", but it would just sit there and not go any further
So I am a little stuck as to what to try to do next ā¦ can you help me to get this working, because I would really like to have this operating the way I want it, and I feel like after weeks of trying to make a headless linux server which would run a win7 vm with GPU pass through ( near bare metal speeds, but couldnt get it to work ), this is my next best option, and I would like to boot it with the 3xSSD (m.2) raid0 for win7, though if it needs it, I dont mind putting it dual boot with win10 on a small partition of the 2xhybrid raid1 (sata) ā¦ but I am just exhausted from sleep deprivation and my brain is fried.
Any ideas?
@GalacticPrez :
Welcome to the Win-RAID Forum!
You have to integrate the RAID drivers into the boot.wim as well (if you donāt want to use the Win7 in-box ones).
Although your questions have not much to do with the topic ādriver integrationā, I try to answer some of them:
1. According to my experience it is not a good idea to mix Win7 and Win10 images resp. parts of them.
2. If you have installed Win7 after the newer OS Win10 with the intention to get a dual-boot system, you cannot boot into both Operating Systems because of wrong/not matching boot sector entries. You can solve this problem by using a tool like EasyBCD.
If you want more informations about these topics, I recommend to post them into >this< Forum.
Regards
Dieter (alias Fernando)
What about the NVMe drivers, do I need to somehow extract them from the windows package update so that Win7 can talk to the pcie m.2 ssdās in the raid? Or is it just the raid drivers alone? Is this the only reason I would get that \boot\microsoft\efi\bcd error, because having set up rst raid in bios, the USB canāt even begin installation without it?
The generic MS NVMe driver (integrated as MS Hotfix) will not be able to detect your NVMe SSDs and the related Windows Boot Manager, if the SSDs are members of an Intel RST RAID array.
Consequence: You have to integrate a suitable Intel RST NVMe driver (v14.8.xx.xxxx or higher), which supports your already existing Intel RST NVMe RAID array, into the install.wim and boot.wim of your Win7 image according my guide.
Nevertheless you can additionally integrate the MS NVMe Hotfix (look >here<) into the Win7 Image to get NVMe support for not-RAIDed NVMe SSDs.
Off topic:
>Here< is an easy to understand guide about how to get the previously customized Win7 Image properly installed in UEFI mode.
I have MSI B350 Tomahawk with Ryzen 7 1700X CPU.
This Guide comes out as first result in my Google search for āintegrate drivers windows 7ā. After 4-5 tries with NTLite + AMD RAID and AMD Chipset Drivers that failed, i found on other website a better solution:
MSI Smart Tool + Windows 7 ISO
MSI Smart Tool is very easy to use. With 3 or 4 clicks i managed to use mouse and keyboard within Windows Installation and all of my hard drives where visible out of the box.
Hi its me again. I want to make this part of my unattended install:
https://gist.github.com/matthewjberger/2ā¦fa34e597f457b7f
Its probably obvious how to do it but havenāt visited this topic in a while.
@megatron :
I am sorry, but I cannot see any relationship between your project and the topic of this thread.