Can this SFC report tell me anything about a corrupted-file-fix operation?

Ghot · Mar 27, 2024

_william said:
Also, I think your profile pic is of the nano-sized man who sits inside my cpu oiling its cogs, maybe I could expedite all this if I could just talk to him.

Nano-sized man: "Crackle, spark, electron this, proton that".

x BlueRobot · Mar 27, 2024

Please do not filter CBS log files despite what others may say, usually the actual issue isn't on a line which is prefixed with "[SR]", more often than not, it will be a few lines prefixed with "Info" or "Error".

Everyone seems to grossly oversimplify the CBS log by suggesting to just filter it down to the [SR] lines, here's a good example of why you shouldn't do that: Troubleshooting 0x800f081f / 0x800f0982 Error

_william · Mar 27, 2024

Ghot said:
Nano-sized man: "Crackle, spark, electron this, proton that".

View attachment 91688

I've got it! He needs offerings of Nestle cereal--the answer was so simple after all!

Ghot · Mar 27, 2024

_william said:
I've got it! He needs offerings of Nestle cereal--the answer was so simple after all!

I knew that "snap, crackle, pop" would generate something along those lines.

Pssst... it's Kelloggs cereal. Namely, Rice Krispies.

_william · Mar 27, 2024

@x BlueRobot Thanks. I'm becoming pretty overwhelmed with it all honestly. I guess I'm lucky then as because chance had it that I actually extracted the lines the SFC command made in that big log file manually, so if there's anything of import in that TXT file I shared then I won't have missed it I guess.

_william · Mar 27, 2024

Ghot said:
I knew that "snap, crackle, pop" would generate something along those lines.

I guess then that I should crush the R. Krispies into a dust and allow the fan on the laptop's underside to inhale it. But which usb-port--or hdmi?--should I siphon the milk into? or does he prefer his cereal dry? Please advise.

Ghot · Mar 27, 2024

_william said:
I guess then that I should crush the dry cereal into a dust and allow the fan on the laptop's underside to inhale it. But which port should I siphon the milk into? or does he prefer his cereal dry? Please advise.

Just run sfc /scannow for the answer. It'll be in the CBS log.

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

_william · Mar 27, 2024

Ghot said:
Just run sfc /scannow for the answer. It'll be in the CBS log.

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

Ah ofc! Brill. I'll report back tomorrow with the result.

Try3 · Mar 27, 2024

x BlueRobot said:
Please do not filter CBS log files despite what others may say, usually the actual issue isn't on a line which is prefixed with "[SR]", more often than not, it will be a few lines prefixed with "Info" or "Error".

Everyone seems to grossly oversimplify the CBS log by suggesting to just filter it down to the [SR] lines, here's a good example of why you shouldn't do that: Troubleshooting 0x800f081f / 0x800f0982 Error

Please tell @Brink about it.
That's how the forum evolves.

All the best,
Denis

Try3 · Mar 27, 2024

x BlueRobot said:
Please do not filter CBS log files despite what others may say, usually the actual issue isn't on a line which is prefixed with "[SR]", more often than not, it will be a few lines prefixed with "Info" or "Error".

Everyone seems to grossly oversimplify the CBS log by suggesting to just filter it down to the [SR] lines, here's a good example of why you shouldn't do that: Troubleshooting 0x800f081f / 0x800f0982 Error

Your linked article is about a Dism-reported error not an error reported by SFC.

SysNative said:
Q: I've replaced the corrupted files identified by DISM/SFC but it still mentions that they're corrupt? Is my installation corrupt beyond repair?
A: No, fortunately this is often not the case and we can repair the operating system after further investigation. The reason the error often persists is due to registry corruption or the servicing stack is expecting an uncompressed file where you replaced it with a compressed file or vice-versa.

If SFC had reported an error that it could not fix then the SFC tutorial would have advised running a particular Dism command whilst online so that Dism could have made use of WU mechanisms to find replacement files.
This is explained in Option 1 Step 3 yellow notes.

I hope this helps,
Denis

Try3 · Mar 27, 2024

_william said:
Ah ofc! Brill. I'll report back tomorrow with the result.

But you've already done that.
I thought you said that SFC did not report any irreparable errors anyway.

Denis

_william · Mar 27, 2024

Try3 said:
But you've already done that.
I thought you said that SFC did not report any irreparable errors anyway.

Denis

Lol no, we were joking about cereal by that point, I wasn't referring to anything to do with the problem when I said that.

Ghot · Mar 27, 2024

Generally, things should proceed like this. The steps below are for problems from very mild, to very horrible.

1. sfc /scannow
2. Dism /Online /Cleanup-Image /RestoreHealth
3. In-Place Upgrade
4. Clean Install

Reboot and run sfc /scannow each time, after steps: 2, 3, and 4.
You won't need to go to the next step, if SFC comes up with no errors.

Try3 · Mar 27, 2024

Ghot said:
Generally, things should proceed like this...

1. sfc /scannow
2. Dism /Online /Cleanup-Image /RestoreHealth
3. In-Place Upgrade
4. Clean Install

Run sfc /scannow each time, after steps: 2, 3, and 4.
You won't need to go to the next step, if SFC comes up with no errors.

But you'll often find that you'll need no more than
SFC /ScanNow
and, if that reports irreparable errors, run the Dism command suggested in the SFC tutorial's Option 1 Step 3 yellow notes whilst connected to the internet.

All the best,
Denis

Ghot · Mar 27, 2024

Try3 said:
But you'll often find that you'll need no more than

Yep, yep... as soon as SFC comes up clean, you can stop proceeding through the four choices.

As mentioned a few times in this topic... all this info can be found in the SFC tutorial.
But to transfer the information from the tutorial to your head... you have to "read" the tutorial.

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

All four steps I mentioned above, are in a giant BLUE (color is really... TEAL), box in the SFC tutorial...

Maxstar · Mar 27, 2024

Filtering a CBS log

Try3 said:
If SFC had reported an error that it could not fix (...)

SFC reported an error, and in this case SFC was able to repair the issue. But because the CBS log was filtered it does not show the additional information about the corrupted file. When looking at the full CBS log it will show which file has been used as replacement, probably a file from the WinSxS directory. But when you filter the log you will miss such info.

Rich (BB code):

2024-03-25 03:35:25, Info                  DEPLOY [Pnp] Corrupt file: C:\Windows\System32\drivers\bthmodem.sys
2024-03-25 03:35:25, Info                  DEPLOY [Pnp] Repaired file: C:\Windows\System32\drivers\bthmodem.sys

_william · Mar 27, 2024

Ghot said:
But to transfer the information from the tutorial to your head... you have to "read" the tutorial.

Thanks for reminding me, I often miss that part.

x BlueRobot · Mar 27, 2024

Try3 said:
Please tell @Brink about it.
That's how the forum evolves.

I have before and it just got dismissed.

Try3 said:
If SFC had reported an error that it could not fix then the SFC tutorial would have advised running a particular Dism command whilst online so that Dism could have made use of WU mechanisms to find replacement files.

You've missed the point of that Q&A, sometimes even if you use DISM with a specified source, it will still report the file as corrupted, even though it isn't. That is when you need to investigate further.

Try3 said:
Your linked article is about a Dism-reported error not an error reported by SFC.

The point being, as @Maxstar has demonstrated, filtering the CBS log either from DISM or SFC just removes lots of useful information.

Here's a good example from this forum: Win 11 - The component store is repairable.

_william · Mar 27, 2024

Maxstar said:
But because the CBS log was filtered

I don't know if it was though... because the file I shared were lines I extracted manually from the CBS log, I didn't create that file with the standard command used for extracting the result of an SFC process; I literally remembered the time and date of when I ran "sfc /scannow" and just went to that part of the CBS log and took the 500 lines or so that seemed to pertain to it.