This app is awesome, so easy to use, thanks alot
There is just one thing i can’t seem to figurer out, have downloaded all x64 updates sinde v1607 and want to intergrate them, all but 2 goes well
windows-kb890830-x64-v5.40
windows-kb890830-x64-v5.40_delta
theese have exe entension, how do i intergrate them ?
@Hackerjac :
You cannot integrate any "Malicious Software Removal Tool", because it is not offered as *.cab file. Furthermore the integration would not make any sense, because this tool wil be updated automaticly each month.
ok, thanks alot 
Ok here is my question … I am trying to install original windows 7 ultimate using UEFI /GTP on a laptop and durring installation i realized it doesn’t detect my HDD. I did the following settings in the bios:
boot mode : Legacy Support
Usb Legacy : enabled
Sata Controller mode : AHCI
Can you tell me which drivers i need to integrate in the image ?? maybe there are some AIO driver pack that can help recognize most of the hardware ??
Without any details about your special system (chipset or - even better - HardwareIDs of your on-board SATA AHCI Controller) I cannot help you.
Excellent tutorial Fernando, one of the best I’ve seen.
I’ve followed it explicitly but I’m still having an issue. I’ve integrated the Samsung NVME drivers from the page you pointed out. I’m using a Dell system disk with Windows 7 Pro 64 bit.
When loading up the Boot CD on a virtual machine it stops the install and says that the secnvme.sys file is missing or corrupt.
I grabbed the drivers from here:
Recommended AHCI/RAID and NVMe Drivers
The “Samsung NVMe drivers v2.0.0.1607 WHQ” as you indicated they were the newest.
Any ideas on what I’m doing wrong? I’m working off of C:\NTLite as the directory. I’ve got the sammy drivers in a folder in C:\NTLite called simply “drivers”. I’ve got .cat and .sys files in that folder with the .inf.
BTW, what’s the PE part of Boot.wim? Maybe that has to be updated with the drivers as well?
And lastly, how can I add the drivers to the other OSes (Home, ultimate, etc All 64 bit, of course) when they disappear in NTLite when I run the process on the pro part? I’ve tried closing the history and re-adding the folder but it reverts back to history
Thanks,
Found a solution…even if I can’t explain it.
I used the older set of drivers that you listed on your driver page. I can only surmise that the installer needed both 32 and 64 bit drivers…for some reason.
That’s the only difference between the two. The new one seems to be exclusively 64 bit, if you read the inf. The older one has a section for 32 bit and 64 bit. In addition, the older on has another driver called secnvmeF.sys. I’m not sure if that matters.
Any input on these observations and answers to the other questions I asked would be greatly appreciated when you get a sec Fernando.
I really thank you for this excellent tutorial and the makers of NTLite. It’s way better than using the AIK kit from MS.
If you want to integrate drivers (and Patches, too) into editions different from "Pro" you will have to select "Home" or "Ultimate". All these editions are bundled in Install.WIM.
Advice from [email protected]: Drivers of devices niot supported by Win7 have to be integrated into both editions of Boot.wim.
Regards, Nemo
@kirm :
Welcome at Win-RAID Forum!
You are right: The latest "pure" Samsung NVMe driver v2.0.0.1607, which I am offering within the start post of >this< thread, is only usable with 64bit Operating Systems from Win8 up. I just have corrected the related description of the driver.
The additional SCSI filter driver named secnvmeF.sys is only required for older Windows Operating Systems up to Win7. Win8/8.1/10 neither need nor use this driver.
Windows PE is a bootable Windows Live medium and has to be processed similar to the "nomal" Windows Setup (= boot.wim).
As Nemo already has explained, the install.wim may contain different Windows images (e.g. "Professional", "Home" etc.). If you want to customize any of the other Windows images (or all of them), you should do it after having finished the customization of the first image (here: "Pro").
Regards
Dieter (alias Fernando)
Thanks a lot. And from what Nemo mentioned that’s why, at home on the target PC, it’s not working. I have to add the driver to the PE part. Damn, I wish I had known that before.
The problem is that after I’ve modified one of the boot sections the other one isn’t visible. I tried closing history and then opening the folder again but it just opens in history. Do I have to close down NTLite completely and then open it again and add the folder over?
Here’s what I mean: here
I’ve opened up the image at home and there are no more options.
Thanks for the help.
It will be visible again after having finished the customization of the related image.
No, you have not to exit NTLite, but just to finalize NTLite’s work on the current image. After having done that, you can click onto "Source" on the left hand side, get accees to all the images, which are within the INSTALL.WIM and BOOT.WIM of your NTLite-Work folder, and can start processing the next image (e.g. "Win10 Home").
Off topic:
Please avoid unneeded blank lines (to save space).
I must have a hobbled version of NTLite because it’s not showing me anything but the two areas I modified after the modification. Just like the image I posted in my last post. Anyway it’s not working but I did find something that might help. There is a hotfix for this and I wanted to post here to give back a bit after all your help. If you look at the instructions MS says to add the fix to both boot images. That backs up what Nemo said. I don’t think I’m going to trust NTLite anymore as it’s not allowing me to do that. I’m going to use the AIK and DISM to add the drivers and the hotfix. It’s an ugly CLI mess but at least I can do what I have too.
I doubt, that this is a bug of NTLite. Otherwise I would have already read about it.
Are you sure, that the ISO file, which you have used as source, contains more than 1 Windows image (here: Windows 7 Professional)?
Yes it most definitely does. I see 4 but after I’ve modified the image there is only the one I’ve modified. Maybe I should try it with another disk?
Regarding my post for the MS hotfix…I’m doing it right now. In the interest of helping others that want to do it here are some things you’ll need to know. Firstly read all the instructions over carefully before proceeding. There are some changes you’ll have to make.
/mount-image should be mount-wim; unmount-image should be unmount-wmi; imagefile should be wimfile
dism /Mount-Image /ImageFile:c:\temp\mount\windows\system32\recovery\winre.wim /Index:1 /MountDir:c:\temp\winremount ← This step only works for index 1. All the other indexes throw an error "The specified image does not exist in the WIM. Check the WIM first for existing images."
I don’t know how MS could be so stupid with their own documentation.
I want to burn it to disk now but it’s way too big. I’ll have to use a USB key. I’ll update you on how it goes.
I’m also going to try this again with NTLite to see what happens.
Here are some screenshots with what NTLite is doing:
Updating Source
After Update
This is just bizzarre! I’ve got to be doing something wrong. Any ideas?
@kirm :
I don’t see any NTLite bug.
You should not compare the “Image History” with the “Mounted Image”.
The Image History shows, what you have done, and that seems to be absolutely correct.
What you have to do, if you want to process the other Windows images, which are within the source ISO file, is to click onto “Add” and load the complete source again.
You obviously had finished the NTLite work completely, when you took the second screenshot.
I know it’s something I’m doing but…doing what you say just gets me the same thing is history. Researching…
GOT IT! There is a box that says export. Uncheck that and then you get the expected behavior. I checked your tutorial and it’s there. GREAT! On with the fun.
Something else I found out. Make sure and recompress the WIM files. it really cuts down on the size for the final ISO.
I’m putting this out there as well if you’re using a Samsung NMVE driver.
“Samsung Drivers (Ver: 1.4.7.6) cannot be used at the same time as the Microsoft Windows 7 SP1 or Windows Server 2008 R2 SP1 HotFixes (KB2990941, KB3087873)”
Just letting you know that the hotfix did work. Firstly, I had to work through some other issues, USB drivers. The mobo is so new and Win 7 is so old.
Remember though that my experience here is with the Samsung 950 pro NVME stick booting Windows 7 64 bit SP 1.
Anyway, if anyone here goes that way there are some strange things about the install. When you come up to the partitioning part of the install, Windows will swear it can’t use the disk (it should show up in the list). But if you click “advanced” you can still create the partitions. Since I’m dual booting I gave Windows 80 gigs and it created the efi boot partition and the MS reserved partition. After that, it STILL said it couldn’t use the disk. You’ll notice though that the “next” button is active. I pressed it and Windows proceeded with the install. In my case it took a long time after decompressing the files to continue the install but it did complete. Mission accomplished…but not in the George Bush sense of the term.
Thank you Fernando and Nemo for all your help, you’ve been great and this forum has been a wealth of info. I hope I’ve added something to this forum as well, instead of just taking and not giving anything back.
@Fernando ,
I do use also NTLite Tool, (Free version) to add/remove drivers (Storage, USB or LAN) from W10 WinPE x64 image to customize them for any PC hardware the USB WinPE boot media of the System Backup/Restore Tools available on the market (Acronis, Aomei, etc…)
You should indicate this in the 1st Post, that can help somebody.
Your Guide does apply also for modding WinPE or WinRE image, mainly on how to use NTLite Tool.
@100PIER :
Thanks for your tip. I agree with you, that the start post of this thread should contain a remark regarding the ability of NTLite to customize a WinPE image.
Meanwile I have tried to follow your advise without risking to additionally blow up my guide.
Please have a look into the updated start post and tell me, if it is ok for you.
I will not write an extra guide for the customization of a WinPE image (incl. screenshots), because only advanced NTLite users like you will use this option.