Hi Fernando, I'm new to this forum and so glad to be one of the members.
My question is:
I tried to follow your guide and everything went OK until on the driver option, I cannot add any drivers.
I tried using INF or folder for multiple drivers but nothing happens, as if I did not do anything.
I was able to select the drivers I want but after clicking OK, nothing happens.

Please help. Thanks.

Hello, Fernando!

I've integrated the Intel SATA AHCI controller drivers successfully into the Win7 installation media many times using the free version of NTLite.

However I'm unable to integrate the Intel SATA AHCI controller drivers for Intel 7 Series chipset SATA AHCI controller (Intel Panther Point HM76, Intel Sandy Bridge). After the installation Win7 still uses some standard driver for the sata controller even though I remove all drivers that could be removed with NTLite Free. Chipset, ethernet, wifi, webcam drivers integrate successfully. Updating the 7 Series chipset SATA AHCI controller manually (using the same ahci drivers) works. I tried with Intel SATA AHCI v11.1.0.1006 which are on the laptop's website drivers section. I downloaded older / newer versions - nothing works. They all install fine manually but don't install if I integrate them with NTLite Free. I tried to integrate the drivers via INSTALL.WIM and BOOT.WIM. It didn't work either way. USB-drive / optical drive - doesn't matter. HP laptop, Toshiba SATA-II hard drive.

I'm running out of ideas. Integrating Intel SATA AHCI controller drivers into Win7 for other PCs / laptops works flawlessly.

RESOLVED!
There should be no blank space in the folder's name where the AHCI driver resides.

Strangely enough "Card Reader" works (for the card reader driver anyway) but "SATA Floppy Image" doesn't work for the AHCI driver.
I don't know if this is a Win7 limitation / bug or it's related to NTLite free.
IMHO NTLite should display a warning when you add AHCI drivers from a folder that contain blank spaces in its name.

I'm going to rename all folders containing drivers for integration. Just in case ;)

@Ivanov3030:
There maybe in internal limit for the length of fully qualified directory name for files used with NTLite!
That could be the explanation why "...\Card Reader\xyz.inf" worked and "...\SATA Floppy Image\blablabla.inf" exceeds this limit.

If you ever work with Abbodi's esd-decrypter-wimlib for decrypting MS' ESD file to ISOs you have to follow
"- Extract this package contents to a folder with simple path (example: C:\ESD)." (Quote from ReadMe.txt)

Regards, Nemo

Hi Fernando,

Firstly, I'm trying to customize a Windows 10 64-bit English US version ISO, and seeing that I'm very new to all these, I really hope you can help me out.

So as I was integrating drivers into the ISO using NTlite, as I was integrating the Thunderbolt driver, where there are 6 .inf files, two of the files cannot be integrated (tp2p70i.inf and tbt70i.inf). The reason given by NTlite was "wrong architecture". The other four files can be integrated (tp2p70x.inf, tp2p81x.inf, tbt70x.inf, tbt81x.inf)

What does wrong architecture mean? Is it referring to the ISO that I am customizing? Or is it referring to the computer that I am using NTlite on?

More importantly, how can I fix this problem?

Thanks for reading and I will really appreciate it if you could help me understand more!

Hi, and thanks for the reply and for the useful information!

So if I understand correctly, NTlite helped me eliminate the 32bit drivers, so I integrate the 64bit drivers into the ISO?

Anyway thanks again for your guide and to the creator of NTlite! :)

Hi Fernando,

i have some troubles modifying my Win10 Image.
The unchanged Image boots / installs fine.
But as soon as i change something with NTlite, i get an immediate bluescreen just before the Windos Installation ( during boot from USB Installation Stick).

It even get a Bluescreen when i dont add the 11.2 driver, but only delete the newer drivers.

I did the modifications to install.wim and boot.wim

Most of the time, the bluescreen names the driver iAStor.sys (even if the 11.2 driver was not integrated, and the only the newer drivers were deleted).

No spaces or crazy letters in the folder structure.

I used Ntlite on 2 different PCs - no difference.

Do you have any more input or suggestions?

edit: RAID mode is enabled in BIOS.
I did not integrate the 11.2 for testing purposes and i thought i could add the driver during the installation (like back in the days).
TL;DR:
as soon as i change the image with NTlite i get a BSOD during installation boot.

Hi Fernando,

I am at it again right now.
I used a folder on my C drive before (c/ntlite), now i created a new partition exclusivley for ntlite. I am also trying your modded+signed drivers.
Wish me luck :)
The image i use is from the Windows Media creation Tool. By default it comes with an install.esd instead of an install.wim. NTlite converts the .esd file to a .wim file upon first mounting of the image. Could that be the cause for my troubles?