How to Extract Drivers from an EXE Installer –
Most vendor driver downloads are self-extracting EXEs that wrap the real driver files (.inf, .sys, .cat). Extract those files when you need to inject drivers into an image, deploy them with MDT/SCCM/Intune, install them on a machine where the EXE fails, or keep a clean copy in a driver repository.
Try the methods in order: a vendor extract switch is fastest and cleanest; 7-Zip works on most other packages; capturing the temp folder catches the rest; exporting from a working machine is the fallback when you have no usable installer.
Applies to: Windows 10 and 11, vendor driver packages from Dell, HP, Lenovo, Intel, AMD, NVIDIA, Realtek and similar.
Prerequisites
- Local administrator rights on the machine you work on.
- 7-Zip installed (free; also handles .cab and .msi).
- The driver EXE downloaded from the hardware vendor’s official support site — never from third-party driver sites.
- An empty target folder, for example
C:\Drivers\<Model>\<Device>. Keep paths short; some installers fail on long paths. - Optional: Process Monitor for Method 3, and innoextract for Inno Setup packages.
Method 1: Use the vendor’s extract switch
Many packages extract themselves when run with the right switch. Open an elevated Command Prompt in the download folder and run the command for your vendor or installer type.
| Vendor / installer type | Command | Notes |
|---|---|---|
| Dell Update Package (DUP) | driver.exe /s /e=C:\Drivers\Dell | Or run the EXE and click Extract in the dialog. |
| HP SoftPaq | sp12345.exe /e /s /f C:\Drivers\HP | /e extract only, /f folder, /s silent. |
| Lenovo | driver.exe /VERYSILENT /DIR=C:\Drivers\Lenovo /EXTRACT=YES | Without /DIR, Lenovo extracts to C:\Drivers. |
| Intel | driver.exe -extract C:\Drivers\Intel | Some older packages use -a -p C:\Drivers\Intel. |
InstallShield setup.exe | setup.exe /a | Administrative install; prompts for a network location to unpack to. |
| MSI inside the package | msiexec /a driver.msi /qb TARGETDIR=C:\Drivers\MSI | Unpacks the MSI’s files without installing. |
| WiX Burn bundle | setup.exe /layout C:\Drivers\Bundle | Writes the bundle’s payloads to the folder. |
| Inno Setup | innoextract driver.exe -d C:\Drivers\Inno | Inno packages often show “Inno Setup” in File > Properties > Details. |
To find an unknown package’s switches, run driver.exe /?, driver.exe -h or driver.exe /help — many print a list. Check the vendor’s release notes too; HP and Dell document their switches there.
When the command finishes, open the target folder and confirm it contains .inf files (see Verify and deploy).
Method 2: Open the EXE with 7-Zip
Most self-extracting EXEs (7z SFX, ZIP SFX, CAB, NSIS, NVIDIA and many Realtek packages) are archives that 7-Zip opens directly.
- Right-click the EXE and choose 7-Zip > Open archive.
- Browse the contents. If you see folders and files such as
setup.exe,.inf,.cabor.msi, the package is extractable. - Choose 7-Zip > Extract to “<name>”, or from the command line:
7z x driver.exe -oC:\Drivers\Device. - Look for nested packages and extract those too:
.cab→expand -F:* file.cab C:\Drivers\Deviceor 7-Zip..msi→msiexec /aas in Method 1, or 7-Zip (file names may come out garbled; msiexec is cleaner)..zipor another.exe→ repeat this method.
- Stop when you reach a folder containing
.inf,.sysand.catfiles.
If 7-Zip shows only PE sections such as .text, .rsrc and .data, the EXE is a real program, not an archive. Go to Method 3.
Method 3: Capture the files while the installer runs
Installers that can’t be opened still unpack their files to disk before installing. Catch them there.
- Run the EXE as administrator.
- When the first wizard screen appears (Welcome, License or Next), stop — don’t click Next or Cancel.
- Open each of these locations and sort by Date modified to find the newest folder:
%TEMP%(type it in the Explorer address bar)C:\Windows\Temp- Vendor defaults:
C:\SWSetup(HP),C:\Dell\Drivers(Dell),C:\Drivers(Lenovo),C:\AMD,C:\Intel,C:\NVIDIA
- Copy the whole folder to
C:\Drivers\Device. - Now cancel the installer. Most installers delete the temp folder on exit, so copy first.
Can’t find the folder? Start Process Monitor, filter on Process Name is driver.exe and Operation is WriteFile, then run the installer. The Path column shows where it writes.
Method 4: Export from a machine that already has the driver
If the installer won’t cooperate, install it normally on one machine, then export the driver from the Windows driver store. This exports only third-party drivers, not the inbox drivers Windows ships with.
- Open an elevated Command Prompt or PowerShell.
- Find the driver’s published name (
oem##.inf):pnputil /enum-drivers— match on Provider name and Class.
- Export one driver or all of them:
- One:
pnputil /export-driver oem42.inf C:\DriverExport - All:
pnputil /export-driver * C:\DriverExport - PowerShell, all:
Export-WindowsDriver -Online -Destination C:\DriverExport
- One:
- Each driver lands in its own subfolder named after its original INF.
The export contains the driver package only. Companion apps (control panels, audio consoles, utilities) are not included.
Verify and deploy the extracted driver
A usable driver package has three file types in the same folder: .inf (install instructions), .sys (the driver) and .cat (the signature catalog).
Check it matches the hardware
- In Device Manager, open the device > Properties > Details > Hardware Ids. Copy the top value, e.g.
PCI\VEN_8086&DEV_15F3. - Search the extracted folder for it:
findstr /s /i /m "VEN_8086&DEV_15F3" C:\Drivers\*.inf. A hit means the package supports the device. - Pick the right architecture folder (
x64,amd64,Win64) if the package holds several.
Install or deploy it
| Scenario | How |
|---|---|
| One running PC | pnputil /add-driver C:\Drivers\Device\*.inf /subdirs /install |
| One device, by hand | Device Manager > Update driver > Browse my computer > point at the folder, tick Include subfolders |
| Offline Windows image (WIM) | dism /Image:C:\Mount /Add-Driver /Driver:C:\Drivers /Recurse |
| MDT | Deployment Workbench > Out-of-Box Drivers > Import Drivers |
| Configuration Manager | Software Library > Drivers > Import Driver, then add to a driver package |
| Intune | Package with pnputil as a Win32 app, or use Windows Driver Update management |
Troubleshooting and tips
| Symptom | Likely cause | Fix |
|---|---|---|
Extracted folder has no .inf | Package is a utility, firmware/BIOS update or app, not a driver | Check the vendor page for a separate driver download; firmware can’t be deployed this way. |
| Extract switch does nothing | Wrong switch or not elevated | Run as administrator; try /?, then Methods 2–3. |
| Temp folder vanishes before you copy it | Installer cleans up on exit or after extraction | Copy while the first wizard screen is still open; use Process Monitor to find the path faster. |
pnputil reports “no matching devices” | INF doesn’t list this hardware ID, or wrong architecture | Recheck the hardware ID and the x64 folder; get the model-specific package. |
| Install blocked: signature error | Missing or altered .cat file | Keep all files from the INF’s folder together; re-extract from the original EXE. |
| Antivirus quarantines files during extraction | Heuristic flag on SFX unpacking | Confirm the EXE is vendor-signed, then extract in an excluded folder. |
Before extracting any EXE, confirm it is genuine: right-click > Properties > Digital Signatures should show the hardware vendor, or run Get-AuthenticodeSignature .\driver.exe and check for Valid.
Keep a tidy repository. Store each package as Vendor\Model\OS\Device\Version, and keep the original EXE beside the extracted files so you can re-extract later.
DCH drivers. Modern “DCH” packages split the driver from its control app, which is distributed through the Microsoft Store. Extracting gives you the driver; deploy the app separately if users need it.