Skip to content

How to inspect an MSI without installing it

An .msi is a database, not a program. Here's what's inside one and how to read it safely — in your browser, with nothing uploaded or executed.

Published on 2 min read

You've been handed an .msi — from a download, an email, a software-deployment share — and you need to know what it does before it touches a machine. The good news: you don't have to run it. A Windows Installer package is not an executable. It is a relational database of instructions, wrapped in an OLE2 compound file, and every one of those instructions can be read as plain data.

What's actually inside

Open an MSI and you'll find:

  • A Summary Information stream — the product, manufacturer, platform, language, package code and whether the payload is compressed. This is your orientation.
  • A database of tables: Property (product code, version, manufacturer), Directory, Component, Feature, File, Registry, Shortcut, ServiceInstall and — the one that matters most — CustomAction.
  • Optional cabinets carrying the payload files.
  • An optional digital signature.

Read it, don't run it

Static triage answers the questions that matter: What product claims to be this? Who signed it? What files does it drop? Does it run any code, and as whom? All of that is in the data. Nothing needs to execute.

MSI Parser does exactly this, client-side: drop a package (or a folder, or a ZIP of packages) and it decodes the container and the database in a Web Worker using a Rust parser compiled to WebAssembly. Nothing is uploaded, and nothing in the package is executed or installed. The next post looks at the single most important thing to check: the custom actions.

Related articles

A practical, static checklist for deciding whether a Windows Installer package is worth trusting — signature, custom actions, payload and reach.
The CustomAction Type field is a bit-field. Decode it and you know whether an installer runs an EXE, loads a DLL, executes a script — and whether it does so as SYSTEM.