How to Fix a 'File Is Corrupted' Error on Windows

Corruption almost always traces back to the bytes themselves being wrong or incomplete. The common causes are:

• Incomplete download - the transfer stopped early, so the file is truncated and missing its end.
• Transfer errors - dropped packets on an unstable connection altered the contents in transit.
• A bad source file - the copy on the server or mirror was already damaged before you downloaded it.
• Storage problems - failing sectors on an HDD or SSD can corrupt files as Windows writes them.
• Antivirus modification - security software occasionally strips or quarantines part of a file, leaving the rest unusable.

Before assuming the worst, compare the size of your downloaded file with the size listed on the vendor's download page. A file that is noticeably smaller than advertised is almost certainly an incomplete download. For archives, right-click a ZIP and choose Extract All; if Windows reports the archive is invalid, the file is damaged rather than the program that opens it.

The definitive test is a checksum. Reputable vendors publish an SHA-256 or MD5 hash for their files. If your downloaded file's hash does not match the published value, the file is corrupted or has been tampered with, and you should not run it.

Windows has a built-in way to check a file's hash. Open PowerShell and run Get-FileHash -Algorithm SHA256 "C:\path\to\file", then compare the result with the hash on the vendor page. A match means the file arrived intact; a mismatch means redownload it. This step is your single best defence against both corruption and tampered installers.

If you prefer a graphical tool, utilities such as 7-Zip can compute CRC and SHA hashes from a right-click menu. Whichever method you use, treat a hash mismatch as a hard stop - never run an installer whose checksum does not match the official value.

If the file is corrupted, the most reliable fix is to download it again from the official vendor, not from a cached copy or a mirror. Before you redownload, delete the broken file so the browser does not append a number and confuse you, and clear your browser cache so it fetches a clean copy rather than serving the damaged one again.

For large files, use a wired connection or a download manager that supports resuming and integrity checks. This dramatically reduces the chance of the same transfer error recurring. Once the file is down, verify the checksum again before opening it.

If multiple unrelated files keep corrupting, the issue may be your storage rather than any single download. Run chkdsk /f on the affected drive from an elevated Command Prompt to scan for and repair file-system errors, and check the drive's health with a SMART monitoring tool. A drive that is failing will corrupt files no matter how cleanly you download them.

For corrupted Windows system files specifically, run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth in an elevated prompt. These repair damaged operating-system components that can cause widespread 'corrupted file' errors.