Universal Driver installer for NT x86/x64

Hello, Snippet World !!!

DriverSod.cmd started as a PESE plugin to facilitate drivers management and installation.

I created a full contained package that should be able to run on any Windows NT from seven
and upward. Follow Readme instruction for a quick start.
-----------------------------------------------------------------------------
Description:
Install Drivers from any device to any Windows NT installations.
Supports from Win7 and upward. Uses Cabinet files for smaller footprint.
Install drivers and make them available immediately, no restart required.
Works with Complete Installations and all Distributions of Live Windows PE/RE.
Simple syntax with helpful drivers installation troubleshooting commands.
Works from Read Only, writable or Network media. Easy to automate installations.
Supports x86/x64 Architectures. And is modifiable and Expandable to meet
your needs. Packs up to 2 gigs of Drivers in a 500 MO cabinet file.
-----------------------------------------------------------------------------

v0.92
-----------------------------------------------------------------------------
The command now enables users to have very simple syntax to remember and
Powerful tools easy to use. for example: You can now use DriverSod from any
drive letter to export drivers from an host. (/exp) in a booted Windows.
Then use them at will in your PE With (/Imp) to load the saved drivers.
You can cleanup those and create cabinet with cabPack for later uses (/inst).
The command can also be used to install drivers to standard windows NT
installations (/inst /load /imp). You can also create a cmd with
@DriverSod /exp %ComputerName% save it and double click it from usb drive on any
machine to automatically backup Hosts drivers to Folder ..\Drivers_x??\Computername.
Then use them right away in PE (/imp).The command can also generate a batch command
to install up to 8 packs at once (/gen). And also create full cmd and ini to use
in projects (/genx). On a Running host Browse to the DriverSod folder in your
usb drive and start the cmd shortcut to have quick access to DriverSod prompt in
program folder. For a quick access to most useful commands.
Use your project plugin Automation create a  DriverSod.ini to enable / Disable packs
installation at PE Startup.
-----------------------------------------------------------------------------
Simply extract over your current installation and replace files.
-----------------------------------------------------------------------------
Here are links to the x64 driver Packs I made for testing... Use at your own Risks 

Chips.cab (50.3 Mb - Date: 2020-01-12)
Stor.cab (37.6 Mb - Date: 2020-01-12)
Usb.cab (32.5 Mb - Date: 2020-01-12)
Lan.cab (18.4 Mb - Date: 2020-01-12)
Wifi.cab ( 90.5 Mb - Date: 2020-01-12)
Vendors.cab (97.0 Mb - Date: 2020-01-12)
Reader.cab (56.4 Mb - Date: 2020-01-12)
Video.cab (447 Mb - Date: 2020-01-12)
Sound.cab ( 3.0 Mb - Date: 2020-01-12)

(Downloads are slow to start because Google drive Struggle with scanning cabs for viruses)

All credits goes to the great teams at Forum.ru and drp.su for their wonderful work putting together all these .

v0.93
-----------------------------------------------------------------------------
New Routine to Extract and install Offline host drivers in Live PE.

Extract Drivers, Remove doppelgangers, Show extracted drivers
for cleanup Before continuing. Or with /go extract, Remove, install
directly.With no interruption.

DriverSod /off <Path_to_offline_Windows> <Path_to_Tmp_Folder> [/go]

DriverSod /off c:\Windows c:\DrvTmp
-----------------------------------------------------------------------------
I have read that this would need Switch to admin. But as far as I
Have tested this. It works without it as long PE has read access.
-----------------------------------------------------------------------------
Simply extract over your current installation and replace files.
-----------------------------------------------------------------------------

Malok, thanks for your work!

Let me tell you how it went, and my setup.

I was looking for a fresh x86 working win10pese to replace some Paragon imaging ISO, right from Winbuilder.  Everything as indicated, Windows 10 Oct 2018 (1809) ISO, last packages, updates... it just works!


**PROBLEM** I need WIFI support over a wide installed hardware base, so -> SDI driverpacks (huge 2,4 Gb uncompressed)

ISO is working good after DISM integration, no complains.  Every adapter is UP and ready.

Downside, BOOT.WIM grows upto 1,3 Gb. so that ends in a beefy X:\boot.  Now, I can´t start systems with less than 3 Gb. RAM.


I would like to keep memory requeriments as minimal as it could, so DRIVERSOD seems promising.

But not working for me, I don´t know why...


I made custom CAB extracting BOOT.WIM \windows\system32\driverstore\filerepository to a root folder in ISO root, $WinPeDriver$

Everything seems to acomplish your indications; "The Source directory structure in the cab needs to have each driver in a separate directory, and ensure that the INF file are always located in top Directory of the Drivers Folder.  The DEVI Command does not support Recursive parsing of folders inside cabs... etc.

DRIVERSOD /inst wifi
Searching and Installing Drivers from Selected cab for:
Microsoft Windows [Version 10.0.17763.107] x86
Please Wait...

...and nothing happens, drivers won´t install

If I choose (from runing win10pese) right click device, "update driver", browse my computer, go to $WinPeDriver$... all adapters up and ready.


I´m gonna make some test, and I will tell you more.

Thanks in advance!

Hi Justgonnalurkabit,

If SDI Works in your compilation. You can place it in the root of your ISO and run it from there, no need for uncompressed drivers. Just run SDI_auto.bat from your PE and all the packs you have in your sdi/drivers folder will be loaded. Very good to keep boot.wim small.

After Applying your iso to a USB drive, it's a piece of cake to maintain. And It's very hard to beat imo. It's also pretty easy to launch it automatically at PE boot. and it can be used to load drivers in Standard windows installations. Worth every bits of it 22gigs.

hth!

Cabinets are half way to acomplish my goal.  Minimal RAM.

Do you think SDI bat could drive some kind of unnatended installation, post boot?

I will try It...  Thanks, and I will back with results, SDI and DRIVERSOD

Yes it supports unattended installations.