Skip to main content

How to Extract an MSI Package in Batch Script

Sometimes you don't want to actually "Install" a program; you just need to peek inside its files. For example, you might need a specific driver .sys file, an icon, or a documentation .pdf that is trapped inside an MSI installer. Or, you might be preparing a "Portable" version of an app that doesn't need to touch the Windows Registry. A Batch script can use the Administrative Installation feature of the msiexec engine to "Unpack" the contents of an MSI into a regular folder.

This allows you to harvest individual files without ever triggering a full system installation.

This guide will explain how to extract MSI contents via the command line.

Method: Administrative Extraction (Msiexec)​

The /a switch (Administrative Install) is the standard way to unpack an MSI into a target directory.

@echo off
set "Installer=C:\Deploy\App.msi"
set "ExtractDir=C:\Temp\ExtractedFiles"
set "LogFile=C:\Logs\msi_extract.log"

:: Verify the MSI file exists
if not exist "%Installer%" (
    echo [ERROR] MSI file not found: %Installer%
    pause
    exit /b 1
)

echo [ACTION] Extracting contents to %ExtractDir%...

:: Ensure the target and log directories exist
if not exist "%ExtractDir%" mkdir "%ExtractDir%"
if not exist "C:\Logs" mkdir "C:\Logs"

:: /a = Administrative Installation (Extraction)
:: TARGETDIR = Define where the files should go
:: /qn = No UI during the process
:: /L*V = Verbose logging
start /wait "" msiexec /a "%Installer%" /qn TARGETDIR="%ExtractDir%" /L*V "%LogFile%"

if %errorlevel% equ 0 (
    echo [SUCCESS] Extraction complete. Explore the files in:
    echo          %ExtractDir%
) else (
    echo [ERROR] Extraction failed with exit code: %errorlevel%
    echo         Check the log file: %LogFile%
)

pause

Method 2: Extracting to a Relative Path​

Use this script if you keep your MSI in a "Tools" folder and want to unpack it right next to the installer.

@echo off
set "MSIFile=%~dp0setup.msi"
set "OutputDir=%~dp0unpacked_output"

:: Verify the MSI file exists
if not exist "%MSIFile%" (
    echo [ERROR] MSI file not found: %MSIFile%
    pause
    exit /b 1
)

echo [SETUP] Unpacking installer to: %OutputDir%...

:: Ensure the output directory exists
if not exist "%OutputDir%" mkdir "%OutputDir%"

:: %~dp0 provides the path to the current script's directory
start /wait "" msiexec /a "%MSIFile%" /qn TARGETDIR="%OutputDir%"

if %errorlevel% equ 0 (
    echo [SUCCESS] Files are now in: %OutputDir%
) else (
    echo [ERROR] Extraction failed with exit code: %errorlevel%
)

pause

Method 3: Harvesting a Specific File Version​

If you are an auditor and want to check the version of a .dll inside an MSI without modifying your system.

@echo off
set "MSI=C:\Deploy\SecurityScan.msi"
set "TargetFile=Engine.dll"
set "TmpDir=%TEMP%\MSI_Audit_%RANDOM%"

:: Verify the MSI file exists
if not exist "%MSI%" (
    echo [ERROR] MSI file not found: %MSI%
    pause
    exit /b 1
)

echo [ACTION] Extracting MSI for file version audit...

:: Extract to a unique temporary directory
mkdir "%TmpDir%"
start /wait "" msiexec /a "%MSI%" /qn TARGETDIR="%TmpDir%"

if %errorlevel% neq 0 (
    echo [ERROR] Extraction failed with exit code: %errorlevel%
    rmdir /s /q "%TmpDir%" 2>nul
    pause
    exit /b 1
)

:: Search for the target file within the extracted contents
echo [AUDIT] Searching for %TargetFile%...

set "FoundFile="
for /r "%TmpDir%" %%f in ("%TargetFile%") do (
    if exist "%%f" set "FoundFile=%%f"
)

if defined FoundFile (
    echo [FOUND] %FoundFile%
    powershell -NoProfile -Command ^
        "$v = (Get-Item '%FoundFile%').VersionInfo;" ^
        "Write-Host 'File Version:' $v.FileVersion;" ^
        "Write-Host 'Product Version:' $v.ProductVersion"
) else (
    echo [WARNING] %TargetFile% was not found in the extracted contents.
)

:: Cleanup the temporary extraction
echo [CLEANUP] Removing temporary files...
rmdir /s /q "%TmpDir%" 2>nul

echo [DONE] Audit finished.
pause

How to Avoid Common Errors​

Wrong Way: Thinking this is the same as "Unzipping"​

You cannot open an MSI with standard Windows "Compressed Folders" (Zip tool). While tools like 7-Zip can sometimes peek inside, the MSI format is a complex database of instructions, not just a simple archive.

Correct Way: Use the native msiexec /a command (Method 1). This is the "Official" way to handle MSI files, ensuring that all sub-folders and file names are preserved exactly as the developer intended.

Problem: "Administrative" Installation Prompt​

Even though you aren't "Installing" the software to your program list, the /a switch is technically an "Administrative" task because it prepares a deployment image.

Solution: You must run the Batch script as an Administrator, or the extraction might fail when it tries to write files to the disk.

Best Practices and Rules​

1. Identify "TARGETDIR"​

You must always explicitly provide the TARGETDIR property. If you don't, Windows might try to extract the files into the root of your C:\ drive or another inconvenient location.

2. File Metadata​

When you extract using /a, the files often lose their "Compressed" state. However, they keep their original creation and modification dates, which is vital for forensic auditing.

3. Cleanup​

Administrative installs can be large, as they include the full, uncompressed payloads. Always remember to delete your extraction directory once you have harvested the specific files you need (as shown in Method 3).

Conclusions​

Extracting an MSI package via Batch script provides a powerful way to interact with software installers on your own terms. By moving from "Blind" installations to targeted file harvesting, you gain the ability to manage drivers, audit binary versions, and create portable tools with total precision. This professional level of file management is essential for developers, sysadmins, and security researchers who need to verify and manage software components without cluttering their Windows environment.

Table of Contents