SFC found corrupt files but could not fix some of them

Best place to run it

Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.

Fast repair workflow

1. Start from the exact symptom on this page: SFC finishes and reports it could not fix some files
2. Run the primary repair line exactly as shown: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt".
3. This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
4. Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
5. Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.

Copyable wrapper script

Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.

Verification commands after the repair

These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.

What problem this command is trying to solve

This page targets partial SFC repair failure rather than total scan failure. The system may be repairable, but the underlying component source is not healthy enough yet.

• SFC finishes and reports it could not fix some files.
• The system still behaves strangely after the scan.
• The CBS log usually contains the details of what SFC could not repair.

How the command works

DISM repairs the component store first, SFC retries the file repair, and the findstr command exports the most useful CBS log lines to a simpler text file.

When it makes sense to run it

Use this sequence when you need to go beyond the basic SFC result and confirm exactly what remains damaged.

Before you run this command

• Open an elevated Command Prompt or PowerShell window before running DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt".
• Confirm that the symptom really matches this guide, especially if you are seeing signs such as: sfc finishes and reports it could not fix some files.
• Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.

What result to expect

After running DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt", compare the result against the symptom that brought you here. The most useful checkpoint is whether sfc finishes and reports it could not fix some files becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.

How to verify that it worked

The best verification step after DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" is to repeat the action that previously triggered the problem. If the system still behaves strangely after the scan still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.

Why administrator rights matter here

This command changes system integrity and component corruption. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.

Before you run it

Do not assume every CBS entry points to a major issue. Review the exported details instead of guessing from one message.

When this is probably the wrong fix

This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.

What to do if it does not help

If DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" does not improve sfc finishes and reports it could not fix some files, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about system integrity and component corruption.