Extracting drivers from exe that doesn't have cmd extract switch

I am in the process of building custom images for deployment. Part of that of course is to include the required drivers. Usually I would extract the needed .inf files from the executable for whatever I was needing, i.e. LAN, Chipset, Graphics, etc, from cmd with the appropriate switch. I have run into a few executables where there is no cmd switch for extracting. I have searched and can't find anything more than things like open archive and copy the contents, run the exe and get the contents of the temp folder that it puts things into. The problem with that is running it tells me my system is not compatible(which it isn't) and opening the archive doesn't reveal anything useful.

What I am needing to know is a way to get the files I need from these .exes. These .exe are the drivers from the MB manufacture. I would prefer to stick with what they sent us as these are custom spec'd boards.

Thank you for any help.

GitHub - Bioruebe/UniExtract2: Universal Extractor 2 is an unofficial updated and extended version of the original UniExtract by Jared Breland.


https://github.com/Bioruebe/UniExtract2/releases

SIW2 said:

GitHub - Bioruebe/UniExtract2: Universal Extractor 2 is an unofficial updated and extended version of the original UniExtract by Jared Breland.

UniExtractor2 said it couldn’t find anything.

Kari said:

I would just export the drivers from your reference machine, if that has the same board than machines onto the image will be deployed. It's then an easy task to inject those drivers to deployment image.

The goal is to be able to do this with out one. I am using MDT and trying to get the .inf files to inject into the image. It may not be able to be done without a reference computer and ultimately I will do what I need to. But before I get to that point I want to exhaust as many other options as I can.

Bree said:

Normally these type of .exe files are self-extracting archives, so there's an archive in there somewhere if only you could open it. I usually find that adding a .7z extension to the .exe file will open it it 7-Zip File Manager which can handle most archive formats.

Did this and didn’t see any .inf or the like type files.


The graphics and the USB 3.0 driver installation executable are the current ones I am working with.

Thank you guys for your advice so far.

Kari said:

I would just export the drivers from your reference machine, if that has the same board than machines onto the image will be deployed. It's then an easy task to inject those drivers to deployment image. See tutorial: DISM - Add or Remove Drivers on an Offline Image | Windows 10 Tutorials

This...



… results this:



Kari

Is there a way to do this but by type of drivers? For example only export the LAN drivers once. Then export the graphics drivers, etc. I am using MDT to create my images and would like to be able to keep things separated.

Afaik there is no universal way to extract drivers from exe. Some can be extracted using 7zip, some not. Some can be acquired by running exe, finding install dir in temp & copy it before cancelling installer.

Also you can check website of mobo manufacturer, drivers are often offered both as exe and as zip archive.