Built-in Windows repair commands are useful when protected system files may be damaged. They should produce evidence about a specific problem, rather than become a repeated ritual whenever any application behaves unexpectedly.

Before starting, preserve important work and note the failing action and exact error. If the drive is becoming unreadable or files repeatedly disappear, establish a storage and data-preservation plan first. System-file repair does not make unreliable hardware dependable.

Complete the stages in order

Microsoft’s Windows 11 guidance starts with Windows updates and a restart. Then search for Command Prompt and choose Run as administrator when authorised. Run:

DISM.exe /Online /Cleanup-image /Restorehealth

DISM supplies files used for repair and normally obtains the needed material through Windows Update. Allow time for it to start and finish. If it reports a source or other failure, preserve that result and resolve the cause; do not paste a placeholder repair-source path from an unrelated example.

After DISM reports successful completion, run:

sfc /scannow

Keep the window open until verification reaches 100 percent and the result appears. Starting the second command while the first is still unresolved obscures which stage actually succeeded.

Read the result before declaring the problem fixed

SFC distinguishes finding no integrity violations, repairing corrupt files, being unable to repair some files, and being unable to perform the operation. Record the actual outcome. Reaching the end of a scan is not the same as successfully repairing everything it found.

If you inspect SFC details from CBS.log, compare timestamps with the run you just completed. Microsoft notes that the extracted details can include earlier runs, so an old unrepaired entry may not describe the current result.

Repeat the original failing action after the appropriate restart or completion steps. Note whether the symptom persists, changes or disappears. A successful protected-file check does not test every application setting, peripheral or personal document.

Retain the command results and this functional comparison for further support. If corruption remains unresolved, continue with a diagnosed repair plan instead of replacing protected Windows files with downloads from an unknown source.

Sources: Microsoft System File Checker sequence; Microsoft detailed SFC results.