Read CBS.log after SFC

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 reports corruption but the summary is too generic
2. Run the primary repair line exactly as shown: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" notepad "%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 the analysis step after SFC so you can verify what happened instead of relying on a vague summary line.

• SFC reports corruption but the summary is too generic.
• You want to know which file paths or repair actions were involved.
• The full CBS.log is too large to inspect comfortably.

How the command works

findstr filters the CBS log down to lines tagged for System File Checker activity, and then Notepad opens the smaller export for review.

When it makes sense to run it

Use it right after an SFC scan when you need evidence before choosing another repair step.

Before you run this command

• Open an elevated Command Prompt or PowerShell window before running findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" notepad "%userprofile%\Desktop\sfcdetails.txt".
• Confirm that the symptom really matches this guide, especially if you are seeing signs such as: sfc reports corruption but the summary is too generic.
• 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 findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" notepad "%userprofile%\Desktop\sfcdetails.txt", compare the result against the symptom that brought you here. The most useful checkpoint is whether sfc reports corruption but the summary is too generic 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 findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" notepad "%userprofile%\Desktop\sfcdetails.txt" is to repeat the action that previously triggered the problem. If you want to know which file paths or repair actions were involved 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

The exported text still needs interpretation. Some log lines are informational and do not always mean the system is still broken.

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 findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt" notepad "%userprofile%\Desktop\sfcdetails.txt" does not improve sfc reports corruption but the summary is too generic, 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.