Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
Apps, installers & Microsoft Store · scoped error record
Error 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.

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

What it means in this context

Microsoft defines Error 1620 (ERROR_INSTALL_PACKAGE_INVALID) as the installation package being unable to be opened and directs the user to contact the application vendor to verify it is a valid Windows Installer package.

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

Windows Installer returned 1620 for a package.

Windows evidence

Package provenance/version and reproducibility with a fresh official copy.

Likely subsystem

Installer package validity.

Evidence still needed

Publisher confirmation that the package is valid for this Windows/device context.

Safe next action

Use a fresh official package and stop bypass attempts.

Handoff boundary

Software publisher/package administrator.

Start here
  1. Verify the installer came from the official publisher.
  2. Download a fresh copy rather than reusing a partially downloaded/archive-extracted file.
  3. Confirm the vendor intended the file for your Windows/device architecture and deployment method.
  4. Avoid modifying the MSI to bypass validation.
1

Replace or validate the package with the publisher

Low risk

Why: 1620 points to package validity rather than a generic system-file problem.

  1. Discard uncertain/corrupt copies.
  2. Download the current official installer.
  3. Confirm checksum/signature when the publisher provides one.
  4. Contact the publisher if the official package continues to return 1620.
Scope boundary

When not to use this record

Do not disable signature/security controls or edit MSI internals to force an invalid package to install.

If it persists

Use a different scoped MSI record only if the package begins opening and returns a different code.

Evidence

Reviewed source