Use Windows Installer by matching the action to the file: double-click an .msi to install, use the file’s context menu or an elevated terminal when Windows needs extra rights, and use msiexec for silent installs, repairs, uninstalls, or logging. Wrong methods can leave half-installed apps, failed updates, or broken uninstall entries. This guide shows the modern Windows path first, then the legacy context for older Server 2003-era labels, and it explains how to repair, remove, or troubleshoot .msi packages safely.

Windows Installer basics

A Windows Installer package is a Windows software package stored in an .msi file. It carries the instructions Windows uses to install, repair, and uninstall an application. It is not the same as a generic EXE installer, and the path you use can change both the options you see and the permissions Windows requires.

On modern Windows, start with Settings, installed apps, File Explorer, or an elevated terminal. On Windows Server 2003-family systems, Microsoft’s older documentation uses Add or Remove Programs and Windows Explorer labels. The underlying installer engine is the same idea, but the UI names and the exact menus differ by version.

What you'll need

  • A Windows device with access to the .msi file
  • Administrator rights, if the package requires them
  • A local copy of the installer or a trusted download location
  • Access to Settings, File Explorer, or an elevated terminal
  • A file view that shows the full filename extension

📊 Microsoft’s older page applies to Windows Server 2003, including R2 and SP1/SP2. Source: Microsoft.

How do you open a Windows Installer package (.msi)?

On modern Windows, open the .msi from File Explorer after confirming the extension ends in .msi. Double-clicking usually starts the package. If Windows needs more rights, it will prompt you. If the file is blocked, the path or trust state can stop it before the installer starts.

  1. Open File Explorer and find the installer.
  2. Confirm the filename ends in .msi, not .exe.
  3. Double-click the file to start the package.
  4. Right-click the file if you need Install, Repair, or Uninstall.
  5. If Windows shows a blocked file message, clear the block in Properties or move the file from a trusted location.

Say your download is PrinterDriver.msi and the only issue is that it came from email. Check the file name first. If the right-click menu shows Install but the app fails immediately, the next thing to check is whether your account can install software without elevation.

How do you use Windows installer from file Explorer?

Use File Explorer when you already have the .msi file and want the package options attached to that file. Microsoft documents the Explorer path as opening Windows Explorer, then using the context menu on the MSI file. That menu can expose Install, Repair, and Uninstall for the package.

  1. Open Windows Explorer or File Explorer.
  2. Go to the folder that contains the .msi package.
  3. Right-click the file to open the context menu.
  4. Select Install, Repair, or Uninstall as needed.
  5. If the option does not appear, try another account or use the command line.

Suppose the package installs from one user account but not another. That usually points to permissions, not file type. A standard account may be able to start the package, while an administrator account can complete a machine-wide install or repair.

How do you use Windows installer from Settings or Control Panel?

On current Windows, use Settings > Apps or installed apps to manage software that is already installed. On the older Windows Server 2003 family, Microsoft documented Add or Remove Programs in Control Panel for the same general job: change or remove installed software entries.

  1. On modern Windows, open Settings and then Apps or Installed apps.
  2. Find the installed program in the list.
  3. Choose the app’s modify, repair, or uninstall option if it is available.
  4. On Windows Server 2003-family systems, open Control Panel.
  5. Select Add or Remove Programs, then choose Change or Remove.

If the program entry is missing, the installer may not have registered correctly, or the package may have been removed outside the normal path. In that case, use the original .msi or run msiexec with the package path from an elevated terminal.

How do you use Windows Installer from the command line?

How do you use Windows Installer from the command line?
A screenshot shows Windows Installer command-line options and switches

Use the command line when you need a controlled install, a repair switch, a fix for a broken GUI path, or a log for troubleshooting. Microsoft documents msiexec as the installer command-line tool for Windows Installer packages. It is the best option for scripted installs and silent deployment.

  1. Open Command Prompt or Windows Terminal as administrator.
  2. Type a command that points to the MSI file path.
  3. Use the install syntax for a fresh install.
  4. Use a repair switch when the app is damaged or partial.
  5. Use uninstall syntax when Control Panel fails to remove the app.

A common first-timer mistake is to open a normal terminal and expect the same result. If the package needs elevated rights, the command may start and then stop with a permission failure. Reopen the terminal with administrator rights before trying again.

What are the exact msiexec commands you can copy?

These examples use msiexec because that is the installer engine Microsoft documents for MSI packages. Replace the sample file path and product code with your own. If a command fails, the most common causes are missing elevation, a bad path, policy restrictions, or an unavailable source file.

  1. Install: msiexec /i "C:\Installers\App.msi" — starts a normal installation from a local path. If it fails, confirm the file exists and the path is quoted correctly.
  2. Quiet install: msiexec /i "C:\Installers\App.msi" /qn — installs with no user interface. If it fails silently, add logging so you can see the return code.
  3. Repair: msiexec /f "C:\Installers\App.msi" — repairs missing or damaged components. If the source is unavailable, Windows may prompt for the original package.
  4. Uninstall by product code: msiexec /x {PRODUCT-CODE-GUID} — removes an installed MSI product. If the product entry is missing, the GUID may be wrong or the app may already be gone.
  5. Elevated use: run the same commands from Windows Terminal started as administrator — the command itself does not add elevation, so the terminal must already be elevated. If policy blocks it, you may still get an access-denied result.
  6. Logging: msiexec /i "C:\Installers\App.msi" /L*V "C:\Temp\App-install.log" — writes a verbose install log. If the folder does not exist or is not writable, the log file will not be created.
  7. USB path: msiexec /i "E:\Setup\App.msi" — installs from removable media if the drive letter is correct. If the USB drive changes letters or disconnects, the source becomes unavailable.
  8. Network path: msiexec /i "\\Server\Share\App.msi" — installs from a shared folder. If the share is blocked by permissions or the network is unavailable, Windows cannot read the package source.

MSI decision table

MSI decision table
Diagram showing MSI Installer with labeled callouts around it

This table maps the task to the right route, the privilege level to expect, and the first fallback when it fails.

Goal Best method Admin needed? Where to click/type What usually goes wrong What to do if it fails
Install an app from an .msi file File Explorer Sometimes Right-click the .msi, then choose Install Missing elevation, blocked file, or a bad file path Open an elevated terminal and run msiexec
Repair a broken MSI app File Explorer or Settings Often Right-click the .msi and choose Repair, or open installed apps and select the app’s repair option if present Source file unavailable or the product entry is damaged Run a repair command with msiexec
Uninstall an MSI app Settings or Control Panel Sometimes Open installed apps or Add or Remove Programs, then choose Remove or Uninstall Missing product entry or policy blocks removal Use msiexec uninstall syntax from an elevated terminal
Fix a package that will not launch normally Command line Yes, for most machine-wide installs Open an elevated terminal and run msiexec with the MSI path Windows Installer service disabled, trust issue, or access denied Check the Windows Installer service and file trust settings
Install from removable media or a share Command line or File Explorer Sometimes Use a USB path like E:\Setup\App.msi or a network path like \\Server\Share\App.msi Source file unavailable after drive changes or network loss Copy the MSI to a local folder and retry
Investigate a silent failure Command line with logging Yes, often Use msiexec with /L*V to write a log file No visible UI means the failure is easy to miss Review the log and rerun with elevation if needed

What’s the difference between install, repair, and uninstall in Windows installer?

Install adds the app and its registered components. Repair checks the existing install and restores missing or damaged pieces. Uninstall removes the program and its registered entry. Use the action that matches the state of the app, not the state you wish it were in.

If you click the wrong action, Windows may still complete it, but the result can be confusing. Repair can leave the app present but fixed. Uninstall removes the program files and registration. Install creates a new entry or starts the setup process from the package.

Common mistakes

Common mistakes
A Windows error dialog about a Windows Installer package appears on screen

These are the failures that most often send people in the wrong direction. Fixing the route usually matters more than trying the same click twice.

  1. Opening the wrong file type: confirm the file ends in .msi before you start. An .exe installer follows a different path.
  2. Skipping elevation: if the package needs administrator rights, reopen File Explorer or the terminal with elevated permissions.
  3. Using the wrong action: use Change or repair for modify or repair, Remove for uninstall, and Install only for new setup.
  4. Ignoring service problems: if MSI actions fail across multiple packages, the Windows Installer service may be the issue.

Consider a package that opens but never finishes, then leaves an entry behind in installed apps or Control Panel. That pattern usually calls for a repair or uninstall from an elevated terminal, not another double-click. If the installer is blocked by policy or file trust, moving it to a trusted local folder can help isolate the problem.

If that didn't work, try this next

  1. Run the package from an elevated terminal with msiexec.
  2. Open services.msc and verify the Windows Installer service is available to the account you are using.
  3. Return to installed apps or Add or Remove Programs and use Change or Remove if the entry still exists.
  4. If the package came from a blocked source, move it to a local folder and try again.

Prevention: keep the original .msi in a local folder with its full filename visible. That makes it easier to confirm the package type and rerun repair or uninstall later.

Keep reading

Frequently asked questions

How do I run an MSI installer as administrator?

Open Windows Terminal as administrator and run msiexec with the full file path. There is not a generic “install as administrator” command built into the file itself, so the elevation comes from the terminal session. If the installer still fails, the package may be restricted by policy or source path.

How do I use Windows installer packages with Settings or Add or remove Programs?

On modern Windows, open Settings > Apps or installed apps, then pick the program entry. On Windows Server 2003-family systems, open Control Panel > Add or Remove Programs. Use the app’s available change, repair, or remove option if it appears.

How do I run Windows Installer from the command line?

Open an elevated terminal and run msiexec with the MSI path. That path is the right choice for scripted installs, repair switches, logging, and uninstall commands. If the command fails at once, rerun it in a window started with administrator rights.

How do I repair or uninstall an MSI package?

Start with the package’s right-click menu in Explorer, then try Repair or Uninstall. If that does not work, open installed apps or Add or Remove Programs and use the app’s removal option. The last step is an elevated msiexec command.

How to use windows installation media

Windows installation media is separate from an MSI package. Use installation media only when you need to install or repair Windows itself, or when setup files for the operating system are involved. For app installers that come as .msi, Windows Installer is the right tool, whether you launch it from File Explorer, Settings, or msiexec.