Doubt about integrating driver

Status
Not open for further replies.
G

Goldtuga

New Member
Hello. It's the first time I use a tool like this one so I'm sorry if this is a such a noob doubt. My PC requires a SSD driver to be loaded for the Windows 11 installer to recognize the SSD or else I won't be able to install Windows 1 on it.

My question is: if I integrate the driver with NTLite (or other tool) to not have to manually load it every time I want to install Windows 11 in this SSD and use this Windows 11 image on a different PC (which doesn't need a driver to recognize the SSD or might need a different one) to install Windows 11, will I have any issue?

Just for curiosiry, what about integrating other drivers and installing Windows 11, like those regarding audio, network, etc., in PCs with different ones?
 
Last edited:
Every PC is a different. Windows includes a set of drivers, which might fit most PC's at some common (and generic) level.

Where you'll have the most problems are with storage and network drivers, especially with NVME devices. A SATA SSD doesn't really require a driver because it's treated as a normal SATA disk. If you need to have a shared ISO that works on different PC's, it's acceptable to integrate all the different drivers that each PC requires into the same image.

The one exception is watch out for Intel RST drivers, they can be very specific to a controller model.

The unused drivers don't harm your system, they just waste a little extra disk space. Windows will only load the drivers that match hardware ID's found on the PC.
 
The only drivers you dont want to add are gpu and audio drivers, some of them are large and will really bloat out your iso.
If you are using a usb audio interface like i am then you can add the driver if its small.
 
garlin said:
Every PC is a different. Windows includes a set of drivers, which might fit most PC's at some common (and generic) level.

Where you'll have the most problems are with storage and network drivers, especially with NVME devices. A SATA SSD doesn't really require a driver because it's treated as a normal SATA disk. If you need to have a shared ISO that works on different PC's, it's acceptable to integrate all the different drivers that each PC requires into the same image.

The one exception is watch out for Intel RST drivers, they can be very specific to a controller model.

The unused drivers don't harm your system, they just waste a little extra disk space. Windows will only load the drivers that match hardware ID's found on the PC.
Click to expand...

When I mentioned the SSD driver, I actually meant the Intel Rapid Storage Technology F6 driver. I guess I shouldn't integrate it, then.

On another note, it seems I made a mistake by creating a Win10XPE Windows 11 image with the Intel RST driver needed by my PC integrated and used it on another PC which doesn't need a driver to be integrated to show its SSD content, but otherwise, how could I access my PC's SSD if I haven't integrated it? In the other PC, it showed this PC's SSD (but when clicking it, it showed that PC's content and not this one), which I guess might be normal behavior because it thinks it has the same SSD as this one since the driver which was integrated was from this PC.

Clanger said:
The only drivers you dont want to add are gpu and audio drivers, some of them are large and will really bloat out your iso.
If you are using a usb audio interface like i am then you can add the driver if its small.
Click to expand...

So, integrating the Intel RST driver is fine, after all?
 
Last edited:
Intel RST drivers must be integrated. But you can't expect the same RST driver to always work on different Intel controllers.

If you have PC's with different RST controllers, just pay attention. You might need to make more than one ISO, if it doesn't work. Read the driver release notes to see if that driver applies to more than one Intel controller family.
 
garlin said:
Intel RST drivers must be integrated. But you can't expect the same RST driver to always work on different Intel controllers.

If you have PC's with different RST controllers, just pay attention. You might need to make more than one ISO, if it doesn't work. Read the driver release notes to see if that driver applies to more than one Intel controller family.
Click to expand...

I can install it from an USB device since OOBE lets me do it and that way I wouldn't need to integrate them. Anyway, just to be sure, I guess it's better if I don't integrate it if using the same image in different PCs, especially from different brands than mine, I presume.
 
NVIDIA drivers can be integrated. But with one weird trick.

The key is not asking NTLite to scan the extracted NVIDIA driver folder, because it will by default add every driver file present. This is how DriverStore works, every driver you add gets a separate copy of the same DLL's in the FileRepository folders.

Adding multiple NVIDIA drivers (as a group) means you copy the DLL's over and over. About 4GB of data.

Instead if you know which NVIDIA driver nv????.sys is the one for your specific card, then add just that one INF file. Not the entire folder.
 
garlin said:
NVIDIA drivers can be integrated. But with one weird trick.

The key is not asking NTLite to scan the extracted NVIDIA driver folder, because it will by default add every driver file present. This is how DriverStore works, every driver you add gets a separate copy of the same DLL's in the FileRepository folders.

Adding multiple NVIDIA drivers (as a group) means you copy the DLL's over and over. About 4GB of data.

Instead if you know which NVIDIA driver nv????.sys is the one for your specific card, then add just that one INF file. Not the entire folder.
Click to expand...

I'm just interested in this Intel RST driver and asked about the other ones for curiosity.
 
Windows 10 11 User likes to spam multiple forums.
Key words for successful snipe hunting: Portuguese (Portugal), "doubt". Hey my English is magically perfect again(!)
 
Status
Not open for further replies.
Back
Top