Using the 'Load Drivers' Option in Windows Installation to Pre-Load All Necessary Drivers?

During the Windows installation, there's a "Load drivers" option that many users use to recognize the hard drive on laptops with Intel processors. My question is, can other drivers also be added in this way so that we don’t have to install each driver individually after installing Windows? Since drivers with the .inf extension are in the Windows installation folder, can we back them up and use them in the next clean install? Has anyone tested this?

Wouldn't it be easier to just inject the drivers into the install.wim?

pseymour said:

Wouldn't it be easier to just inject the drivers into the install.wim?

Click to expand...

If doing this isn't easy for you, you could also follow this tutorial:

I was thinking more like hsehestedt's handy little

pseymour said:

Wouldn't it be easier to just inject the drivers into the install.wim?

Click to expand...

Are there any differences after installation? because I can't explain to all my "Q&A website" users about how to inject the drivers to iso file. also, I think this is easier to add drivers during installation...

Guys! I know how to add drivers with DISM to WIM image or even better, add updates and debloat the iso file. Please just answer my question nothing more. thanks.

Sheikh said:

Just answer my question nothing more. thanks.

Click to expand...

Or I can just abandon the thread. Adios.

pseymour said:

Or I can just abandon the thread. Adios.

Click to expand...

NOOOO I just don't want to waste your time because I've tested other things.
Since English is not my native language and it is quite different from your language, my tone might make you think I'm being rude or ungrateful. However, I just want to express my thoughts in the shortest way possible so that English speakers can better understand what I want. Therefore, if the conversation deviates from my goal, I will try to eliminate the diversion. Sorry if I caused you any distress.

A non-DISM method is to create an unattended file on the USB media.

For boot-critical devices, like SATA/NVME/RST controllers, you can copy driver files to USB folder \$WinPeDriver$. This may cause problems with drive numbering, because $WinPeDriver$ drivers are loaded into memory last. Drives 0 & 1 could now be identified as drives 1 & 0.

For non-critical drivers, copy them to the USB's \sources\$OEM$ folders and use DriverPaths to point to a local C: drive folder. Which $OEM$ path is up to you. Setup wll copy everything in the $OEM$ folders to the target disk before it reboots out of WinPE. These drivers will be loaded in the specialize pass.

These are known (and documented) methods for people who don't use DISM integration.

garlin said:

A non-DISM method is to create an unattended file on the USB media.

For boot-critical devices, like SATA/NVME/RST controllers, you can copy driver files to USB folder \$WinPeDriver$. This may cause problems with drive numbering, because $WinPeDriver$ drivers are loaded into memory last. Drives 0 & 1 could now be identified as drives 1 & 0.

For non-critical drivers, copy them to the USB's \sources\$OEM$ folders and use DriverPaths to point to a local C: drive folder. Which $OEM$ path is up to you. Setup wll copy everything in the $OEM$ folders to the target disk before it reboots out of WinPE. These drivers will be loaded in the specialize pass.

These are known (and documented) methods for people who don't use DISM integration.

Click to expand...

if I copy every .inf file to a specific folder named "my drivers" in my bootable flash drive and then, in the installation process I choose the "Load Drivers" option and select all of them, will it do the same thing?

Load Driver will only load one driver, because it's only intended to fix the problem of a missing storage controller. WinPE Setup has no other UI option to load drivers for the user. You could open a CMD window with Shift-F10 and run "drvload".

garlin said:

Load Driver will only load one driver, because it's only intended to fix the problem of a missing storage controller. WinPE Setup has no other UI option to load drivers for the user. You could open a CMD window with Shift-F10 and run "drvload".

Click to expand...

Alright so I will not use it.
I've downloaded the latest retail update with UUPdump.net tool. forced it to use DISM to update install.wim, boot.wim and winpe. then I've cleaned up the component store. also I've used this method to ensure having all optimizations. Now I want to use the Rufus to create a "Windows to Go" on my external SSD. then boot from that SSD, install manufacture drivers from my Laptop Support Page, then backup all necessary drivers with DISM to inject them to iso file.
There are plenty of .exe files on support page which I used 7zip to extract and grab .INF and .SYS files for WIFI, Bluetooth & etc. I'm not sure if using this method causes problems or not. maybe some drivers need to install some services and apps to work properly instead of just copying the inf files to windows folder!
Hate using the old method which installs windows, drivers and updates then uses the Sysprep to clean everything related to user account. editing the .iso file using DISM is more professional :)))