When a game installation reports corrupted files, such as Battle.net saying that "files in your Heroes of the Storm installation are damaged," protect saves, configuration, and mods, then run that launcher’s official repair once. Battle.net calls it Scan and Repair; Steam, Epic, and the EA app call it Verify or Repair. Note whether the failure occurred during download, installation, verification, or launch. If corruption returns after a clean repair, investigate storage, write permissions, security quarantine, and hardware instead of repeating an endless download.

Key Takeaways

Preserve the exact file, error code, stage, launcher, install path, and time.

Back up irreplaceable saves, configuration, and mod lists before repair or reinstall.

Use only the affected launcher’s official Verify or Repair workflow.

Review security quarantine without disabling protection or restoring an unverified file.

Repeated corruption after a clean repair is evidence to inspect storage, permissions, memory, or another writer.

This guide covers files in a game installation, not damaged personal documents, cloud-save conflicts, or operating-system system files. The data-corruption explainer covers the general concept, while the game-save synchronization guide protects progress across devices. For other launcher and platform problems, start from the entertainment troubleshooting hub.

1. Which stage failed when a game installation reports corrupted files?

Write down the launcher, game, edition, install path, exact error, named file, percentage, and local time. Then classify the stage:

Stage	What is being handled	First owner to inspect
Download	Chunks, manifests, temporary files	Launcher cache, network delivery, temporary storage
Installation	Decompression, patching, writing final files	Free space, file system, permissions, security software
Verification	Comparison with publisher manifest	Modified, missing, quarantined, or unreadable files
Launch	Runtime libraries, configuration, mods, anti-cheat	Game, dependencies, security controls, local changes

A generic “corrupted” message can describe a failed archive extraction, a checksum mismatch, a file that another process changed, or an unreadable storage block. Do not assume the download itself is bad until the stage is clear.

If the error names a save or profile rather than an installation file, stop. Do not let a repair tool overwrite the only copy of personal progress. Back it up and use the game’s save-recovery documentation.

2. What should you back up before repair?

Protect data that the launcher may not own:

Local saves that are not confirmed in cloud storage.
Configuration and accessibility settings.
Screenshots, custom maps, replays, and exported creations.
A list of mods and load order, plus original archives where licensed.
The exact install path, game edition, branch, and optional content.

Do not copy unknown executable or modified game files into the future clean installation. The backup is for irreplaceable user data and a record of customizations, not a way to reintroduce the same mismatch.

If cloud saves are enabled, confirm their state rather than assuming “synced” means the desired version is safe. Keep a separate local copy where the platform allows it. If the storage device itself may be failing, copy only essential personal data first and minimize further writes.

3. Are storage space and the install path healthy?

Check free space on both the installation volume and the system or temporary volume. A patch can require working space in addition to the final game size. Keep the path mounted and writable throughout the operation.

If the library is on an external drive, confirm the drive is present under the same mount or drive letter, uses a supported file system, and is not read-only. EA’s current support guidance explicitly distinguishes download, installation, and loading problems and notes that drive format or write access can affect installation behavior.［1］

Inspect the operating system’s storage-health warnings and the drive vendor’s supported diagnostic tools. Do not run destructive repair, reformat, or surface-write tests before backing up personal data. If the drive disconnects, reports I/O errors, or disappears, use the external-drive detection guide before reinstalling the game.

Avoid moving only part of a game folder by hand while the launcher is active. Use the launcher’s supported move or library-management feature so its manifest and path remain consistent.

4. Are permissions blocking installation or repair?

Confirm the current user and the launcher’s service can write to the documented library path. A folder copied from another computer, restored from backup, or moved between drives can retain ownership or read-only attributes that differ from the launcher’s expectations.

Use the operating system’s normal permission view and the publisher’s documented procedure. Do not grant broad write access to every user, disable User Account Control permanently, or run unknown tools as administrator. A temporary elevated launch is useful only when the publisher explicitly requires it and the executable is verified.

EA documents a permissions branch for Create Folder errors and separate write-access checks for external drives.［1］ Apply those instructions to the EA app only when the error and platform match. Other launchers use different services and directories.

Close other launchers, mod managers, backup tools, and file-sync applications that may be writing the same library during one controlled repair. This is a local single-operation baseline, not a recommendation to disable normal protection permanently.

5. How should you use Verify or Repair?

Use the affected launcher’s official command once, with the game closed and the install volume stable. Do not run two launchers or repair tools against the same files simultaneously.

Epic’s Verify function checks installed files and replaces or repairs files that differ; Epic says saved data is not affected in that specific workflow.［2］ Do not generalize that promise to every launcher, game, mod, or configuration file. Backups still come first.

EA’s app provides a Repair action from the game’s library menu for games that do not load.［1］ Steam likewise provides Verify Integrity of Game Files for local installation files.［3］ Use the current official menu for your launcher rather than deleting random folders from an older forum post.

Record the verification result:

Number or name of files reacquired, if shown.
Whether the same file fails again.
Whether the game launches before mods or custom assets return.
Whether a second verification immediately reports another mismatch.

One repaired file can be a normal local difference. The important signal is whether the same controlled baseline remains healthy.

6. Could security software have quarantined a file?

Open the security product’s history or quarantine view and look for an event at the time of the failure. Check the file path, detection name, signer, and publisher guidance. Do not disable antivirus or restore a file merely because the game wants it.

If a legitimate file was removed, update the launcher and security definitions, then use the official Verify or Repair command to reacquire it from the publisher. Submit a suspected false positive through the security vendor’s official process if the signature and source are verifiable.

If the file is unsigned, comes from a mod, or differs from the publisher manifest, leave it quarantined until its source is established. Never add the entire game library to a permanent exclusion list as a convenience.

A file that is repeatedly quarantined after official repair needs publisher and security-vendor review. Reinstalling without understanding the detection only repeats the same event.

7. Are mods or custom files changing the installation?

Mods, injectors, reshade tools, unofficial translations, custom maps, and edited configuration can intentionally change files that verification expects to match. Preserve the mod list and user data, then return to the game’s documented clean baseline.

Disable the mod manager and remove custom assets through its supported profile or deployment function. Do not simply delete shared runtime libraries from the game folder. Verify the clean game, launch it once without modifications, and test the same scene.

If the clean game works, restore mods in small groups and confirm game-version compatibility. A mod that was safe for an older build may overwrite a file changed by an update. The publisher’s verifier is not a mod compatibility checker.

Keep game saves separate from installation mods. If a mod changes the save format, read its removal instructions before opening the save in a clean game.

8. What if repair fixes the files only temporarily?

Repeated corruption after a clean verification points beyond one bad download. Record whether failures follow a reboot, large update, system crash, security scan, storage disconnect, or memory-intensive workload.

Check, in a safe order:

Operating-system storage and file-system warnings.
Drive health using supported read-only diagnostics first.
Cable, enclosure, port, power, and mount stability for external storage.
Memory diagnostics if unrelated applications also report corrupted archives.
Background sync, backup, cleanup, or mod tools writing the library.
Available space on system and installation volumes.

Do not continue writing hundreds of gigabytes to a drive that reports I/O errors. Protect personal data and seek hardware support. A launcher reinstall cannot repair failing storage.

If only one game and one file repeatedly fail on a healthy volume, provide the manifest result and file path to the publisher. The issue may be an update-package or compatibility defect.

9. When should you try another official install location?

Use another location only after the current path, permissions, and storage are documented. Choose a supported internal or external volume with enough space and a suitable file system. Use the launcher’s library move function when possible.

Install or move one affected game, not the entire library. Keep the launcher version, game branch, mods-off state, and security configuration unchanged. If the same package succeeds elsewhere, the original path or storage becomes the leading branch.

Do not use a network share, cloud-synced folder, case-sensitive file system, or removable format unless the publisher explicitly supports it. A location that accepts files is not necessarily a supported game library.

10. When is a full reinstall justified?

Reinstall after backups, space, permissions, official repair, security history, and mods have been checked. Confirm how the launcher treats installed games and local saves before uninstalling either component.

Remove only the affected game through the launcher’s official flow. Preserve the diagnostic error and verification result. Download again from the official store without restoring old executable or modified files, then launch once before adding mods.

If the fresh installation reports the same corruption on the same drive, stop reinstalling and investigate storage or publisher packaging. If it fails on multiple healthy drives and networks, send the publisher a reproducible case.

11. What should you send to support?

Include:

Launcher and exact version.
Game edition, branch, build, and optional content.
Exact error, file path, stage, timestamp, and time zone.
Install volume, file-system type, free space, and whether it is external.
Verify or Repair result and whether the same file returned.
Security quarantine result and mod state.
Whether another supported install location changed the outcome.
Storage warnings, with personal device identifiers redacted.

Do not upload saves, logs, or diagnostic archives publicly without reviewing them for usernames, email, tokens, and file paths. Use the publisher’s official private support channel.

Summary

Classify download, installation, verification, and launch errors separately.
Back up irreplaceable saves, settings, and mod records before repair.
Check free space, mount state, file system, write access, and background writers.
Use one launcher’s official Verify or Repair command with the game closed.
Review quarantine without disabling protection or trusting an unknown file.
Test a clean, mod-free baseline before restoring custom files.
Treat repeated corruption as storage, permission, memory, or packaging evidence—not a reason for endless reinstalls.

FAQ

What does "corrupt data found, please verify your installation" mean?

The game or launcher found local files that do not match what it expects. Close the game and run the check from the store you installed through: Steam's Verify Integrity of Game Files［3］, Epic's Verify［2］, the EA app's Repair［1］, or Battle.net's Scan and Repair. A "corrupted download" notice belongs to the download stage, so check free space and the library drive first. If the same message returns after one clean pass, treat it as repeated corruption (step 8) rather than verifying in a loop.

Does Verify delete my saves?

It depends on the launcher and game. Epic says its Verify workflow does not affect saved data, but that promise should not be extended to every platform. Back up irreplaceable saves first.

Should I disable antivirus before repairing the game?

No. Review quarantine and detection history, update definitions, and reacquire verified files through the official launcher. Do not restore an unknown file or exclude the whole library.

Why does the same file become corrupted again?

The storage, permissions, security software, a mod, another writer, memory, or the publisher package may be changing it. Record the repeated path and inspect those branches.

Are corrupted game files the same as corrupted saves?

No. Installation files can usually be reacquired from a publisher manifest. Saves contain personal progress and need a separate backup and recovery process.

Can low disk space cause a corruption error?

Yes. Installers may need temporary space to download, decompress, and replace files. Check both the game volume and the system temporary volume.

Should I delete the whole game folder manually?

Not as an early step. Manual deletion can remove saves, mods, or launcher metadata and destroys useful evidence. Use the official Verify, Repair, move, or uninstall flow.

Can mods make verification fail?

Yes. Mods and custom assets may intentionally alter files that the official manifest expects. Preserve the mod list, test a clean profile, and restore compatible mods gradually.

When does the storage device need attention?

Investigate it when corruption repeats after clean repair, I/O errors appear, the drive disconnects, or unrelated archives also fail. Back up personal data before any destructive disk action.

Sources

EA Help, games that will not download, install, or load in the EA app — https://help.ea.com/en/articles/orders-and-rewards/ea-app-game-download-installation-loading-not-working/
Epic Games Support, verify game files in the Epic Games Launcher — https://www.epicgames.com/help/c-202300000001639/c-EpicGamesStore_Launcher/a202300000017217
Steam Support, Verify Integrity of Game Files — https://help.steampowered.com/ms/faqs/view/0C48-FCBD-DA71-93EB

Sources checked 4 October 2026.

Game Installation Reports Corrupted Files: What to Check