SFC, DISM or CHKDSK? Choose the Right Windows Repair Tool

When Windows freezes, an update fails, or an application starts crashing, online advice often says to run SFC, DISM and CHKDSK in one long sequence. Those commands do different jobs. Running all three without deciding what is broken can waste time and, in the case of disk repair, change data on a volume that should have been backed up first.

Use SFC and DISM when you suspect damaged Windows system files or the Windows component store. Use CHKDSK when evidence points to file-system errors on a drive. If the PC is reporting an unhealthy SSD, repeated read failures, or missing personal files, protect your data before attempting repairs. None of these three commands is a universal fix for bad drivers, malware, failing hardware or damaged documents.

This guide applies to a Windows 11 PC that still starts normally. The commands and their scope are grounded in Microsoft's documentation. They are not described as tests performed on a faulty Jitsumi computer.

One comparison before you open Command Prompt

Think in layers. SFC inspects protected Windows system files. DISM services the Windows image and its component store, which is one source from which Windows can repair itself. CHKDSK examines the structure of a disk volume's file system, rather than the integrity of the Windows installation as a set of components. The distinctions follow Microsoft's System File Checker instructions, Windows image repair reference, and CHKDSK command reference.

For example, Windows Update fails with component corruption: the DISM/SFC route is relevant. A drive reports damaged directory structures: CHKDSK may be relevant after the data is protected. One third-party game crashes while the rest of Windows works: investigate the game's own logs and support guidance before treating the entire operating system as corrupt.

Decide whether a repair is appropriate at all

Start by writing down a reproducible symptom: the exact error, when it began, and whether it affects one app, all apps, a particular drive, or Windows itself. Check whether a recent Windows update, driver installation, storage warning or power interruption coincided with the first failure.

If personal files are important, make a separate backup and check that the copied files open. A repair tool is not a substitute for a recovery copy. If a drive is disappearing, clicking, reporting critical health warnings or producing repeated read errors, avoid a stressful series of full-disk scans; prioritise safe data recovery and the storage vendor's diagnostics. Microsoft's Windows recovery overview likewise recommends protecting important data before changing the system.

On a work-managed PC, check with IT before using an elevated repair command. An enterprise may provide approved recovery sources and maintenance procedures that differ from a home computer.

Route A: Windows system files or update components seem damaged

Microsoft's current Windows 11 guidance gives the straightforward repair sequence: run DISM RestoreHealth first, then run SFC /scannow. The order matters because DISM repairs the underlying Windows image components that SFC can depend on. The steps below apply to an online Windows installation that still boots normally; they are not commands for an offline installation image.

1. Open an elevated Command Prompt

Save your work, close applications you do not need, and connect a laptop to power. From Start, search for Command Prompt, right-click it and choose Run as administrator. Approve the User Account Control prompt. Do not run unfamiliar command batches copied from a forum; use the two commands below as written.

2. Repair the component store

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for the process to complete. It may appear slow at some stages. Do not interrupt it just because progress pauses. By default DISM can obtain required repair files using Windows Update; an enterprise policy may supply another source. Microsoft's SFC support article documents this behaviour and explains that a different repair source can be specified when necessary.

Do not copy the example path from an online tutorial's /Source option unless that exact location exists and contains suitable repair files. If DISM says source files could not be found, record the full error and follow Microsoft's repair-source guidance or your organisation's IT instructions. Repeating the identical failing command does not create missing files.

3. Check protected system files

After DISM completes successfully, run:

sfc /scannow

Leave the window open until verification reaches 100%. Microsoft documents several outcomes: it may find no integrity violations, repair files successfully, report that it could not perform the requested operation, or identify corrupted files it could not repair. These are different results and deserve different responses.

If SFC repairs files, restart Windows and repeat the exact symptom that led you here. The repair message establishes that protected files were replaced; it does not prove that the crashing application or failed Windows feature now works. If SFC reports no integrity violations and the symptom remains, move on to another diagnosis instead of repeating SFC indefinitely.

If SFC cannot fix some files, use the recorded result and Microsoft's CBS log inspection instructions before deciding on further recovery. Manual replacement of protected Windows files and ownership changes are advanced interventions, not an ordinary next click.

4. If you want to inspect the Windows image first

You may see DISM commands named /CheckHealth and /ScanHealth. These are diagnostic options, whereas /RestoreHealth attempts repair. The Windows image documentation distinguishes the quick recorded-state check from the more thorough scan:

DISM.exe /Online /Cleanup-Image /CheckHealth
DISM.exe /Online /Cleanup-Image /ScanHealth

These checks can help when you are collecting evidence for support. They do not replace the repair sequence when corruption has been identified. Do not infer that an apparently successful DISM check proves every protected Windows file is intact; that is why the SFC stage remains separate.

Route B: Windows reports a file-system error on a drive

CHKDSK is the relevant tool for file-system metadata and volume-structure problems. It is not an alternative spelling of SFC, and it does not reconstruct a damaged personal document or repair the Windows component store.

Identify the affected volume first. The examples here use C:, but only substitute that letter if you know it is the volume you intend to check. An external drive may use a different letter. If that drive holds irreplaceable data or has hardware-health warnings, save or recover its contents before a write-capable repair. Avoid running several repair options just because they appear in a command collection.

For a Windows NTFS volume, Microsoft documents the online scan option:

chkdsk C: /scan

The /scan option is NTFS-specific. It checks the volume while it is online, and its result should guide what happens next. This is not a data-recovery command or a guarantee that hardware is healthy. Read the complete result rather than assuming a quick return means no issue existed.

Do not jump straight to /f, /r or /x

/f attempts to correct file-system errors and requires a lock on the volume. If Windows cannot lock a volume in use, it can offer to schedule checking at the next restart. Read that prompt carefully, save work and plan the restart rather than forcing it during a critical task.

/r adds a search for bad sectors and attempts to recover readable information; it includes /f. That is substantially more work and is not the default way to check a routine Windows error. /x can force a dismount, invalidating open handles; it is not an innocuous speed switch. Microsoft's CHKDSK parameter reference makes these distinctions explicitly.

For a deteriorating disk, a long repair attempt can consume time that is better used securing a backup or professional recovery. If you have a clear file-system corruption report, protected your data and can tolerate downtime, follow the exact repair recommendation for that volume. Avoid turning a single error into a blanket instruction to run CHKDSK /r on every drive.

Where to read a CHKDSK result after restart

A scan scheduled for boot may finish before you can read all its on-screen text. Microsoft's CHKDSK documentation gives an Event Viewer route: open Event Viewer → Windows Logs → Application, then filter for the Chkdsk and Wininit event sources. Read the entry that matches the time of your scan. Its findings are more informative than a vague memory that the repair “ran.”

If a check repeatedly finds new problems, the same volume becomes inaccessible, or files keep disappearing, stop treating the tool as a permanent cure. Preserve data and investigate the underlying drive, controller, cabling or system stability, using hardware diagnostics appropriate to the device.

Worked decision example: one symptom, three possible branches

Suppose a Windows 11 laptop begins showing errors after a forced power-off. You should not assume the sudden shutdown proves one repair tool is correct.

Case A: Windows Update and built-in Windows features fail, while personal files are readable and the drive reports no health warning. Record the exact update error, make sure you have a backup, then consider Microsoft's DISM-then-SFC procedure. Verify by retrying the same update or Windows feature after restarting.

Case B: Opening folders on an external NTFS drive produces file-system errors, while Windows and other drives behave normally. Identify the actual drive letter, protect the recoverable files, then examine the volume with CHKDSK as appropriate. An SFC repair of C: is not a direct test of that external volume.

Case C: Windows displays a critical SSD reliability warning, or the drive repeatedly disappears. The immediate priority is preserving data and checking the device's hardware health, not treating a clean SFC result as a storage diagnosis. A logical file-system check cannot certify that the storage hardware is dependable.

The useful test is whether the action addresses the failing *layer* and whether the original symptom improves. Merely seeing a reassuring completion message is not enough.

What if both DISM and SFC complete but Windows is still broken?

Do not assume that every remaining problem is corruption. A driver regression, incompatible application, hardware fault, user profile problem or failed service can produce similar symptoms. Review the exact error and the change that preceded it.

If Windows itself remains affected, Microsoft documents Settings → System → Recovery → Fix problems using Windows Update → Reinstall now on supported Windows 11 configurations. That repair reinstall reinstalls the current Windows version while preserving apps, files and settings according to Microsoft. It still requires a reliable backup and sufficient time, power and connectivity. The option's availability can vary by device and management policy.

That is different from resetting or performing a clean installation, which may remove apps, settings or personal files depending on the chosen route. Compare the consequences in Microsoft's recovery-options guide before proceeding.

If the fault began after a specific system change and a suitable restore point exists, System Restore can be another route. The goal is to choose a documented repair that matches the event, not to keep adding commands to a generic checklist.

The practical stopping rule

Use DISM followed by SFC for suspected protected Windows-file or component-store damage; use CHKDSK for evidenced volume file-system faults; use hardware diagnostics and backups when a drive may be failing. Write down the initial symptom, each command's final result and the outcome of one matching retest.

If the error persists after the relevant tool completes, preserve that evidence and change the investigation. Running a different repair tool solely because the first one did not help can create new risk without answering a new question.

Sources

1. Microsoft Support — Using System File Checker in Windows. 2. Microsoft Support — DISM, SFC results and CBS log inspection. 3. Microsoft Learn — Repair a Windows Image. 4. Microsoft Learn — CHKDSK reference, switches and logs. 5. Microsoft Support — Windows 11 repair reinstall. 6. Microsoft Support — Windows recovery options.