Fix errors when unzipping flight simulator downloads, including CRC failures, corrupt archives, long paths, blocked files and permission problems.
To fix errors when unzipping flight simulator downloads, move the archive to a short, local folder, confirm there is enough free space, and extract it again. If you see CRC, checksum or “unexpected end” errors, delete the file and download a fresh copy; the archive is usually incomplete or damaged.
This applies to general add-ons for MSFS, FSX, X-Plane, Prepar3D and older simulators. The simulator rarely causes an extraction failure: the fault normally lies with the downloaded archive, extraction program, destination path, storage or security software.
What does your unzip error mean?
The wording of the error usually identifies whether you need a fresh download, a shorter path or a different extraction method.
| Error message | Likely cause | Best fix |
|---|---|---|
| CRC failed, checksum error or data error | A damaged or incomplete archive | Delete the archive and download it again rather than reusing the same file. |
| Unexpected end of archive | The download stopped before the complete file arrived | Download a fresh copy without resuming the failed transfer. |
| Cannot open, invalid archive or unknown format | A corrupt file, incorrect extension or unsupported archive format | Check the real file type and use an extractor that supports it. Renaming the extension does not convert the archive. |
| Access denied or permission denied | The destination is protected, read-only or blocked by security settings | Extract into a user-owned working folder instead of the simulator directory or Program Files. |
| Path or filename too long | The combined folder and filename exceeds a Windows or application limit | Move the archive to a short path such as C:\SimTemp before extracting it. |
| Not enough space or write error | Insufficient storage or a failing destination drive | Free additional space and extract to a healthy local drive. |
| Password required or missing volume | The archive is protected or belongs to a multipart set | Check the download instructions, or place every archive part in one folder and open the first volume. |
If the message is vague, our archive extraction checklist for corrupt files and path problems covers the underlying tests in more detail.
How do you repair a failed extraction?
A clean extraction from a verified archive fixes most flight simulator download errors.
- Create a local working folder. Use a short, writable location on an internal drive. Do not start by extracting directly into an MSFS
Communityfolder, an X-Plane aircraft folder or another simulator installation directory. - Remove the failed output. Delete the partially extracted folder before trying again. Mixing new files with incomplete output can produce an add-on that installs but later fails to load.
- Check the downloaded file. Confirm that its extension matches the advertised format and compare its size with the download listing if a size is supplied. A suspiciously small ZIP may be an interrupted download or an error page saved under an archive filename.
- Download a fresh copy. Delete the original archive first. If the previous transfer stopped or resumed several times, begin a completely new download rather than continuing it.
- Allow enough working space. Extraction requires room for both the compressed archive and its expanded contents. Installation may temporarily create another copy, so free space should comfortably exceed the archive's displayed size.
- Check Windows blocking and permissions. For a trusted archive, open its Properties dialogue and use
Unblockif that option appears. Extract to a folder owned by your user account rather than immediately running the extractor as administrator. - Use a compatible extractor. ZIP, RAR, 7z and multipart archives are not interchangeable. Use software that explicitly supports the archive's real format and compression method, and do not rename extensions to force them open.
- Test repeated failures. Extract a known-good archive to the same drive. If fresh copies always fail on the same file, the source archive may be damaged; failures at changing points can indicate unstable memory, storage errors or interference from security software.
Should you extract directly into the simulator folder?
No; extract into a temporary working folder first, inspect the contents, and then install the actual package.
This prevents permission errors and makes nested folders easier to spot. It also avoids leaving half-written files in an active add-on directory when extraction fails. Once the archive opens correctly, follow our step-by-step add-on installation workflow to identify the correct aircraft, scenery or package folder.
Why does a CRC error return after downloading again?
A recurring CRC error means either every copy is arriving damaged or the extraction computer is corrupting data while reading, writing or decompressing it.
- Same filename every time: the archive stored at the source may be defective, particularly if its checksum does not match a published value.
- Different filename or point each time: test another local drive and check the system's storage and memory stability.
- Only one extraction program fails: the archive may use a method that program does not support correctly.
- The download repeatedly stops at the same size: browser caching, interrupted transfers, storage limits or security filtering may be truncating it.
If the CRC or Feature Transfer message appears while installing or updating official Microsoft Flight Simulator packages, it is not an ordinary add-on unzip problem. Use our guidance for diagnosing MSFS CRC and Feature Transfer errors instead.
Should you disable antivirus protection to extract an add-on?
No; do not disable system-wide protection simply to make an archive extract.
Check the security history to see whether a specific file was blocked or quarantined. Executable installers, scripts and DLL files deserve particular care. Only restore a detected file after confirming that the archive came from a trusted listing and that the detection is understood; repeatedly forcing an unexplained file through security controls is not a valid extraction fix.
Why is the add-on missing after extraction succeeds?
A successfully extracted add-on usually fails to appear because the wrong folder level was installed, not because unzipping failed.
- The outer folder may contain documentation and a second package folder that actually belongs in the simulator.
- The downloaded ZIP may contain another archive that must also be extracted.
- The package may require an installer rather than manual copying.
- The add-on may target a different simulator, edition or operating system.
- Security software may have removed one required file during extraction.
Inspect the extracted structure and read any included instructions before moving files. Never assume that the archive's outermost folder is the one the simulator needs.