Driver Extractor для Windows

Оценка:	1 2 3 4 5 4.33 /5 голосов — 6
Лицензия:	Бесплатная
Версия:	2.0 | Сообщить о новой версии
Обновлено:	10.11.2020
ОС:	Windows 10, 8, 7, XP
Интерфейс:	Английский
Разработчик:	AloneWolf Software
Категория:	Программы для драйверов
Загрузок (сегодня/всего):	2 / 10 113 | Статистика
Размер:	929 Кб
СКАЧАТЬ

Driver Extractor бесплатная портативная утилита, предназначенная для извлечения файлов драйверов (аудио, видеоадаптера, модема, других) из уже установленной операционной системы (поддерживаются версии от Windows XP до 10) которые могут потребоваться при переустановке ОС либо для резервного копирования в выбранную папку.

Driver Extractor показывает дату драйвера и производителя данного устройства, с разбиением по классам устройств, так что Вы легко можете найти и сделать бэкап нужного Вам драйвера, чтобы потом переустановить его на том же или другом компьютере, но при этом всегда учитывайте ОС и версию драйвера на совместимость.

IObit Driver Booster — полезная программа, автоматически сканирующая и определяющая драйвера на ПК.

Display Driver Uninstaller — бесплатная программа для удаления из системы драйверов видеокарт NVIDIA и AMD.

Snappy Driver Installer — программа для поиска и установки драйверов. Предлагает пользователю.

Бесплатная и безопасная программа, которая предлагает миллионы драйверов.

RivaTuner — Утилита предназначена для тонкой настройки параметров видеокарт на чипах от NVIDIA и.

DriverPack Solution — пакет, состоящий из наиболее актуальных драйверов для всевозможных конфигураций ПК, а также для разнообразных моделей ноутбуков.

Отзывы о программе Driver Extractor

imperialregent про Driver Extractor 1.1 [11-11-2020]

Совершенно бессмысленная программа для тех, кто переустанавливает систему. В наше время, когда есть автоэкстракторы — тупо сидеть и вставлять в систему по одному драйверу. ну это верх извращения. Напомню для тех, кто не в курсе: драйвер можно выдернуть более продвинутыми прогами, которые сделают из них EXE-шники. Запускаешь их по очереди, и все.
1 | 4 | Ответить

[Windows 10] Extracting Microsoft drivers from Windows OS

Summary

Downloading and deploying drivers in an environment where Windows Update is disabled using pnputil.exe

Issue

Many enterprise environments disable Windows Update and use their own method for deploying software updates (e.g. SCCM). This is usually achieved using a GPO or the registry key:

This poses an interesting question when it comes to Microsoft driver updates. What do you do when a peripheral device requires a driver update?

One way is to search the Microsoft Update Catalog:
https://www.catalog.update.microsoft.com/

But what happens if you can’t get the driver from MS Update? As an example lets presume a webcam driver is causing issues but the fix is located in a newer version of the driver. Many webcams manufacturers no longer provide driver packs to manually download and deploy. Instead they opt to hardware certify with Microsoft and have the driver added to Windows Update.

A quick google will reveal PowerShell commands such as

The issue is however that these will only extract third party drivers, not quite what we are looking for.

Resolution

There is a utility built into Windows that was the go-to for printer driver deployments on Windows XP/7 called pnputil

Our tool of choice today still works on Windows 10 (1803) and is great for extracting drivers from a device.

Pnputil is located in the following directory %windir%\system32\pnputil.exe and follows the syntax:

Extract to current directory:

C:\Windows\System32\pnputil.exe /export-driver .inf .

Extract to a specified directory (directory must exist):

C:\Windows\System32\pnputil.exe /export-driver .inf

Implementation

Identifying the driver files

Before extracting the drivers however we need to identify the driver files we need. There are a number of ways to do this such as the below.

Get driver INF file

1. 1. Open device manager
      1. Right click the Start button
      2. Click Device Manager

Or for more restrictive environments

1. 1. 1. Open an elevated command prompt
      2. Type devmgmt.msc
   2. Open device properties
      1. Navigate to the device in question
      2. Right click on the device
      3. Click Properties this will bring up the device device properties page
         
   3. Navigate to Inf name property
      1. Click on the Details tab
      2. Select Inf name from the Properties drop down
         
   4. Get Inf Name(s) listed

Alternatively you can query WMI if a programmatic method is required.

Extract Driver

From a device with a working driver

1. Open an elevated command prompt
2. Type the following command to confirm the driver is present:
   C:\Windows\System32\pnputil.exe /enum-drivers | findstr « .inf”
3. 
   For example:
   C:\Windows\System32\pnputil.exe /enum-drivers | findstr «oem49.inf»
   
4. Type the following to extract the driver
   C:\Windows\System32\pnputil.exe /export-driver .inf .
   For example:
   C:\Windows\System32\pnputil.exe /export-driver oem49.inf .
   As this model of webcam has a Mic built-in, we also need to extract the audio driver
   

You will find the drivers in the folder you specified

Conclusion

These extracted drivers are now ready to deploy using your preferred method.

Manual Install:

Simply right click on the .inf file and click Install on the target machine

Pnputil:

Or you can use pnputil itself to install the driver with the following command line:

C:\Windows\System32\pnputil.exe /add-driver «C:\LogitechDrivers\luvc1564v.inf» /install

For multiple drivers, place all drivers in the same directory and use a wildcard
C:\Windows\System32\pnputil /add-driver

Good article showing the basic steps on how to deploy pnputil using SCCM:

Frustrated IT Engineer

How to extract drivers from .exe packages

Pc manufactures are now using self-extracting EXE packages to install drivers when you down load them from there support websites.

Which is very handy when you have one or two pc’s to install the drivers on to, but not so much when you are building an image for multiple pc’s or trying to look at driver file without having to run the .exe or install it.

This is where the universal extractor software is very helpful tool to use.

Run the Uniextract Installer and go though the steps of installing accepting all the defaults and let it install

Once installed right-click on the self-extracting EXE files you want the driver from and select uniextract files

Universal Extractor context menu

This will open the Universal Extractor file/destination GUI

The top bar is the location of self-extracting EXE file and the bottom bar is the location you wish the file to extracted to.

Universal Extractor file/destination GUI
(Top bar is location of the self-extracting EXE files)
(Bottom bar is location you want it extracted to)

Left click OK and it go though the process of extracting the files out of the self-extracting EXE and put them in the destination folder you specified and there you will find the driver you needed.

How to extract MSI files from an EXE installer

Problem:

You need to extract an .msi file from an .exe installer.

Solution:

There are at least three ways of solving this problem, but none of them is universal. You might need to go through all of them to find the one that works for the EXE installer that you have.

CodeTwo strongly advises against extracting (and using) MSI files from the EXE installers of the CodeTwo software. Unless the product website allows such an operation (or unless you are instructed/allowed to do so by CodeTwo Support), use the .exe setup files.

The first method is based on the fact that most installers extract their .msi files to the temporary files folder during the installation process. To extract an MSI file from an EXE installer, you need to:

1. Launch your .exe file.
2. When you see the first prompt (e.g. a question about whether you want to continue installation, accept a license agreement, etc.), do not click anything in this window and do not close it.
3. Open Windows Explorer, type %temp% in the address bar and press Enter.
4. Sort the files in the folder by the modification date. The newest file on the list should be the .msi file you are looking for.
5. Copy the MSI file to a safe location before you close the installer prompt window (see step 2). Be aware that if you close the installer window, the MSI file will be immediately deleted from the temporary files folder.

The second method uses a free third-party tool called 7-Zip to browse the content of the .exe installer file. Follow the steps below.

1. Download 7-Zip from this page and install it.
2. Right-click on the .exe file (from which you want to extract an .msi file) and from the shortcut menu choose 7-Zip >Open Archive.
3. Do not extract any files yet. Instead, browse and look for the folder MSI within the contents. It might take some time to find this folder because it is not always located directly in the root directory (its location may vary depending on the installer).
4. When you locate the MSI folder, you will notice that it most likely does not contain any .msi files, but a file or files with no extensions and rather cryptic names such as 132. Despite these misleading names, these are actually the MSI files you are looking for.
5. Drag and drop these files to any desired folder or select them and extract them with 7-Zip. Close 7-Zip after that.
6. Change the names of the extracted files so that they include the .msi extension.
7. If there are two files, the larger one is the 64-bit installer, and the smaller one is the 32-bit version. Use the one you need.

The third method works with InstallShield based projects. To get the MSI file from your EXE installer, you need to:

1. Log on to a computer where the software (the installer of which you would like to access) is not installed. This is because this method forces the uninstalling process to trigger extraction of the .msi file. If you already have this software installed, this method will remove it, which might not be desired.
2. Run Windows Command Prompt (cmd) (in Windows 10: open the Start menu, type cmd and press Enter) and go to the folder where your EXE file is located.
3. Execute the command below:

replace with the name of your .exe file and with the path to the folder where you want the .msi file to be extracted (for example C:\Folder ).

As described in this thread, the switches for the command above do the following:

• /s /x — silently ( /s ) uninstalls ( /x ) the product from the system;
• /b — defines the target path for the .msi file;
• /v — passes desired arguments to the installer. In this case, the argument is /qn — it disables GUI and any prompts.

Extract MSI from EXE

I want to extract the MSI of an EXE setup to publish over a network.

For example, using Universal Extractor, but it doesn’t work for Java Runtime Environment.

8 Answers 8

7-Zip should do the trick.

With it, you can extract all the files inside the EXE (thus, also an MSI file).

Although you can do it with 7-Zip, the better way is the administrative installation as pointed out by Stein Åsmul.

For InstallShield MSI based projects I have found the following to work:

This command will lead to an extracted MSI in a directory you can freely specify and a silently failed uninstall of the product.

The command line basically tells the setup.exe to attempt to uninstall the product (/x) and do so silently (/s). While doing that it should extract the MSI to a specific location (/b).

The /v command passes arguments to Windows Installer, in this case the /qn argument. The /qn argument disables any GUI output of the installer.

Quick List: There are a number of common types of setup.exe files. Here are some of them in a «short-list». More fleshed-out details here (towards bottom).

Setup.exe Extract: (various flavors to try)

dark.exe is a WiX binary — install WiX to extract a WiX setup.exe (as of now). More (section 4).

There is always:

MSI Extract: msiexec.exe / File.msi extraction:

Many Setup Tools: It is impossible to cover all the different kinds of possible setup.exe files. They might feature all kinds of different command line switches. There are so many possible tools that can be used. ( non-MSI , MSI , admin-tools , multi-platform , etc. ).

NSIS / Inno: Commmon, free tools such as Inno Setup seem to make extraction hard (unofficial unpacker, not tried by me, run by virustotal.com). Whereas NSIS seems to use regular archives that standard archive software (7-zip et al) can open and extract.

General Tricks: One trick is to launch the setup.exe and look in the 1) system’s temp folder for extracted files . Another trick is to use 2) 7-Zip, WinRAR, WinZip or similar archive tools to see if they can read the format. Some claim success by 3) opening the setup.exe in Visual Studio . Not a technique I use. 4) And there is obviously application repackaging — capturing the changes done to a computer after a setup has run and clean it up — requires a special tool (most of the free ones come and go, Advanced Installer Architect and AdminStudio are big players).

UPDATE: A quick presentation of various deployment tools used to create installers: How to create windows installer (comprehensive links).

And a simpler list view of the most used development tools as of now (2018), for quicker reading and overview.

And for safekeeping:

Just a disclaimer: A setup.exe file can contain an embedded MSI, it can be a legacy style (non-MSI) installer or it can be just a regular executable with no means of extraction whatsoever. The «discussion» below first presents the use of admin images for MSI files and how to extract MSI files from setup.exe files. Then it provides some links to handle other types of setup.exe files. Also see the comments section.

UPDATE: a few sections have now been added directly below, before the description of MSI file extract using administrative installation. Most significantly a blurb about extracting WiX setup.exe bundles (new kid on the block). Remember that a «last resort» to find extracted setup files, is to launch the installer and then look for extracted files in the temp folder (Hold down Windows Key , tap R , type %temp% or %tmp% and hit Enter ) — try the other options first though — for reliability reasons.

Apologies for the «generalized mess» with all this heavy inter-linking. I do believe that you will find what you need if you dig enough in the links, but the content should really be cleaned up and organized better.

General links:

Extract content:

Vendor links:

WiX Toolkit & Burn Bundles (setup.exe files)

Tech Note: The WiX toolkit now delivers setup.exe files built with the bootstrapper tool Burn that you need the toolkit’s own dark.exe decompiler to extract. Burn is used to build setup.exe files that can install several embedded MSI or executables in a specified sequence. Here is a sample extraction command:

Before you can run such an extraction, some prerequisite steps are required:

1. Download and install the WiX toolkit (linking to a previous answer with some extra context information on WiX — as well as the download link).
2. After installing WiX, just open a command prompt , CD to the folder where the setup.exe resides. Then specify the above command and press Enter
3. The output folder will contain a couple of sub-folders containing both extracted MSI and EXE files and manifests and resource file for the Burn GUI (if any existed in the setup.exe file in the first place of course).
4. You can now, in turn, extract the contents of the extracted MSI files (or EXE files). For an MSI that would mean running an admin install — as described below.

There is built-in MSI support for file extraction (admin install)

MSI or Windows Installer has built-in support for this — the extraction of files from an MSI file. This is called an administrative installation. It is basically intended as a way to create a network installation point from which the install can be run on many target computers. This ensures that the source files are always available for any repair operations.

Note that running an admin install versus using a zip tool to extract the files is very different! The latter will not adjust the media layout of the media table so that the package is set to use external source files — which is the correct way. Always prefer to run the actual admin install over any hacky zip extractions. As to compression, there are actually three different compression algorithms used for the cab files inside the MSI file format: MSZip, LZX, and Storing (uncompressed). All of these are handled correctly by doing an admin install.

Important: Windows Installer caches installed MSI files on the system for repair, modify and uninstall scenarios. Starting with Windows 7 (MSI version 5) the MSI files are now cached full size to avoid breaking the file signature that prevents the UAC prompt on setup launch (a known Vista problem). This may cause a tremendous increase in disk space consumption (several gigabytes for some systems). To prevent caching a huge MSI file, you should run an admin-install of the package before installing. This is how a company with proper deployment in a managed network would do things, and it will strip out the cab files and make a network install point with a small MSI file and files besides it.

Admin-installs have many uses

It is recommended to read more about admin-installs since it is a useful concept, and I have written a post on stackoverflow: What is the purpose of administrative installation initiated using msiexec /a?.

In essence the admin install is important for:

• Extracting and inspecting the installer files
  • To get an idea of what is actually being installed and where
  • To ensure that the files look trustworthy and secure (no viruses — malware and viruses can still hide inside the MSI file though)
• Deployment via systems management software (for example SCCM)
• Corporate application repackaging
• Repair, modify and self-repair operations
• Patching & upgrades
• MSI advertisement (among other details this involves the «run from source» feature where you can run directly from a network share and you only install shortcuts and registry data)
• A number of other smaller details

Please read the stackoverflow post linked above for more details. It is quite an important concept for system administrators, application packagers, setup developers, release managers, and even the average user to see what they are installing etc.

Admin-install, practical how-to

You can perform an admin-install in a few different ways depending on how the installer is delivered. Essentially it is either delivered as an MSI file or wrapped in an setup.exe file.

Run these commands from an elevated command prompt, and follow the instructions in the GUI for the interactive command lines:

MSI files:

that’s to run with GUI, you can do it silently too:

setup.exe files:

A setup.exe file can also be a legacy style setup (non-MSI) or the dreaded Installscript MSI file type — a well known buggy Installshield project type with hybrid non-standards-compliant MSI format. It is essentially an MSI with a custom, more advanced GUI, but it is also full of bugs.

For legacy setup.exe files the /a will do nothing, but you can try the /extract_all:[path] switch as explained in this pdf. It is a good reference for silent installation and other things as well. Another resource is this list of Installshield setup.exe command line parameters.

MSI patch files (*.MSP) can be applied to an admin image to properly extract its files. 7Zip will also be able to extract the files, but they will not be properly formatted.