STEP-BY-STEP GUIDE

Repair Corrupted Windows System Files with DISM and SFC

What to do first

Complete DISM at an administrator command prompt and then run SFC.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product
Windows
Versions and conditions
Windows 11 / Windows 10
Error codes and identifiers
DISMSFC0x800F081F0x80073712

Symptoms

  • Windows functions do not work
  • System errors, freezes, and update failures continue

Causes and conditions

The likely cause is missing or corrupted protected system files or component stores.

Before you start

  • Apply Windows Updates and restart
  • Connect to AC power and do not interrupt processing

Precautions

  • Back up important files in advance
  • Check the impact before deleting, initializing, or resetting the network.

Tools and official pages used in this guide

Windows troubleshooting sequence: Open the administrator screen; Run DISM; Run SFC; Judging the results
Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

  1. 01

    Open the administrator screen

    #

    Search for ``Command Prompt,'' right-click, and select ``Run as administrator.''

    Select Yes to confirm User Account Control. If you need administrator authentication and are unsure, ask your administrator before proceeding.

    Make sure it has "Administrator" in the title and maintain power and internet during the process.

    Check before continuing

    Verdict: Search for ``Command Prompt,'' right-click, and select ``Run as administrator.'' Select Yes to confirm User Account Control. If you need administrator authentication and are unsure, ask your administrator before proceeding.

  2. 02

    Run DISM

    #

    Run DISM.exe /Online /Cleanup-image /Restorehealth and keep the window open until the command completes.

    This may take several minutes. Confirm the successful completion message before proceeding to the next step, and if you receive an error such as a source file not being found, record the code.

    Check for either "The operation completed successfully", a restart request, or an error code when the command finishes. If it fails, do not repeat the operation and save the display code and C:\Windows\Logs\DISM\dism.log.

    Even if RestoreHealth progress appears to have stalled, keep the window open and wait for a specific error such as exit code 0 or 0x800f081f.

    Command or path
    DISM.exe /Online /Cleanup-image /Restorehealth
    Check before continuing

    Verdict: Run DISM.exe /Online /Cleanup-image /Restorehealth and keep the window open until the command completes. This may take several minutes. Confirm the successful completion message before proceeding to the next step, and if you receive an error such as a source file not being found, record the code.

  3. 03

    Run SFC

    #

    Run sfc /scannow and wait until verification is 100%.

    After DISM completes successfully, run SFC and do not restart until the final message "Verification 100% completed" appears.

    Command or path
    sfc /scannow
    Check before continuing

    Verdict: Run sfc /scannow and wait until verification is 100%. After DISM completes successfully, run SFC and do not restart until the final message "Verification 100% completed" appears.

  4. 04

    Judging the results

    #

    If SFC reports no integrity violations or successfully repairs the files, restart. If Windows cannot repair the files, preserve the results and CBS log.

    Save the result by copying the last message on the command screen. The log is located at C:\Windows\Logs\CBS\CBS.log. Even if there are no integrity violations, not all app defects have been ruled out.

    If SFC reports no integrity violations, system-file corruption is less likely. If repairs complete successfully, reboot and check the original symptom, and if some parts cannot be repaired, save CBS.log.

    Check before continuing

    Judgment: If SFC reports no integrity violations or successfully repairs the files, restart. If Windows cannot repair the files, preserve the results and CBS log. Save the result by copying the last message on the command screen. The log is located at C:\Windows\Logs\CBS\CBS.log. Even if there are no integrity violations, not all app defects have been ruled out.

Check the result

  • DISM completes with "The restore operation completed successfully" equivalent
  • SFC shows no integrity violations or successfully repaired corrupted files
  • Retest the original function/update once after restarting

If the problem continues

  • Retry in safe mode if SFC cannot perform requested operation
  • If DISM cannot retrieve the repair source, save the error code and ask your administrator to specify your organization's update source or Microsoft repair source.
  • If Windows cannot repair the files, check whether reinstallation is possible using Windows Update in [Settings] > [System] > [Recovery]

Scope of this guide

Troubleshooting guide — General diagnostic procedures. It does not describe a specific current incident.

Frequently asked questions

Which comes first, DISM or SFC?

DISM repairs the component store used for recovery; run SFC after DISM completes successfully.

It looks like it stopped in the middle.

The progress rate may not change for a long time. Keep AC power on and don't close the window until the completion message.

Official sources and dates

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides