Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Apps, installers & Microsoft Store · scoped error record
Error 1603

Windows Installer fatal installation error

1603 is a fatal MSI installation failure, but Microsoft documents multiple possible conditions; preserve package/context before applying a fix.

Applies to: Windows Installer (MSI)Reviewed: 2026-09-17

What it means in this context

Microsoft documents Windows Installer Error 1603 as a fatal installation failure and lists multiple possible conditions, including an app already being installed, encrypted target folder, substituted drive, or SYSTEM lacking Full Control on the target folder. The code is therefore a failure class, not a single-cause diagnosis.

Diagnostic state

What is known, and what is not proven yet

Keep observation, evidence and conclusion separate before making a higher-impact change.

Observed fact

An MSI transaction ended with Error 1603.

Windows evidence

Package/version, target path/state and optional verbose MSI log.

Likely subsystem

Windows Installer/package custom action; 1603 alone does not identify which.

Evidence still needed

Which documented condition or log action immediately precedes rollback.

Safe next action

Verify documented conditions, then collect one verbose log.

Handoff boundary

Publisher/IT for package custom-action or product-specific failure.

Start here
  1. Confirm the package is MSI-based and came from the trusted publisher.
  2. Check whether the product is already installed.
  3. Preserve the exact install path and whether it is encrypted/substituted.
  4. Create a verbose MSI log when the simple conditions do not identify the cause.
1

Check Microsoft’s documented 1603 conditions first

Low risk

Why: The dedicated Microsoft article identifies concrete 1603 conditions that can be verified before broader repair.

  1. Check Installed apps/Programs and Features for an existing installation.
  2. Avoid installing to an encrypted or substituted-drive target.
  3. Verify the target folder permissions are appropriate for Windows Installer/SYSTEM.
  4. If none fit, collect the MSI verbose log and use vendor-specific setup guidance.
Scope boundary

When not to use this record

Do not assume every 1603 failure is a permissions problem or disable security software globally. Custom actions and vendor packaging can also produce 1603.

If it persists

Use the verbose MSI logging guide and provide the package/version, exact time and log to the publisher if the documented conditions do not fit.

Evidence

Reviewed source

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

GuideMSI installer failed in Windows 11: create one verbose Windows Installer log before guessing

Use the exact MSI code first; when the cause is still unclear, a controlled /L*V log can preserve the Windows Installer sequence for support.

GuideDesktop program will not install, update or uninstall in Windows 11

Separate a desktop installer problem from Microsoft Store/MSIX deployment, then use repair, uninstall and installer evidence in the least disruptive order.

ErrorError 1618 — Another Windows Installer installation is already in progress

1618 means Windows Installer reports another installation already running; finish or clear the legitimate pending operation before retrying.

ErrorError 1619 — Windows Installer package could not be opened

1619 means the MSI package could not be opened; verify the file exists, is accessible and is a valid publisher-supplied Windows Installer package.

ErrorError 1620 — Windows Installer package is invalid or cannot be opened as a valid package

1620 is a package-validity/opening error; verify the installer with the publisher instead of applying generic Windows repairs.

Commandmsiexec — install MSI with verbose log

Run one MSI installation attempt while writing a verbose Windows Installer log that can be correlated with the exact failure code and provided to the software publisher or IT.