When Windows 11 reports operating system errors or behaves unpredictably, the built-in DISM and System File Checker tools can help identify and repair specific types of corruption. The following guide explains their correct order, results and limitations.
Understand What System File Corruption Means
Windows depends on operating system files and components that supply essential functions. If certain protected files are missing or damaged, a feature may fail to start, display an error or behave unpredictably. A failed update, interrupted servicing operation or an underlying storage problem can be associated with corruption. An application failure can also occur when Windows files are perfectly healthy.
System File Checker, commonly called SFC, checks protected system files. Deployment Image Servicing and Management, commonly called DISM, can inspect and repair the Windows image and its component store. These tools address related but distinct parts of the operating system. A healthy repair source matters because Windows needs suitable component files when repairing protected system files.
A successful repair does not automatically repair third-party applications, personal documents, damaged hardware, user profiles or every driver. Conversely, a clean system-file scan does not establish that nothing else is wrong with the computer. Use these tools when the symptoms or supporting diagnosis make corruption a reasonable possibility, then validate the original failure.
If Windows cannot boot normally, the recovery environment requires separate procedures. Do not assume that a command targeting the running system will repair a different Windows installation. Our Windows Startup Repair guide explains the purpose of the supported boot-recovery option.
Identify When SFC And DISM Are Appropriate
Consider system repair when Windows features fail unexpectedly, operating system components report errors or supported troubleshooting points toward damaged files. A Windows Update problem may also justify checking and repairing system components, particularly when the ordinary update troubleshooter or error information supports that direction.
Start with the simplest explanation that matches the symptom. A browser that crashes on one website may have a browser-specific issue. A printer showing offline may have a connection or spooler problem. A computer that is slow only while transferring files may be experiencing storage or network limits rather than damaged operating system components.
Write down the error message, which Windows function fails and the approximate time it began. Note any update, unexpected shutdown or application installation that occurred around the same time. Try to reproduce the failure safely using a normal task. For a persistent blue screen, record the stop code instead of relying on a general impression of instability; see our blue screen diagnosis guide.
Select a repair that corresponds to the evidence. If Windows Update reports a specific error, inspect Microsoft’s guidance for that error. If several built-in functions fail, a supported system repair may be useful. If the machine shows signs of disk failure, prioritize preserving data and obtaining storage diagnostics rather than repeatedly writing repair files to a potentially failing drive.
Microsoft’s system file repair documentation describes DISM and SFC as built-in operating system recovery tools. It is a better starting point than a third-party program advertising generic registry or DLL repair.
Prepare Your PC Before Repairing Windows
Save active documents and close applications that are performing important work. Make sure that valuable files have a current backup in a location you can actually access. Although the standard commands described here are not intended to erase personal files, troubleshooting a malfunctioning operating system is not a substitute for protecting your information against an unexpected failure.
If the device is encrypted, confirm that you can recover the appropriate BitLocker recovery key if later troubleshooting requires starting a recovery environment or making a relevant configuration change. Keep recovery information in an authorized secure location rather than posting it online. On a work or school PC, contact the responsible administrator if the device is managed or you do not have authorization to service it.
Connect a laptop to a reliable power source if appropriate. Make sure that Windows has enough available drive space for ordinary servicing work. If the computer is seriously unstable, loses power randomly or shows indications of hardware failure, preserve your data and seek appropriate service before initiating repairs that may require considerable uninterrupted activity.
Use an ordinary trusted internet connection for the default DISM repair process, which can obtain repair material through Windows Update under the applicable configuration. If your organization manages update sources, use its approved network and procedures. Do not change a work computer’s security policy merely to obtain repair files.
Read our Windows backup preparation guide for help with safeguarding data. If free storage is the immediate problem, follow the low-risk checks in our Windows storage cleanup article before starting an extensive repair.
Open An Elevated Command Prompt
The commands in this guide target a Windows 11 installation that can start normally. First open the Start menu and search for Command Prompt. Select the supported Run as administrator option and respond to the User Account Control request using an authorized administrator account.
Administrator access matters because the tools need permission to inspect or modify protected operating system components. A normal command window may reject a repair operation that requires elevation. If you do not have administrator privileges, do not attempt to bypass the computer’s account restrictions. Ask the person or organization responsible for the device.
You can use an elevated Windows Terminal session with an appropriate Command Prompt or PowerShell shell for the two main commands, but the examples that use environment-variable expansion and command redirection later in this guide are specifically written for Command Prompt. The syntax of other shells can differ. Copy each command individually and review it before pressing Enter.
The first command repairs the running Windows image. The second scans and repairs protected system files. Wait for the first operation to complete before starting the second; opening several simultaneous repair sessions can complicate diagnosis and interfere with normal servicing.
For introductory help with command windows and their output, see our command line guide. The commands below are built into Windows. There is no separate repair program to install or executable to download from an advertisement.
Step 1: Repair The Windows Component Store Using DISM
In the elevated Command Prompt, run the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealthThe Online option identifies the Windows operating system currently running on the computer. Cleanup-Image selects image servicing functions, and RestoreHealth asks DISM to scan for component-store corruption and perform appropriate repair operations. The word Online in this context identifies the running image; it is not a declaration that the machine has internet access.
The operation can take time, and displayed progress does not necessarily advance at a constant rate. Do not conclude immediately that the tool has failed simply because the percentage remains unchanged for a while. Keep the computer powered and allow the command to return a result. The necessary time depends on device performance, component state, servicing activity and the availability of repair sources.
Check the final message. If DISM reports successful completion, continue to the System File Checker step. If it returns an error, record the complete error code and accompanying description. Do not assume that entering the same command several times will overcome an unavailable repair source or an underlying storage problem.
Under ordinary default conditions, DISM can use Windows Update to obtain required components. Managed policies or a broken update path may affect source selection. The Microsoft Learn image repair documentation explains alternative repair-source options. Do not download individual Windows components from unknown websites when the default repair source fails.
Step 2: Scan And Repair Protected Files Using SFC
Once the DISM repair has completed successfully, run the following command in the elevated Command Prompt:
sfc /scannowSystem File Checker examines Windows files that are covered by Windows Resource Protection and attempts to replace damaged protected files with appropriate known-good versions. It does not examine every photograph, downloaded program or document on the computer. Its scope is why the order of operations matters: DISM can help repair the component material on which protected-file recovery depends.
Allow the verification to reach completion and read the final result. Do not close the command window merely because the progress indicator pauses. If Windows itself becomes unstable or the computer reports a serious hardware problem, record that situation and prioritize safe recovery.
Write down the result and whether any repair was reported. If the scan completes and repairs files, restart Windows when appropriate and reproduce the original failure. Check any Windows feature or update that motivated the repair. The tool’s result is evidence about protected files, not direct proof that all symptoms have disappeared.
If the command did not identify damaged files, avoid treating that outcome as a reason to repeat the same scan indefinitely. Investigate the narrower cause that matches the original problem. If the tool reports an unsuccessful repair or inability to complete the operation, use the appropriate branch below. Microsoft provides a concise System File Checker procedure with the DISM-first sequence.
Interpret The Four Common SFC Outcomes
An SFC result must be interpreted in relation to the symptom you are trying to resolve. A result indicating no detected integrity violation means that the scan did not find corruption among the protected files checked. It does not rule out problems with third-party programs, settings, drivers, hardware or the user profile.
A result indicating that damaged files were successfully repaired means that SFC corrected the problems it could identify during that operation. Restart as appropriate, retest the original behavior and keep a note of the result. If the failure is resolved and the computer is stable, there is generally no need to run repair commands repeatedly.
A result indicating that the requested scan could not be completed requires investigation of the circumstances that prevented verification. Check for a pending restart or servicing activity and consult Microsoft’s supported guidance. A safe-mode scan may be appropriate in certain situations. Do not delete servicing folders or change their permissions merely because a forum post suggests it.
If SFC detects corruption but cannot repair everything, retain the final message and inspect the relevant diagnostic entries. A failed DISM source or a more complex servicing problem may require attention. If the machine is managed, share the result with its administrator rather than performing a series of undocumented manual replacements.
These results provide different next actions. Use the exact reported wording to select the branch, rather than interpreting every result as an instruction to reset Windows. The same tool can report a clean scan on a malfunctioning machine or a successful file correction on a machine that has another independent fault.
| SFC Outcome | Recommended Next Action |
|---|---|
| No Integrity Problems Detected | Investigate The Original Symptom |
| Corruption Repaired | Restart And Retest |
| Verification Could Not Complete | Investigate Servicing State And Supported Recovery |
| Some Corruption Remains | Inspect Logs And Repair Source |
Use Optional DISM Health Checks Correctly
DISM also offers health inspection options for the Windows image. These are useful when you or a support professional want further context before attempting restoration. The following commands have different purposes and should not be treated as interchangeable names for the repair command.
DISM.exe /Online /Cleanup-Image /CheckHealth
DISM.exe /Online /Cleanup-Image /ScanHealthCheckHealth reports whether servicing has identified corruption and whether the image is considered repairable. It is not a comprehensive new scan of the entire computer. ScanHealth performs a more extensive component-store corruption check and may take longer. Neither option requests the same automatic repair operation as RestoreHealth.
If you are following the standard Microsoft-supported repair sequence described earlier, it is not necessary to run both inspection commands before every RestoreHealth operation. Use them when their diagnostic distinction is useful. For example, someone gathering evidence for support may run the scan and record its reported health state before selecting a repair.
If the tool identifies a non-repairable condition or cannot complete the scan, do not repeatedly change random servicing settings. Record the exact result, verify the computer’s stability and consult the appropriate recovery or support instructions. A specialist can determine whether an appropriate repair source, a supported Windows reinstall or another action is needed.
Microsoft’s Repair-WindowsImage documentation explains these health-operation distinctions for the corresponding Windows servicing capabilities. Use the documented syntax for the command-line interface you choose.
Troubleshoot DISM Source Errors Without Random Downloads
If RestoreHealth cannot obtain required repair content, determine whether the computer has access to its configured update service. A home PC may need a working internet connection to reach the ordinary Windows Update source. A managed PC may use an organization-approved update server or a policy that governs repair sources.
Record the error identifier and final description. Check the ordinary Windows Update screen for a related failure or a pending restart. Follow the Microsoft Windows Update troubleshooting guidance when the evidence points toward update components. Our Windows Update troubleshooting guide covers additional precautions.
An alternative repair source can be appropriate when the default source cannot supply suitable files. The source must provide the components needed by the actual Windows installation. Compatibility involves the installed operating system and relevant servicing requirements, not merely a folder named Windows. Obtain official media or an approved repair location and follow Microsoft’s source-selection documentation.
For example, the following is a template only, not a command that can be copied unchanged:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccessReplace the example location with a verified suitable repair source. LimitAccess prevents the online repair operation from using Windows Update as a source or fallback. For installation-image sources, the required syntax and image selection may differ. Do not guess an image index, borrow an unknown Windows folder or assume every installation image is compatible.
If you do not have an approved compatible source, stop at the recorded error and seek help rather than downloading random DLL files. An unsuitable replacement can introduce new corruption or security risks. Review Microsoft’s image-repair instructions and its linked repair-source guidance before using advanced source options.
Inspect Diagnostic Logs And Preserve Useful Evidence
System File Checker records details within Windows servicing logs. Viewing the relevant entries can help identify an unsuccessful repair or assist a support professional. A log may contain entries from earlier scans and other servicing activity, so pay attention to timestamps rather than assuming that every line refers to your latest command.
In an elevated Command Prompt, this example extracts lines containing the SFC marker from the Component-Based Servicing log into a file under your user profile:
findstr /c:"[SR]" "%windir%\Logs\CBS\CBS.log" > "%userprofile%\sfc-details.txt"Open the resulting sfc-details.txt file if the command completes successfully. Because the destination is within the user profile used by that command session, make sure you are checking the appropriate account’s folder. The extraction can include earlier SFC activity, and rotated logs may hold additional historical information. It is not a complete automatic diagnosis.
DISM diagnostic information is commonly available within the Windows Logs directory under DISM, including dism.log. Follow the relevant Microsoft support procedure when a repair returns an error. Record the complete code, time and command alongside any selected log material.
Do not delete CBS or DISM logs just to remove evidence of errors. Do not change ownership of protected operating system files merely because they appear in a report. If an entry identifies a component that cannot be repaired, seek an appropriate supported repair method.
Logs may reveal system paths, installed components and organization-specific details. Review diagnostic material and remove unnecessary sensitive information before sharing it through a public forum. If your organization manages the device, use its approved support channel.
Verify Windows After The Repair
Once the repair operations are complete and Windows has restarted normally when appropriate, test the exact feature that was failing. For example, open the built-in application that previously reported an operating system error, repeat the original settings change or attempt the Windows Update operation that motivated the repair.
Observe whether the issue recurs after another normal session. A successful SFC repair can coexist with a separate fault. If the original symptom is a third-party application crash, use that application’s supported troubleshooting options. If it occurs when a particular device is connected, inspect the appropriate driver and hardware information.
An optional subsequent SFC scan can be useful when you need to confirm the protected-file state after a reported repair. Do not use repeated clean scans as a daily maintenance plan. Running a repair command without a relevant fault or diagnostic reason is not a guarantee of improved performance.
If the original problem persists while DISM and SFC complete normally, identify the next branch rather than escalating automatically to a reset. Common branches include application-specific faults, storage problems, incompatible drivers, Windows Update issues and user-profile configuration. Our safe driver guide explains how to identify appropriate drivers without untrusted download tools.
Record the repair result alongside the original symptoms. This can help you avoid repeating a procedure that has already been performed and gives a support technician useful information. The real completion criterion is that the original required function works reliably, not simply that a command printed a success message.
Handle Recurring Corruption And Recovery Failures
Protected-file corruption that returns repeatedly after an apparently successful repair deserves a wider investigation. A failing storage device, repeated unexpected power interruptions or persistent servicing faults may contribute to recurring problems. The repair tools do not replace proper storage, memory or power diagnostics.
If you suspect storage failure, protect valuable information first and consult the device manufacturer’s supported diagnostics. Avoid repeatedly initiating write-intensive repair work on a drive that is making unusual noises, disappearing from the system or reporting serious hardware errors. The most important objective in that situation may be preserving data.
A PC that cannot start normally may require the Windows recovery environment. Drive-letter assignments and the location of the intended Windows image can differ there. A command with the Online option would target the running environment rather than automatically identifying the non-running installation. Offline servicing and protected-file verification require appropriate target paths, encryption access and a verified supported procedure.
For a Windows installation that starts but remains unusable after ordinary repairs, Microsoft provides supported recovery and reinstallation options. These have different implications for installed software, settings and personal files. Verify which option is available on the exact Windows version, obtain suitable backups and ensure account access before selecting it. If you cannot safely identify the target installation or repair source, ask qualified support.
Avoid unofficial scripts that delete component-store folders, replace protected system files wholesale or run registry cleaners as a general repair method. They can remove necessary servicing material and make future updates or recovery more difficult. A supported repair or reinstall is preferable to modifying protected components without a validated plan.
Frequently Asked Questions
Should I Run DISM Or SFC First?
Run the supported DISM RestoreHealth operation first, then run SFC after successful completion. Repairing component material can help SFC restore protected files.
Will SFC Delete My Personal Files?
SFC targets protected Windows system files rather than personal photos and documents. Maintain backups because an already malfunctioning computer can still fail unexpectedly.
Does DISM Online Mean I Must Be Connected To The Internet?
No, Online identifies the running Windows image. The default repair operation can require access to Windows Update unless a suitable alternative source is used.
Why Does DISM Progress Appear To Pause?
Servicing operations do not always advance at a constant rate. Allow the operation to finish and use its actual final status rather than guessing from a temporary pause.
Can SFC Fix A Failing SSD Or A Bad Driver?
No, its scope is protected system files. Hardware faults and device-specific drivers require their own diagnostics.
What If SFC Finds No Corruption But Windows Still Fails?
Investigate the original symptom, including applications, drivers, storage, configuration and updates. A clean scan is not a comprehensive health certificate.
Should I Download A Missing Windows DLL From A Repair Website?
No, use approved Windows servicing sources or official recovery procedures. Untrusted replacement files can introduce compatibility problems or malware.


