Many vendors ship their software as a single EXE installer, but the underlying payload is often a standard MSI wrapped inside that EXE. Extracting that MSI gives you a clean, deployable package with a known ProductCode — something Group Policy, SCCM, and Intune can detect and uninstall reliably.
This guide covers three proven ways to extract an MSI from an EXE installer. Each method takes a different tradeoff between speed and reliability.
Method 1: Open the EXE with 7-Zip
The fastest first attempt. Many EXE installers — especially those built with Inno Setup, NSIS, or InstallShield — are actually self-extracting archives. 7-Zip can open them like any other archive and show the bundled files inside.
How to do it: Right-click the EXE, choose 7-Zip > Open archive. Look for an MSI file in the root or in a $PLUGINSDIR or MSI subfolder. If you see one, drag it out and you are done.
When it works: Inno Setup and NSIS installers often expose the MSI directly. Some InstallShield setups also bundle the MSI unencrypted.
When it fails: Custom bootstrapper EXEs that download the MSI at runtime, or EXEs that encrypt the payload, will show garbage or no MSI at all.
Method 2: Use the built-in /extract switch
Some installer frameworks ship with a hidden or documented switch that extracts the bundled files to a folder without actually running the install.
Common switches by framework:
- InstallShield:
setup.exe /a /s /v"/qn TARGETDIR=C:\Extract"— performs an administrative install that dumps the MSI and support files to a target directory. - Some vendor wrappers:
installer.exe /extract:[path]— extracts the payload without executing it. - Self-extracting archives: Try
/extract:"C:\Extract"or/extractalldepending on the tool that built the EXE.
How to find the right switch: Run installer.exe /? or installer.exe /help from a command prompt. Many installers print a usage screen with supported switches. Vendor admin guides and deployment KBs also document these.
Pro tip: Always extract to an empty folder. The extracted contents often include multiple MSIs, transforms (.MST), and prerequisite installers — not just a single MSI.
Method 3: Monitor the %TEMP% folder during execution
When an EXE installer runs, almost every framework unpacks its payload to a temporary folder before the actual install begins. That folder usually lives under %TEMP% and often contains the MSI in plaintext.
How to do it:
- Open
%TEMP%in Windows Explorer (paste it into the address bar). - Sort by Date modified so new folders appear at the top.
- Run the EXE installer.
- Watch for a new folder with a random name like
{XXXXXXXX}or a vendor-specific prefix. - Open that folder. Look for
*.msifiles. Copy them out immediately — the installer deletes the temp folder on exit.
When to use this: This is the most reliable universal method. It works on InstallShield, Inno Setup, NSIS, and many custom frameworks, because every installer needs to unpack somewhere before it can execute.
The catch: Some installers clean up the temp folder even on failure, and some run the install so quickly you may miss the window. Running the EXE on a slower machine or VM gives you more time to grab the files.
What to do once you have the MSI
Extracting the MSI is only the beginning. You still need the silent install switch, the correct ProductCode for detection, and the uninstall command. If the vendor EXE was a bootstrapper, the extracted MSI may also need transforms (.MST) or prerequisite MSIs that were bundled alongside it.
That is where an automated workflow saves the most time. InstallMage fingerprints the installer framework, extracts the silent arguments, and produces a deployable MSI or .intunewin with detection rules pre-filled. You skip the manual archaeology entirely.
Read our silent install switches guide for the full cheat sheet by framework, or our Intune detection rules guide to make sure your extracted MSI is actually detectable in production.
Bottom line
Start with 7-Zip for a 30-second check. If that fails, try the installer's documented extraction switch. If all else fails, the %TEMP% monitoring method works on almost everything because every installer has to unpack somewhere.
Need to skip the extraction dance entirely? The free tier converts vendor EXEs to deployable MSIs automatically — including silent switches, detection rules, and Intune-ready metadata. Try it on your next deployment.