How do I fix MSFS CRC or Feature Transfer errors?

A CRC or Feature Transfer error in Microsoft Flight Simulator means Windows could not read, verify or write data. Note the file and final error line, then replace a corrupt download or disc, check free space and errors on both drives, correct access permissions, and test storage or memory if the failing file changes.

What do CRC and Feature Transfer errors mean?

A CRC error, or cyclic redundancy check failure, means the data read from a package, archive or disc does not match its expected checksum. The source may be corrupt, but unstable memory, a faulty drive or a bad external-drive connection can also alter data during installation.

Feature Transfer Error is a broader installer heading. The useful information appears underneath it: the file or folder path and a message such as cyclic redundancy check, access denied, file not found or insufficient disk space.

Microsoft Flight Simulator 2020 and 2024 generally install digital packages through a platform client and the simulator’s package manager. The exact Feature Transfer wording is more common with boxed editions, older Flight Simulator installers and standalone add-on installers, although the underlying read and write failures can affect any edition.

Fix the MSFS installation error in the safest order

Work through these checks in order so that a damaged package is not mistaken for a failing drive or permissions problem.

1. Record the complete error. Note the filename, source path, destination path, error code and approximate installation percentage. A screenshot is useful because the installer may remove the message after it closes.
2. Restart Windows and retry once. This clears locked temporary files and abandoned installer processes. Repeating setup many times will not repair corrupt source data.
3. Check space on both drives. MSFS may download or decompress files on the Windows system drive even when the Packages folder is on another drive. Both locations need enough free space for the compressed download, temporary data and final package.
4. Check the installation source.
   • Digital package: Close the simulator and its launcher fully, then download the failed package again. If package downloads restart, loop or remain incomplete, use our MSFS package-download and launcher recovery checklist.
   • ZIP or other downloaded archive: A CRC message while extracting usually means the archive is incomplete or corrupt, not that MSFS itself is damaged. Download a fresh copy rather than trying to recover individual files; our archive-specific CRC and extraction checks cover that case.
   • Disc: Clean it using straight strokes from the centre outwards. Try copying the named CAB or data file to a temporary folder. If Windows cannot copy it, the installer cannot read it either; test another known-good optical drive before concluding that the disc is damaged.
   • ISO or local installer: Replace the complete image or installer from its original legitimate source. Do not obtain an individual CAB, DLL or package from elsewhere because it may belong to a different build.
5. Check the destination drive. Use Windows drive error checking, and connect external storage directly instead of through a hub. If the error occurs only on an external drive, try another cable and port. A local NTFS volume is the safest destination for a Windows app-managed installation.
6. Repair only the affected content. Use the platform client’s repair or verification option first. Be aware that platform verification may repair the launcher without replacing every package downloaded inside the simulator. For MSFS 2020, follow our platform-specific file and package repair methods before considering a reinstall.
7. Test memory and storage if the failure moves. Return CPU and memory settings to their defaults, temporarily including XMP, EXPO, undervolting or other overclocking. Run Windows Memory Diagnostic and the drive manufacturer-independent checks available through Windows. Failures on different files or at different percentages often indicate hardware instability rather than one corrupt package.

How do I fix Feature Transfer Error: Access is denied?

Access denied means Windows blocked the installer from reading the source or writing to the destination; it is a permissions or security problem, not a CRC mismatch.

1. Read the blocked path. A path under the source media points to an unreadable or quarantined installer file. A destination or temporary-folder path points to permissions, security software, a locked file or an unsuitable installation location.
2. Close programs using the folder. Exit MSFS, its launcher, archive tools and any programme displaying or synchronising the destination. Restart if the locked process is unclear.
3. Check Windows Security history. Restore a legitimate quarantined installer file only when you trust its source. If Controlled Folder Access blocked the installer, allow that specific trusted application rather than disabling protection system-wide.
4. Use elevation only where appropriate. Right-click a trusted legacy disc or standalone installer and run it as administrator. For Microsoft Store, Xbox app or Steam-managed editions, launch and repair the simulator through the normal platform client instead of running package files manually.
5. Choose a writable local destination. Avoid network shares, read-only folders and synchronised document folders. Confirm that your Windows account can create and delete a test folder at the chosen destination.
6. Do not alter WindowsApps permissions. Taking ownership of WindowsApps or granting broad Full Control permissions can break Microsoft Store servicing. If the denied path involves the Xbox app, Microsoft Store or error 0x80070005, use our Microsoft Store, Xbox app and Gaming Services recovery steps.

Is there a MAFS file system or an MSFS Packages folder?

Microsoft Flight Simulator does not use a Windows file system called MAFS or MSFS; on PC, its data sits on an ordinary storage volume, normally using NTFS, and simulator content is organised into packages.

If by “MAFS file system” you mean the MSFS package structure, look for the Packages location selected during installation. Its content root normally contains Community and Official. The exact path differs between Microsoft Store, Xbox app, Steam, custom installations, MSFS 2020 and MSFS 2024, so copying a path from another computer is unreliable.

The protected WindowsApps directory is not the folder to edit when replacing simulator packages. Do not take ownership of it. Likewise, do not confuse rolling-cache or streamed scenery data with the installed package source; MSFS 2024 streams more content than MSFS 2020, so not every asset is present as a conventional local file.

On Xbox, and for Microsoft Flight Simulator 2024 on PS5, these package folders are not exposed to the user. Remove and download affected content through the console’s storage interface instead of applying Windows file-system instructions.

How can I tell whether the download, drive or RAM is faulty?

The failure pattern across repeated attempts usually provides the strongest clue.

A repeatable failure on one file strongly implicates that source, but it is not absolute proof. A destination-drive fault can recur when the installer repeatedly writes to the same damaged area.

Should I delete the Packages folder or reinstall MSFS?

Do not delete the entire Packages folder or reinstall Microsoft Flight Simulator as the first response to a CRC or Feature Transfer error.

Start with the named file or package. Move or remove only clearly identified damaged content after closing the simulator and launcher, and preserve the Community folder if it contains add-ons you want to keep. Never combine partial package folders from different simulator versions or installations.

A full reinstall is justified only when the source has been replaced, both the system and destination drives pass their checks, memory is stable, permissions are correct and platform repair still cannot replace the affected content. Otherwise, reinstalling may download hundreds of valid files only to fail again for the same underlying reason.