Fix it now
These are two halves of one sentence. 1619 is ERROR_INSTALL_PACKAGE_OPEN_FAILED – verify that the package exists and is accessible. 1620 is ERROR_INSTALL_PACKAGE_INVALID – the file opened and is not a valid installer package. Neither is a fault in the application you are installing, and neither is fixed by clearing caches or reinstalling runtimes.
Get-FileHash C:\pkg\app.msi -Algorithm SHA256
Unblock-File -Path C:\pkg\app.msi
msiexec /i "C:\pkg\app.msi" /l*v "C:\pkg\open.log"
- Copy the package to a short local path with no spaces – C:\pkg\app.msi will do – and install from there. That removes path length, mapped drives and share permissions in one move.
- Compare the hash and the file size against what the vendor publishes. A file much smaller than expected is the classic 1620.
- If the file is suspiciously small, open it in a text editor. A saved proxy error page or a login redirect stored with an .msi name is extremely common and produces 1620 every time.
- Re-download over a different route – a different network, or straight from the vendor rather than a mirror – and delete any partial file first rather than resuming.
1619 from a deployment tool on a package that installs fine when you double-click it is almost always account context: part of the installation runs as the local system account, which usually has no rights to a file share and no mapped drives.
If the log shows the database opening and the sequence starting, you are past this error. If not, the next section explains what the engine is trying to open and which of the two failures you have.
Why it happens
An MSI is not an archive and not a script. It is a relational database held inside a structured storage file: tables describing directories, files, components, registry entries and the sequence of actions that installs them. Before anything can happen, Windows Installer has to open that storage and read its tables. Two distinct failures live in that single step, which is why there are two error numbers with almost identical wording.
1619 is the file-level failure, and Microsoft’s text asks you to verify that the package exists and is accessible. That covers a mistyped path, a file that has been moved or quarantined, a path longer than the classic limit, and the case that catches deployment engineers most often – a package on a share that the installing account cannot read. Remember that part of the installation runs as the local system account, which on most networks has no rights to a file share at all and no mapped drive letters.
1620 is the database-level failure: the file opened and turned out not to be a usable installer package. That is what a truncated download looks like, what a package edited carelessly in a table editor looks like, and what an HTML error page saved with the wrong extension looks like. The internal errors that accompany it are more specific. 2245 is “IStorage::Stat failed”, which is the structured storage layer itself refusing. 2705 is “Invalid table: [2]; Could not be linked as tree”, meaning a table exists but cannot be resolved into the directory structure the engine needs. And 0x80070654 is simply 1620 wrapped in an HRESULT by a setup bootstrapper.
The account running the install cannot reach the path
You have this one if The package installs when you double-click it and fails with 1619 from a deployment tool, a scheduled task or a startup script.
- Copy the package to a local folder as part of the deployment, and install from the local copy.
- Where it must run from a share, grant read access to the computer accounts – Domain Computers – rather than only to users.
- Never use mapped drive letters in scripts; they exist only in the interactive user’s session. Use the full UNC path or a local copy.
- Re-run with
/l*vand confirm the log records the package being opened.
The download is incomplete, or is not a package at all
You have this one if 1620, and the file is much smaller than expected or opens as readable text.
- Check the size against the vendor’s published figure and compare the hash with
Get-FileHash. - Open the first few bytes in a text editor. Readable text such as an HTML tag means you have downloaded an error page.
- Re-download without a proxy or content filter in the path; interception is a frequent cause of truncated or substituted files.
- Delete any partial file before starting again rather than letting a download tool resume it.
The file is blocked or has been quarantined
You have this one if The package is the right size and the install fails immediately, with a security product logging an event at the same moment.
- Remove the mark of the web:
Unblock-File -Path C:\pkg\app.msi, or Properties then Unblock on the General tab. - Check the endpoint product’s quarantine and restore the file if it was taken.
- Add an exclusion for the staging folder your deployment uses, in the management policy rather than on the machine.
- Confirm the file still exists immediately before the install runs; some agents delete rather than block.
The package has been edited or repackaged badly
You have this one if 1620 with an internal table error in the log, on a package customised in-house or produced by a repackaging tool.
- Test the vendor’s original, unmodified package. If that installs, your customisation is at fault.
- Rebuild the customisation as a transform applied at install time rather than by editing tables inside the MSI.
- Where you must edit the database, use a proper MSI editing tool and run the package through its validation checks before deployment.
- Keep the vendor original archived so you always have a known-good baseline to compare against.
The path is too long, or carries characters the parser rejects
You have this one if 1619 on a deeply nested folder, a very long file name, or a path full of unusual characters after an automated download.
- Move the package to a short path such as C:\pkg and rename it to something plain.
- Avoid quotation marks, semicolons and non-ASCII characters in the name you pass on the command line.
- Where a script builds the command, echo the fully expanded path before the install runs and read it.
Full reference
The codes, as Microsoft states them
| Code | Constant or type | Message |
|---|---|---|
| 1619 | ERROR_INSTALL_PACKAGE_OPEN_FAILED | This installation package couldn’t be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package |
| 1620 | ERROR_INSTALL_PACKAGE_INVALID | This installation package couldn’t be opened. Contact the application vendor to verify that this is a valid Windows Installer package |
0x80070654 |
HRESULT form of 1620 | Facility 0x8007 with 0x654, which is 1620 |
| 2245 | Internal message | IStorage::Stat failed with error [3] |
| 2705 | Internal message | Invalid table: [2]; Could not be linked as tree |
| 2715 | Internal message | The specified File key (‘[2]’) not found in the File Table |
The wording difference between 1619 and 1620 is the whole diagnosis. 1619 asks you to verify the package exists and is accessible – a file and access problem. 1620 does not, because the engine already found and opened it; it asks you to verify the package is valid. Read which of the two you actually have before you decide whether to fix a path or re-download a file.
Proving a package is what it claims to be
Get-FileHash C:\pkg\app.msi -Algorithm SHA256and compare against the vendor’s published value.- Compare the byte size against the download page. Truncation is far more common than corruption in place.
- Open the file in a text editor and look at the first line. A valid installer database is binary; readable markup means you have an error page with the wrong extension.
- Check the digital signature on the Digital Signatures tab of the file’s properties. A package that will not verify is one you should not deploy regardless of this error.
- Try it on a second machine. A package that fails identically everywhere is a bad file; one that fails on a single machine is an access or environment problem.
Deployment context, which is where 1619 usually lives
| Interactive install | Deployment tool |
|---|---|
| Runs as you, with your profile | Runs as the local system account or a service account |
| Mapped drive letters exist | Mapped drives do not exist at all |
| Share access uses your rights | Share access uses the computer account, which usually has none |
| Your environment variables resolve | A different, smaller environment resolves |
| Long paths may work through your profile | The expanded path can differ entirely |
That table explains almost every “it works when I double-click it” report. Stage the package to a local folder as the first step of the deployment, reference it by absolute local path, and the difference disappears – along with the argument about whether the package is faulty.
Repairing a damaged package
Practically, you cannot. The database is a structured storage file with internal streams and cross-references, and a truncated one has lost data that cannot be reconstructed. Editing tools will sometimes open a damaged package far enough to look promising, which wastes more time than it saves. Get a clean copy from the vendor you bought it from – that is a support request rather than a new purchase.
Related failures that are not this one
- 1613, ERROR_INSTALL_PACKAGE_VERSION, means the package cannot be installed by the installer service on this machine and needs a newer Windows Installer version – a different problem from an invalid package.
- 1635 and 1636 are the patch equivalents of 1619 and 1620: a patch package that could not be opened, and one that opened and is not valid.
- 1632, ERROR_INSTALL_TEMP_UNWRITABLE, means the Temp folder is full or inaccessible. It is easy to mistake for a package problem because it also fails before anything visible happens.
- 1633 means the package is not supported on this platform, which is an architecture or language mismatch rather than a damaged file.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1619 |
ERROR_INSTALL_PACKAGE_OPEN_FAILED: the package could not be opened; verify that it exists and is accessible | Microsoft Learn |
1620 |
ERROR_INSTALL_PACKAGE_INVALID: the file opened but is not a valid Windows Installer package | Microsoft Learn |
0x80070654 |
The same invalid-package result in HRESULT form: facility 0x8007 with 0x654, which is 1620 | Microsoft Learn |
2715 |
The specified File key not found in the File table – an action referenced a file key the package does not contain, which is a packaging fault for the vendor rather than a machine fault | Microsoft Learn |
2245 |
IStorage::Stat failed: the structured storage layer underneath the package could not be read | Microsoft Learn |
2705 |
Invalid table; could not be linked as tree – a table in the package cannot be resolved into the directory structure the engine needs | Microsoft Learn |
Confirm the fix worked
- The log written by
/l*vrecords the database opening and the action sequence starting. - The file hash matches the vendor’s published value.
- The same install runs through your deployment tool, not only interactively, so you know the account context works.
- The product appears in Settings under Apps, Installed apps afterwards.
- A second machine installs the same staged copy, which confirms the package rather than one machine’s path.
Questions people ask about this
Does this cost anything to fix?
No. This is a file, path or download problem. Nothing here is a licensing state, and re-obtaining the package from a vendor you have already bought from is not a new purchase.
Why does it work when I double-click it but fail from my deployment tool?
Different account, different session, no mapped drives and no user profile. Deployment runs as the local system account, which typically has no rights to a share. Copy the package locally first and the difference goes away.
Can I repair a corrupt MSI?
Practically, no. The database is a structured storage file with internal references and streams, and a truncated one has lost data that cannot be reconstructed. Get a clean copy.
Is 0x80070654 the same as 1620?
Yes. It is 1620 carried inside an HRESULT, which is what you see when a setup wrapper reports the failure rather than msiexec itself. Treat them identically.
The log mentions an internal error in the 2xxx range. Is that my machine?
Almost certainly not. Internal errors in that range describe the package’s own tables and streams – a missing file key, an unreadable storage, a table that cannot be linked. They belong to whoever built the package, and the useful action is to send them the log.
