How to view details of the System File Checker process

Kol12 · Nov 28, 2021

I am trying to view the details of the System File Checker process. There is a MS support article on how to do so here: Use the System File Checker tool to repair missing or corrupted system files

When I run the command: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" I receive the error:

out-file : Could not find a part of the path 'C:\Users\MyUsername\%MYUsername%\Desktop\sfcdetails.txt'.
At line:1 char:1
+ findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%MyUsername%\Desktop\s ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: :)) [Out-File], DirectoryNotFoundException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

What is wrong with the command?

Ghot · Nov 28, 2021

The command itself looks OK. Did you use an elevated command prompt?

I just ran sfc /scannow and then ran this... (copy/paste from article)

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Use System File Checker (SFC) to Repair System Files in Windows 11 Tutorial

This tutorial will show you how to run the System File Checker (SFC) tool to repair missing, corrupted, and modified system files in Windows 10 and Windows 11. System File Checker (SFC) is a tool built into Windows that will check for system file corruption. The SFC /SCANNOW command scans and...

www.elevenforum.com

...and it worked OK for me. But I am on Windows 10 at the moment.

Bree · Nov 28, 2021

Kol12 said:
What is wrong with the command?

Nothing. Works perfectly for me...

That suggests the environment variable USERPROFILE you used in that command returns an incorrect value.

Open a command prompt and type the command SET USERPROFILE to see what value it returns. It should be C:\Users\MyUsername (or whatever your username really is).

zbook · Nov 28, 2021

See if you can run:
Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.
SFCfromFile.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Superfly · Nov 28, 2021

Kol12 said:
I am trying to view the details of the System File Checker process. There is a MS support article on how to do so here: Use the System File Checker tool to repair missing or corrupted system files

When I run the command: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" I receive the error:

out-file : Could not find a part of the path 'C:\Users\MyUsername\%MYUsername%\Desktop\sfcdetails.txt'.
At line:1 char:1
+ findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%MyUsername%\Desktop\s ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: :)) [Out-File], DirectoryNotFoundException
+ FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

What is wrong with the command?

It's a Cmd command (does that make sense? LOL)

The Powershell equivalent would be :

Code:

Select-String -Path (Join-Path $env:windir -ChildPath  "Logs\CBS\CBS.log") -SimpleMatch -Pattern "[SR]" |
Out-File (Join-Path $env:USERPROFILE -ChildPath  "Desktop\sfcdetails.txt")

Kol12 · Nov 28, 2021

I just get: The system cannot find the path specified. I get this for both user profiles on my machine.

Bree · Nov 28, 2021

Superfly said:
It's a Cmd command (does that make sense? LOL)

@Kol12 ran it in PowerShell when it should have be run in a Command Prompt. Well spotted. Running a CMD command in PowerShell rarely turns out well :lmao:

Kol12 · Nov 28, 2021

I ran it in Windows Terminal yes...

OK I ran it from Command Prompt in the admin account and it worked. So my question now is how can see what files were corrupted and repaired? All I see is: Beginning Verify and Repair transaction, Verify complete.

Superfly · Nov 28, 2021

Yep seems a bit useless TBH I also just have "Beginning Verify and Repair transaction" only - perhaps there are other strings we need to get?

(BTW: there was a space I had to remove from the PS command above so copy paste works w/o error)

Bree · Nov 28, 2021

Kol12 said:
All I see is: Beginning Verify and Repair transaction, Verify complete.

That means that no files were corrupt and had to be replaced from the component store. But there is another form of corruption that SFC may find and report that it fixed that doesn't get the "[SR]" tag, permissions that are set twice. To find if those were the errors SFC fixed, open the CBS.log itself in Notepad and search for the string 'twice'.

Kol12 · Nov 28, 2021

Superfly said:
Yep seems a bit useless TBH I also just have "Beginning Verify and Repair transaction" only - perhaps there are other strings we need to get?

(BTW: there was a space I had to remove from the PS command above so copy paste works w/o error)

Maybe it will only tell you what files are corrupted in the sfcdetails.txt if it can't repair them? I am wanting to see what files were corrupted anyway.

Kol12 · Nov 28, 2021

Bree said:
That means that no files were corrupt and had to be replaced from the component store. But there is another form of corruption that SFC may find and report that it fixed that doesn't get the "[SR]" tag, permissions that are set twice. To find if those were the errors SFC fixed, open the CBS.log itself in Notepad and search for the string 'twice'.

There is no "twice" in my CBS.log and all I have is "Beginning Verify and Repair transaction, Verify complete" in the sfcdetails.txt. However SFC /scannow found integrity violations and fixed them. Is there anything else in the CBS.log to look for?

Fabler2 · Nov 28, 2021

If there are corrupt files then I simply copy and paste 'C:\Windows\Logs\CBS\CBS.log' whether it's in PowerShell or CMD and it opens the log so I can save to desktop.

Superfly · Nov 28, 2021

OK, so I ran sfc /scannow and it found corruption

Ran the above command it lists the corrupted files under "Repairing file" - so not useless..

Kol12 · Nov 28, 2021

Superfly said:
OK, so I ran sfc /scannow and it found corruption
View attachment 14706

Ran the above command it lists the corrupted files under "Repairing file" - so not useless..

View attachment 14705

My sfcdetails.txt does not look like that. I only have the date and time. How did you get it to show the rest of the file path?

Superfly · Nov 28, 2021

Kol12 said:
My sfcdetails.txt does not look like that. I only have the date and time. How did you get it to show the rest of the file path?

Run the PowerShell script to get full details.

Kol12 · Nov 29, 2021

Superfly said:
Run the PowerShell script to get full details.

I got the full details with the PowerShell script but my log did not show any particular files that were repaired like yours. I wonder why it detected integrity violation in the first place.