Solved SFC /Scannow - Corrupted Files

[Peter2]

I am not a skilled user but wish to ask a question. I read as well as I could about DISM.
If I ran, as admin, and typed the following after the blinking cursor, would it help when SFC had failed?

run this; Dism /Online /Cleanup-Image /RestoreHealth then reboot.

 

[David Bailey]

I am not a skilled user but wish to ask a question. I read as well as I could about DISM.
If I ran, as admin, and typed the following after the blinking cursor, would it help when SFC had failed?

run this; Dism /Online /Cleanup-Image /RestoreHealth then reboot.

Yes, it would help.
Try it & post back.

Let sfc FINISH first !

Then run DISM :

Dism /Online /Cleanup-Image /RestoreHealth


Then reboot.
Then run sfc AGAIN !

 

[Saltgrass]

When sfc got to 100% it was NOT done.

You are correct, I had to leave SFC along for another 12 minutes before I got the Unable to Repair message.

After that, I checked the log and saw the following message.

Committing transaction
[SR] Cannot commit interactively, there are boot critical components being repaired
[SR] Repairing 11666 (0x0000000000002d92) components

So I rebooted and tried again...same message showed up in the next log and no files have yet been repaired, hence my comment about DISM vs SFC.

Two systems showing the same problem does not seem to be normal...I think something is going on, but uncertain as to what it might be. I will leave my current system without using DISM to repair it. If anyone has anything they would like to test, let me know.

If necessary, I will start a new thread about this .. the OP may not like the way the discussion is going.

 

[Peter2]

I hope I have not said something inappropriate. My system is finally stable only after a system recovery but I had an awful time with SFC reporting corrupted files.
I wish I had DISM when the trouble with SFC occurred.
Thank you

 

[tprothro1]

As for dism, please post the zipped \Windows\Logs\DISM\dism.log and \Windows\Logs\CBS\CBS.log just in case.

guess what? there's no dism.log file residing in my c:\windows\logs\dism\ folder, i'ts empty - also, a system search diesn't turn up the file either. fwiw i have show all system files and folders enabled. maybe this is the reason why /restorehealth reports "the component store corruption was repaired" even tho /checkhealth and /scanhealth report "no component store corruption detected."?

fwiw, my system is running great, actually i couldn't imagine it running any better, everything seems to work perfectly well, including the metro side...

 

[Brink]

Robert,

I'm happy to hear that it's all working fine now.

The Dism log can be in either log file below, so you might check the other to see if has anything if you like.

C:\Windows\Logs\CBS\CBS.log

C:\Windows\Logs\DISM\dism.log​

http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

 

[tprothro1]

Robert,

I'm happy to hear that it's all working fine now.

The Dism log can be in either log file below, so you might check the other to see if has anything if you like.

C:\Windows\Logs\CBS\CBS.log

C:\Windows\Logs\DISM\dism.log​

http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

the thing is, all was working perfectly fine before as well, the handful of corrupted files /scannow encountered was just bugging me more than anything else, it wasn't impacting my system's performance. nonetheless i'm glad /scannow is reporting a clean slate, thanks to your help.

re the dism.log: if the dism scan results were being written to the cbs.log file, wouldn't the cbs.log file's time stamp reflect when the dism scan was run? if that's the case, then i don't think the dism.log file is being written to the cbs.log file because the time stamp doesn't change.

 

[Brink]

Yep, the /scanhealth and /restorehealth switches logs to the C:\Windows\Logs\CBS\CBS.log file. I just happened to notice that it also logged to the C:\Windows\Logs\DISM\dism.log file for me as well.

Fixing component store corruption in Windows 8 and Windows Server 2012 - The Windows Servicing Guy - Site Home - TechNet Blogs

 

[Vadikan]

DISM won't repair corrupted system files. If /ScanHealth says it's OK, then DISM is not the way to go for repair, but SFC is.

Based on my experience, this statement does not appear to be accurate. Why it would not repair the OP's files eludes me, since the same links were shown in my sfcdetails.txt listing.

It may not appear to be accurate, but DISM's /RepairHealth and SFC still serve different purposes.

DISM's /RepairHealth (or CheckSUR) verify the component store integrity and fix corrupted manifests and metadata. You can see it in dism.log

Checking System Update Readiness.
 
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-lpksetup_31bf3856ad364e35_6.2.9200.16384_none_7a23086df63cad13
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_ru-ru_2422e0b40b0ac235
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_ru-ru_2a982e5d65c9a294
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_ru-ru_53ea2a36610cb913
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_ru-ru_879ccd7f3842e229
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_ru-ru_8e2bd9e9b9aeac5f
(p) CSI Manifest Corrupt    (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_ru-ru_c73545896a8993dd
 
Summary:
Operation: Detect and Repair 
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:  7
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    7
    CSI Metadata Corruption:    0
    CSI Payload Corruption: 0
Total Repaired Corruption:  7
    CBS Manifest Repaired:  0
    CSI Manifest Repaired:  7
    CSI Payload Repaired:   0
    CSI Store Metadata refreshed:   True
 
Total Operation Time: 221 seconds

When dealing with issues (especially, Windows Update ones), you should first verify the component store integrity with DISM (or CheckSUR in OS prior to Windows 8).

On the other hand, SFC repairs system files by verifying their signed hash. If the file hash doesn't match the hash in the component store, it restores the files (technically, they are hardlinks).

These tools are related, but they repair different things. It's not like "I have DISM, and I don't need SFC now". You may need both.

 

[Peter2]

Hello
Because I am not very techy I hope my previous post is accurate. If SFC reports corruption, then run DISM.
It has always worked for me. Dism /Online /Cleanup-Image /RestoreHealth
I am writing as I noticed some controversy.
tTank you
Peter

 

[popeye]

It means there is corruption in the Windows core store files, ie dll's that run basic functions. Your computer can seemingly be running fine but a corruption can cause anything to crash at anytime.

Run the sfc /scannow at least twice and see if it still reports unrepaired corruption. If still corruption, then run the DISM command: Dism /Online /Cleanup-Image /RestoreHealth

As shown here: http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

PS: Of course, you need to be connected to internet when you run it.

 

[rdwray]

It means there is corruption in the Windows core store files, ie dll's that run basic functions. Your computer can seemingly be running fine but a corruption can cause anything to crash at anytime.

Run the sfc /scannow at least twice and see if it still reports unrepaired corruption. If still corruption, then run the DISM command: Dism /Online /Cleanup-Image /RestoreHealth

As shown here: http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

PS: Of course, you need to be connected to internet when you run it.

Thanks, it worked and sfc says there is no corruption. I had 2 HDD that were clones and all 3 had to be scanned.