How to Fix Corrupted Files in Windows 11 & 10 (10 Fixes)

byKona -
0

How to Fix Corrupted Files in Windows 11 & 10 (10 Proven Methods)

Repair corrupted files in Windows 11 and Windows 10

If a program suddenly refuses to open, a file won't load, or Windows throws a strange error out of nowhere, you're probably dealing with a corrupted file. It's one of the most common — and most misunderstood — problems on Windows 11 and Windows 10, and the good news is that you almost never need to reinstall Windows to fix it.

In this guide, you'll learn how to fix corrupted files in Windows 11 and Windows 10 using 10 proven methods, starting with the simplest built-in tools and working up to more advanced repairs. Every step is written for beginners, so you don't need any technical background to follow along.

Quick Answer: The fastest way to fix corrupted files in Windows is to run the SFC scan (sfc /scannow) followed by DISM RestoreHealth. These two built-in tools repair most corrupted system files automatically, without deleting your personal data.

Table of Contents

What Causes Corrupted Files in Windows?

Corrupted files don't appear out of thin air. Something on your PC triggers them, and knowing the cause helps you pick the right fix instead of guessing.

  • Sudden power loss — a shutdown mid-write to disk while Windows is saving or updating a file.
  • Bad sectors on the hard drive or SSD — physical or logical damage that scrambles stored data.
  • Malware or virus infections — some malware deliberately damages system files to hide itself.
  • Failed Windows updates — an update that's interrupted partway through can leave system files half-written.
  • Running low on storage or memory — Windows can fail to write files correctly when resources run out. If this happens often, our guide to fixing low memory issues on a Windows PC is worth a look.
  • Faulty RAM or a failing drive — hardware errors can silently corrupt data as it's written.
  • Improperly removed USB drives — yanking out a USB drive while it's transferring data is a common cause of corrupted files. If Windows won't recognize a drive afterward, see our USB device not recognized fix.
  • Third-party disk tools and forced shutdowns—cleanup utilities that interrupt a file mid-write or holding the power button during a Windows Update can leave critical files half-written and unreadable.

Most of the time it's not just one of these on its own—it's a combination, like a power outage happening while an update is installing. That's why the fixes below start with software-level repairs and only move toward disk checks and reinstalling Windows if the simpler methods don't resolve things.

Signs Your Files or System Are Corrupted

File corruption doesn't always announce itself clearly. Here are the most common warning signs:

If any of this sounds familiar, don't panic. Work through the fixes below in order—they're arranged from safest and simplest to more advanced.

Two Kinds of "Corrupted Files" (and Why It Matters)

Before jumping into fixes, it helps to know which type of corruption you're dealing with, because the right tool depends on it.

  • Corrupted system files — these are the core Windows files that keep the operating system running. When these break, you'll see crashes, error codes, boot failures, or missing features. This is what SFC, DISM, CHKDSK, and Startup Repair are built to fix.
  • Corrupted personal files — a single document, photo, video, or downloaded file that won't open properly. This usually happens from an interrupted transfer, a bad USB removal, or a failing drive, and it's fixed differently — often by re-downloading the file, restoring from a backup, or using file-repair software for that specific format.

This guide focuses mainly on system-level corruption, since it's the more common—and more disruptive—of the two. If it's a single personal file causing trouble, start with Fix 6 (System Restore) or check whether you have a cloud backup or previous version saved.

Which Fix Should You Try First?

If you're not sure where to start, use this quick guide based on your symptoms:

  • Apps crashing or random errors while Windows runs normally → Start with Fix 1 (SFC) and Fix 2 (DISM).
  • SFC scan keeps failing or can't complete the repair → Run Fix 2 (DISM) first, then repeat Fix 1.
  • Fixes 1–2: Won't run properly, or files are locked → Try Fix 3 (Safe Mode).
  • Windows won't boot into the desktop at all → Skip ahead to Fix 4 (offline SFC), Fix 8 (Startup Repair), or Fix 9 (Reset This PC).
  • Problem started right after an update or new software → Try Fix 6 (System Restore) first.
  • You suspect a failing drive → Run Fix 7 (CHKDSK) before anything else.
.

Before You Begin

A couple of quick prep steps will save you time:

  1. Back up important files if you can — a quick copy to a USB drive or cloud storage is enough.
  2. Check your PC specs so you know your Windows version and available storage before troubleshooting. Here's how to check your PC specs in Windows.
  3. Make sure you're logged in as an administrator, since most of these fixes need admin rights.

Fix 1: Run an SFC Scan

Run SFC scannow command in Windows to repair corrupted files

The System File Checker (SFC) is Windows' built-in repair tool, and it should always be your first step. It scans every protected system file, compares it against a clean cached copy, and automatically replaces anything that's damaged or missing.

  1. Click Start, type cmd, right-click Command Prompt, and choose Run as administrator.
  2. Type the following command and press Enter:
sfc /scannow

The scan usually takes 10–20 minutes. Don't close the window while it's running. When it finishes, you'll see one of three messages:

  • "Windows Resource Protection did not find any integrity violations" — your system files are fine; move on to another fix.
  • "Windows Resource Protection found corrupt files and successfully repaired them"—the problem is fixed. Restart your PC.
  • "Windows Resource Protection found corrupt files but was unable to fix some of them" — move on to Fix 2.

Why does SFC sometimes fail to complete the repair? It relies on a local cache of clean, original Windows files stored on your PC. If that cache is itself damaged or the specific file version doesn't match what's expected, SFC has nothing reliable to copy from—which is exactly the gap Fix 2 is designed to close.

Tip: Always run DISM before SFC if the scan keeps failing. SFC relies on a healthy Windows image to pull replacement files from — if that image is also damaged, SFC can't finish the repair.

Fix 2: Run DISM RestoreHealth.

DISM RestoreHealth command repairing Windows system image

DISM (Deployment Image Servicing and Management) repairs the underlying Windows system image itself. This is essential when SFC can't complete its repair, because SFC pulls clean files from that same image.

  1. Open Command Prompt as administrator again.
  2. Run this command:
DISM /Online /Cleanup-Image /RestoreHealth

This process downloads replacement files from Windows Update, so make sure you're connected to the internet. It can take 15–30 minutes and may appear stuck at certain percentages (like 20% or 40%); that's normal, so let it run.

Once it finishes, run sfc /scannow again. With a repaired system image in place, SFC will usually complete successfully this time.

If your PC has no internet connection, DISM can also pull replacement files from a mounted Windows ISO instead of Windows Update, using the /Source flag. This is a good option on a fresh install or a PC with limited connectivity.

Fix 3: Restart in Safe Mode and Try Again

.
Starting Windows 11 and 10 in Safe Mode to repair corrupted files

Sometimes a background app or driver locks a file that SFC or DISM needs to replace, which causes the repair to fail. Safe Mode loads Windows with only the essentials running, clearing that conflict out of the way.

For full step-by-step instructions, see our guide on how to boot Windows 10 & 11 in Safe Mode. Once you're in Safe Mode, repeat Fix 1 and Fix 2 from a Command Prompt.

Safe Mode is also useful for narrowing down the cause. If your PC runs fine in Safe Mode but keeps crashing normally, that points toward a third-party app or driver rather than deep system corruption — worth keeping in mind if the repairs above don't fully resolve things.

Fix 4: Run an Offline SFC Scan.

Offline SFC scan using Windows installation media


If Windows won't fully boot, or a critical file is corrupted while Windows is running (so it can't be replaced live), you can run SFC from outside your normal Windows environment using bootable installation media.

  1. Create a bootable USB drive using the Media Creation Tool. If Windows doesn't detect your USB drive properly at any point, check our USB device not recognized guide.
  2. Boot from the USB drive and select Repair your computer > Troubleshoot > Advanced options > Command Prompt.
  3. Find your Windows drive letter (it's often D: in this environment, not C:) by typing:
wmic logicaldisk get caption
  1. Run the offline scan, replacing the letters with your actual drive letters:
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

This lets SFC repair files even though the damaged copy of Windows isn't currently running. It's a more technical process than the earlier fixes, but it's often the difference between a full reinstall and a quick repair when Windows can't start normally.

Fix 5: Manually Replace a Corrupted File

.
Manually replacing a corrupted system file using Command Prompt

If SFC identifies a specific file it can't fix, you can sometimes replace it manually with a healthy copy from another PC running the same Windows version and build.

  1. Check the log at C:\Windows\Logs\CBS\CBS.log to find the exact file path SFC couldn't repair.
  2. Take ownership of the file:
takeown /f C:\path\to\file
icacls C:\path\to\file /grant administrators:F
  1. Copy a known-good version of the file from a matching Windows installation, then paste it into the same location, overwriting the damaged one.
Note: This method is more advanced and best used only when Fixes 1–4 haven't solved the problem. Always match the exact Windows build number, or you risk introducing new errors.

Fix 6: Use System Restore

.
Using System Restore to fix corrupted files in Windows

If the corruption started after a recent update, driver installation, or software change, System Restore can roll your PC back to a point before the problem began—without touching your personal files.

  1. Type Create a restore point in the Start menu search and open it.
  2. Click System Restore and choose a restore point dated before the issue started.
  3. Follow the prompts and let your PC restart.

This only works if System Protection was turned on beforehand and restore points exist. If you don't see any listed, skip to the next fix.

It's worth checking that system protection is switched on now, even if it wasn't before, so you have a safety net for next time. You'll find this under System Protection in the same window — enable it for your main drive and set aside a small amount of disk space for future restore points.

Fix 7: Run CHKDSK to Fix Disk Errors.

Running CHKDSK command to scan and repair disk errors in Windows

If your hard drive or SSD has bad sectors or file system errors, corruption will keep coming back no matter how many times you run SFC. CHKDSK scans the drive itself and repairs the underlying file system.
  1. Open Command Prompt as an administrator.
  2. Run:
chkdsk C: /f /r

Since your system drive is in use, Windows will ask to schedule the scan on the next restart — type Y and reboot. The scan can take anywhere from 20 minutes to a couple of hours depending on drive size and health, so let it run fully.

Disk-level corruption can also cause unrelated symptoms, like a DNS server not responding error or devices that randomly disconnect—worth keeping in mind if CHKDSK turns up repaired sectors.

If CHKDSK reports a large number of bad sectors, treat that as an early warning rather than a one-time fix. Bad sectors tend to increase over time on aging drives, so back up your files soon and consider replacing the drive if the count keeps growing after future scans.

Fix 8: Use Startup Repair.

.Using Startup Repair tool to fix corrupted boot files in Wind

When corrupted files affect boot-critical components, Windows may fail to start altogether. Startup Repair is designed specifically to diagnose and fix this kind of damage automatically.
  1. Force your PC to shut down 2–3 times during boot to trigger Automatic Repair, or boot from installation media.
  2. Select Troubleshoot > Advanced options > Startup Repair.
  3. Let Windows scan and fix startup-related issues automatically.

If your PC won't boot at all and shows a "no bootable device" message instead, that's a different issue with its own fixes — see our guide on the No Bootable Device Found error (13 fixes). A corrupted boot sector can also show up as a white screen at startup, so that guide is worth checking too if Startup Repair doesn't resolve it.

Fix 9: Reset This PC.


If nothing above has worked, Reset This PC reinstalls Windows while giving you the choice to keep your personal files. It replaces every system file with a fresh copy, wiping out corruption that's too deep for SFC or DISM to reach.

  1. Go to Settings > System > Recovery.
  2. Click Reset PC.
  3. Choose Keep my files to preserve personal documents, photos, and data while reinstalling Windows itself.

This process can take an hour or more. Apps will need to be reinstalled afterward, but your files, photos, and documents stay intact.

There's also a "Remove everything" option in the same menu, which wipes the drive completely. Choose this only if you've already backed up everything you need—it's a good middle ground between Keep my files and a full manual clean install.

Fix 10: Clean Install Windows

If corruption is severe, widespread, or tied to a failing drive, a clean install is the most reliable fix. It wipes the drive completely and installs Windows from scratch.

  1. Back up all your personal files first—a clean install erases everything on the drive.
  2. Create bootable installation media using the Media Creation Tool.
  3. Boot from the USB drive, choose Custom install, and select your drive to install a fresh copy of Windows.

This should be your last resort, but it guarantees a 100% clean system with zero leftover corruption.

After a clean install, take a few minutes to install Windows Updates and your storage/chipset drivers before restoring your personal files. Setting up System Protection and a regular backup routine at this point will make any future corruption far easier to recover from.

How to Prevent File Corruption in the Future

  • Use a UPS or laptop battery backup to avoid sudden power loss during writes
  • Keep at least 15–20% of your drive free—running low on space is a common trigger, so check out our tips to fix low memory on a Windows PC
  • Always use "Safely Remove Hardware" before unplugging USB drives
  • Keep Windows Update and your antivirus running regularly
  • Run sfc /scannow occasionally as routine maintenance, even before problems appear

Frequently Asked Questions

What is the fastest way to fix corrupted files in Windows?

Running sfc /scannow in an administrator Command Prompt is the fastest first step. It automatically finds and repairs damaged system files in most cases within 10–20 minutes.

Does DISM RestoreHealth delete my files?

No. DISM only repairs the underlying Windows system image. Your personal files, documents, and installed apps are untouched.

Can corrupted files cause my PC to run slowly?

Yes. Corrupted system files can trigger crashes, freezing apps, and unusual slowdowns, including issues like high GPU usage from background processes.

What's the difference between SFC and CHKDSK?

SFC repairs damaged Windows system files, while CHKDSK scans and repairs the physical or logical health of the drive itself, including bad sectors and file system errors.

Will Reset This PC delete my personal files?

Not if you choose the Keep my files option. It reinstalls Windows and removes apps, but your documents, photos, and personal files remain.

How do I know if a corrupted file is caused by a failing hard drive?

If CHKDSK repeatedly finds and repairs bad sectors, or corruption keeps returning after fixing it, that's a strong sign your drive may be failing and should be backed up immediately.

Do I need to run SFC and DISM every time Windows updates?

No, not routinely. It's a good idea to run sfc /scannow occasionally as maintenance, but you only need DISM when SFC reports errors it can't fix or when you're troubleshooting a specific problem.

Can I fix corrupted files without losing any data?

Yes. Fixes 1 through 8 in this guide — SFC, DISM, Safe Mode, offline SFC, manual file replacement, System Restore, CHKDSK, and Startup Repair — do not delete your personal files. Only Fix 9 and Fix 10 involve reinstalling Windows, and even Reset This PC lets you keep your files if you choose that option.

Tags

You may like these posts

Post a Comment

Previous Post Next Post