How to Check for Corrupted Files in Windows 11

Corrupted files are more common than most people realize. A sudden power cut, a failed update, a misbehaving driver, or even normal wear on storage hardware can quietly damage system files — often without any obvious warning until something goes wrong. Windows 11 includes several built-in tools specifically designed to detect and repair this kind of damage, and knowing how to use them can save a lot of troubleshooting time.

What Causes File Corruption in Windows 11?

Before running any scans, it helps to understand what you're actually looking for. File corruption happens when the data stored in a file becomes inconsistent, incomplete, or unreadable. In Windows, this most commonly affects:

• System files — the core files Windows needs to boot and run
• Application files — program data that gets partially written or overwritten
• User profile files — settings and data tied to your account

Common causes include interrupted writes (such as a forced shutdown), bad sectors on a hard drive or SSD, malware, failed Windows Updates, and hardware faults like failing RAM.

The Primary Tool: System File Checker (SFC)

The System File Checker (SFC) is Microsoft's built-in utility for scanning and repairing protected system files. It compares your current system files against a cached version of what they should look like, then replaces any that don't match.

How to Run SFC in Windows 11

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

sfc /scannow 

3. Wait — this can take 10–20 minutes depending on your drive speed and system size
4. When it finishes, you'll see one of three results:

If SFC reports that it couldn't repair all files, that's where the next tool comes in.

The Deeper Scan: DISM

DISM (Deployment Image Servicing and Management) repairs the Windows image that SFC relies on. If SFC's repair cache is itself damaged, SFC can't fix anything — DISM addresses that problem by pulling a clean image from Windows Update servers.

How to Run DISM

Open Command Prompt as administrator and run these commands in order:

DISM /Online /Cleanup-Image /CheckHealth 

This quickly checks for any flagged corruption without making changes.

DISM /Online /Cleanup-Image /ScanHealth 

This performs a deeper scan. It can take 15–30 minutes. 🕐

DISM /Online /Cleanup-Image /RestoreHealth 

This downloads and replaces corrupted components. Requires an active internet connection.

After DISM completes, run sfc /scannow again. The two tools work best in combination — DISM repairs the foundation, then SFC rebuilds on top of it.

Checking for Disk-Level Issues: CHKDSK

SFC and DISM target Windows system files specifically. CHKDSK (Check Disk) operates at a lower level, scanning the file system and physical storage for bad sectors, allocation errors, and structural problems.

When to Use CHKDSK

CHKDSK is particularly relevant when:

• Files outside the Windows system folder seem corrupted
• You're seeing read/write errors in apps
• The drive has been through a sudden power loss or improper ejection
• Your PC is running on an HDD (which is more physically vulnerable than an SSD)

Running CHKDSK

In Command Prompt as administrator:

chkdsk C: /f /r 

• /f — fixes file system errors
• /r — locates bad sectors and recovers readable data

Because the C: drive is in use while Windows is running, CHKDSK will ask to schedule the scan for the next restart. This is normal.

⚠️ On HDDs, a full CHKDSK scan with /r can take several hours. On SSDs, it's significantly faster, though bad sector scanning is less relevant since SSDs don't use spinning platters.

Reading the Results

Once scans complete, you can check logs to see exactly what was found:

• SFC log: Located at C:WindowsLogsCBSCBS.log — search for entries marked [SR]
• DISM log: Located at C:WindowsLogsDISMdism.log
• CHKDSK results: Open Event Viewer → Windows Logs → Application → look for Wininit source events

These logs can get technical, but the key thing to look for is whether errors were detected and whether they were successfully repaired.

When Built-In Tools Aren't Enough

If all three tools report problems they can't fully fix, the issue may be deeper than software can address. Persistent corruption after running SFC and DISM together sometimes points to:

• Failing storage hardware — particularly relevant for older HDDs
• Faulty RAM — use Windows Memory Diagnostic (search mdsched.exe) to test
• A corrupted Windows installation — at which point an in-place repair install or a clean install becomes worth considering

Variables That Affect Your Experience

How these tools perform — and which one you actually need — depends on factors specific to your setup:

• Storage type: HDDs are more prone to bad sectors than SSDs, making CHKDSK more critical on older machines
• Windows version and update status: DISM pulls repair files from Windows Update, so being up-to-date matters
• How the corruption happened: Malware-related corruption may return unless the underlying threat is removed first
• Technical comfort level: SFC is the most beginner-friendly; DISM and CHKDSK require more patience and administrator access

A system that's been running stable for three years with one interrupted update is a very different situation from a machine showing persistent errors after a hard drive has logged thousands of hours of use. The right sequence — and whether repairs fully stick — depends on what's actually going on under the hood of your specific machine.