Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Executables & Installers›.msi
THE FILE FIELD GUIDE
.msi

Windows Installer

Executables & Installers

A package containing a Windows Installer database/resources. Opening can start installation, distinct from viewing a document.

What it is used for
Installing and repairing Windows applications
What the file contains
Executable code / installation package
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

Inspect the package

Opening can initiate installation.

  1. Identify official origin, product and supported OS.
  2. Inspect signature, version and required CAB files.
  3. Distinguish install, update and repair workflows.
Follow the installation workflow

Follow administrator deployment on managed PCs.

  1. Check upgrade instructions and data backup.
  2. Keep required companion files in their intended layout.
  3. Install as documented and verify version/launch.
Inspect installation logs

Use return codes and logs.

  1. Record error code and installation stage.
  2. Use the publisher’s documented logging workflow.
  3. Inspect companion files, privileges and restart requirements.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Missing-source failures may involve absent CAB/resources; verify the installed version matches the repair package.
  • Record the error and consult official msiexec logging guidance. Do not publish logs containing personal information.
  • Another installation active: inspect updates/restart requirements.
  • Downgrade rejected: inspect product support.
  • Installed but fails: distinguish installation and launch logs.
  • Wrong version repaired: compare product/version and repair media.

When another package format is needed

  1. Check the publisher’s supported builds/packages.

Renaming/extraction does not port the application.

External files can be required

Keep external cabinet/source files with their expected names/layout.

Example: preserve the documented layout when an MSI requires a companion CAB.

Source for these steps：Microsoft · Installation Package / Microsoft · msiexec

Remove through uninstall

Use app-management/official uninstall workflows instead of deleting installed or cached installer files.

Source for these steps：Microsoft · Installation Package / Microsoft · msiexec

Related-format differences

Related-format differences
Format / methodRoleWhat to verify
MSIInstallation databaseCompanion files
EXE setupSetup entryProduct workflow
CABInstallation assetsMatching package/layout

Handling and security

Installers modify the system. Avoid unknown attachments and verify publisher/OS warnings.

Questions and answers

Can I install MSI on Mac?

It is for Windows Installer; seek the publisher’s macOS distribution.

Why does the MSI alone fail?

Some packages need CAB/source files. Check the complete distribution.

Is opening MSI only viewing?

It can start installation; distinguish inspection from deployment.

Does extraction install the app?

Registration and dependencies are separate; use the supported installation workflow.

May I publish the log unchanged?

Review usernames, paths and settings and share only necessary diagnostic details.

Format facts: name, steward and MIME type
Formal name
Windows Installer package
Steward / specification
Microsoft
MIME type
application/octet-stream (generic binary)

Primary and official sources

  • Official documentationInstallation Package

    Documents the installation database and accompanying files.

    Microsoft · Link checked：
  • Platform documentationmsiexec

    Documents Windows Installer commands and logging.

    Microsoft · Link checked：