Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 1335

MSI 1335: The Cabinet File Required for This Installation Is Corrupt

10 min read Updated October 5, 2026 Installers, Runtimes & App Deployment

Fix it now

The compressed payload does not match what the package expects. Microsoft’s message for 1335 says the cabinet is corrupt and cannot be used, and names a network error, a read error from media, or a problem with the package as the possibilities. A verified copy from a local disk clears nearly all of these.

Download the package again to C:\pkg first, then run these from an elevated Command Prompt

certutil -hashfile C:\pkg\package.msi SHA256
msiexec /a "C:\pkg\package.msi" TARGETDIR="C:\pkg\extracted" /qb
msiexec /i "C:\pkg\package.msi" /l*v C:\pkg\install.log
  1. Download from the vendor’s own site to a local folder. Not a network share, not a USB stick, and not from inside a zip folder.
  2. Compare the file size with the published size. A short file is a truncated download and nothing else needs investigating.
  3. If the vendor publishes a checksum, compare it with the certutil output. If they publish nothing, the administrative extraction on the second line is the next best test – it unpacks the payload without installing anything.
  4. Install from the verified local copy.

If the extraction fails as well, the file is damaged and no repair tool will recover it. Replace the source rather than trying to salvage the cabinet.

If setup completes from the local copy you are done. If a verified copy still fails, the next section covers what else corrupts a payload between the vendor and the disk.

Why it happens

Most installers ship their files inside cabinet archives, either alongside the MSI or embedded in it. The package carries a manifest of every file, its size and its position within the cabinet. At the copy stage the installer opens the cabinet, seeks to the offset it expects and reads. If the bytes there do not decompress cleanly, or the file it finds is not the one the manifest describes, it stops.

That check is strict on purpose, because a half-written binary is worse than a failed install. It also means the code tells you almost nothing about the reason. A dropped connection, a filter driver that altered the stream, a failing USB stick, an interrupted copy and a proxy that rewrote the download all look identical at the point the cabinet is read.

The neighbouring codes narrow it usefully. 1334 says the named file could not be found inside the cabinet, which points at the wrong or an incomplete cabinet rather than damaged bytes. 1330 says the cabinet has an invalid digital signature, and the published message includes the error returned by the signature check, which moves the investigation to certificates and system time. 1331 is published as a CRC error during the copy, so the bytes changed rather than went missing. 1311 says a required source cabinet could not be located at all.

The download was incomplete or altered in transit

You have this one if The file size differs from the published size, or a download over a different connection installs cleanly.

  1. Download again over a different connection where you can, and avoid download managers that split the file into parts.
  2. Verify the hash with certutil -hashfile <file> SHA256 against the vendor’s published value.
  3. If your organisation inspects TLS or filters content, ask for the vendor’s download host to be excluded and try again.

Large installers suffer most. A proxy that truncates at a size limit produces a file that looks plausible until the cabinet is read.

Setup is running from inside an archive or across a flaky link

You have this one if The failure happens at the same point every time and the installer is being launched from a zip folder, a share, a mounted image or removable media.

  1. Extract the archive completely to a local folder and run setup from there.
  2. Copy the whole media locally, not just the executable, so every cabinet travels with it.
  3. If the source is an ISO, copy it to local disk before mounting it rather than mounting it across the network.

Security software is altering the file as it is read

You have this one if The download verifies correctly but setup fails only on machines running a particular endpoint product.

  1. Pause real-time protection briefly and retry, purely to confirm the cause.
  2. If that resolves it, add an exclusion for the installer’s working folder rather than leaving protection off.
  3. If the file was quarantined outright, restore it or download again after the exclusion is in place.

The storage holding the file is failing

You have this one if The same file fails from one disk or USB device and installs from another, and other large files from that device are also unreliable.

  1. Scan the volume without taking it offline: chkdsk C: /scan.
  2. Copy the package to different storage and rerun setup from there.
  3. If several unrelated packages fail with cabinet errors on one machine, treat the storage or memory as suspect rather than the downloads.

Full reference

What each number is published as

Number Published message
1311 Could not locate source file cabinet: [2].
1330 A file that is required cannot be installed because the cabinet file [2] has an invalid digital signature. This may indicate that the cabinet file is corrupt.
1331 Failed to correctly copy [2] file: CRC error.
1334 The file [2] cannot be installed because the file cannot be found in cabinet file [3]. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
1335 The cabinet file [2] required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

1330 deserves separate treatment because it is not really a corruption message. The signature check is performed by the operating system’s trust verification, and the published message carries the error that check returned. A machine with a badly wrong clock, or one missing the certificate chain the cabinet was signed with, fails this while holding a perfectly intact file. Check the date and the certificate before re-downloading anything.

Testing the payload without installing it

An administrative installation unpacks a package to a folder and touches nothing else on the machine. If it succeeds, the cabinet is intact and the fault lies somewhere else entirely, which is a useful thing to know before you spend an afternoon on permissions:

msiexec /a "C:\pkg\package.msi" TARGETDIR="C:\pkg\extracted" /qb

expand -D "C:\pkg\data1.cab"
expand -F:* "C:\pkg\data1.cab" "C:\pkg\out"

expand -D lists the contents of a cabinet without extracting, which tells you whether the directory of the archive is readable. expand -F:* extracts everything. If the listing works and the extraction fails part-way, the damage is at a fixed offset, which is the signature of a truncated or altered download rather than a random hardware fault.

Where to get the file

  • The vendor’s own download page, or your own volume licensing portal. Nothing else.
  • Mirrors and download aggregators repackage installers, and an unexpected cabinet error is exactly the symptom that produces.
  • For an internal distribution point, verify the hash once when you stage the file and again after replication, not just at the source.
  • Keep the checksum with the file. It is the only way to tell six months later whether the copy on the share is the copy you approved.
  • If the vendor publishes no checksum, an administrative extraction on a known-good machine is a reasonable substitute for one.

When a verified file still fails

  1. Confirm the installer is being run from a local path, and that the path is short and contains no unusual characters.
  2. Check free space on the volume holding the temporary folder, not just on the install target.
  3. Test the memory in the machine if several unrelated packages fail. Decompression is one of the few desktop workloads that reliably surfaces bad RAM.
  4. Look for a filter driver from a backup, encryption or endpoint product in the path, and check the vendor’s guidance on exclusions.
  5. Try the same file on a different machine on the same network. If it installs, the fault is the machine; if it does not, it is the file.

Every code this article covers

Code What it points at Source
1335 The cabinet holding the installation payload is corrupt and cannot be used Microsoft Learn
1334 A file listed in the package could not be found inside the cabinet Microsoft Learn
1330 The cabinet has an invalid digital signature; the message carries the error the signature check returned Microsoft Learn
1331 A file was not copied correctly: a CRC error, so the bytes changed rather than went missing Microsoft Learn
1311 A required source cabinet could not be located Microsoft Learn

Confirm the fix worked

  1. Compare the hash of the local copy with the vendor’s published checksum and confirm they match.
  2. Run an administrative extraction with msiexec /a and confirm it completes without error.
  3. Install from the verified local copy and confirm setup reaches completion.
  4. Open the installed application and confirm the components that were being copied when it failed are present and working.
  5. If the file came from an internal share, re-verify the copy on the share so the next person does not repeat this.

Questions people ask about this

Do I need to buy a replacement copy of the software?

No. A corrupt cabinet is a damaged copy of a file, not a licensing problem. Downloading the same package again under your existing entitlement costs nothing, and your key is unaffected by a failed download.

Should I trust a copy of the installer from a third-party download site?

No. Mirrors are a frequent source of altered or repackaged installers, and an unexpected cabinet error is exactly what one produces. Take the file from the vendor or from your own licensing portal.

Can I repair the cabinet instead of re-downloading?

In practice, no. Cabinet compression is not designed to survive partial damage, and any tool claiming to salvage one hands you files you cannot trust. Replace the source.

Why does it fail at the same percentage every time?

Because the damage is at a fixed offset in the file. The installer reads sequentially and reaches the bad region at the same point on every attempt, which points at a truncated or altered download rather than a random hardware fault.

I get 1330 rather than 1335. Is that the same thing?

Not quite. 1330 is a signature verification failure, and the published message carries the error the check returned. A wrong system clock or a missing certificate chain produces it while the file itself is perfectly intact, so check those before downloading again.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x803F8001: This App Is Not Licensed for Your Account or This Device Free Fix MSI Error 1603: Fatal Error During Installation and How to Find the Cause Free Fix MSI 1618: Another Installation Is Already in Progress – Clearing the Lock Free Fix MSI 1639 and 1624: Invalid Command Line or Transform in Silent Deployments
โ† Back to Knowledge Base