SFC Corrupt files

Britton30 · 06 Oct 2013

I have again corrupt files SFC can't fix after 3+ attempts with reboots in between. System restore won't work. Here's is the cbs.log.

Attachment 288641

tom982 · 07 Oct 2013

Hi Gary,

Running SFC 3 times to fix corruption is actually an urban myth and has no real benefit :) Twice is very rarely necessary, but the third run is excessive. If there is a file SFC can use as a replacement (from winsxs), then it will either perform the replacement or pend it to be done over a reboot if the file is in use. If there's no suitable replacement, then it doesn't matter how many times you run SFC, it won't fix it because there's simply not a file there.

Just the one file to repair!

Code:

2013-10-06 19:49:54, Info                  CSI    00000318 [SR] Repairing 1 components
2013-10-06 19:49:54, Info                  CSI    00000319 [SR] Beginning Verify and Repair transaction
2013-10-06 19:49:54, Info                  CSI    0000031a Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-explorer.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6c3c2316c1b39396\explorer.exe.mui do not match actual file [l:32{16}]"explorer.exe.mui" :
  Found: {l:32 b:TMUUp9mvrnY83SGTLucirkp4fJaLq5ccOx0wBEFRz+M=} Expected: {l:32 b:Dj02THUxW5qR3U7HehFKqlQgLmDKILSIheIz7uyXktA=}
2013-10-06 19:49:54, Info                  CSI    0000031b [SR] Cannot repair member file [l:32{16}]"explorer.exe.mui" of Microsoft-Windows-explorer.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-06 19:49:54, Info                  CSI    0000031c Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-explorer.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6c3c2316c1b39396\explorer.exe.mui do not match actual file [l:32{16}]"explorer.exe.mui" :
  Found: {l:32 b:TMUUp9mvrnY83SGTLucirkp4fJaLq5ccOx0wBEFRz+M=} Expected: {l:32 b:Dj02THUxW5qR3U7HehFKqlQgLmDKILSIheIz7uyXktA=}
2013-10-06 19:49:54, Info                  CSI    0000031d [SR] Cannot repair member file [l:32{16}]"explorer.exe.mui" of Microsoft-Windows-explorer.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-06 19:49:54, Info                  CSI    0000031e [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"

Strangely, this is exactly the same as your last problem, so we can just use the last fix again:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/...n30/SFCFix.zip

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

Britton30 · 07 Oct 2013

Well I think you did it again Tom. I edited my name in the SFCfix.txt.

Thank you and niemiro so very much.

Attachment 288725

Code:

SFCFix version 1.5.7.0 by niemiro.
Start time: 2013-10-07 18:06:32.965
Using .zip script file at K:\Users\Username\Desktop\SFCFix.zip
 
 
PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\wow64_microsoft-windows-explorer.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6c3c2316c1b39396\explorer.exe.mui
Successfully took permissions for file or folder C:\Windows\en-US\explorer.exe.mui
Successfully copied file \\?\C:\Users\GlBritton\AppData\Local\niemiro\Archive\explorer.exe.mui to \\?\C:\Windows\WinSxS\wow64_microsoft-windows-explorer.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6c3c2316c1b39396\explorer.exe.mui.
Successfully copied file \\?\C:\Users\GlBritton\AppData\Local\niemiro\Archive\explorer.exe.mui to \\?\C:\Windows\en-US\explorer.exe.mui.
Successfully restored ownership for C:\Windows\WinSxS\wow64_microsoft-windows-explorer.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6c3c2316c1b39396\explorer.exe.mui
Successfully restored permissions on C:\Windows\WinSxS\wow64_microsoft-windows-explorer.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6c3c2316c1b39396\explorer.exe.mui
Successfully restored ownership for C:\Windows\en-US\explorer.exe.mui
Successfully restored permissions on C:\Windows\en-US\explorer.exe.mui
PowerCopy:: directive completed successfully.
 
 
Successfully processed all directives.
SFCFix version 1.5.7.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2013-10-07 18:06:33.090
----------------------EOF-----------------------

I was fine until I run a script that was supposed to find and delete superseded Windows Updates. It is listed and discussed here: A step-by-step project for a patient meddler - cleanup Windows 7 image

tom982 · 07 Oct 2013

My pleasure! I'll pass on your appreciation to Richard :)

Hmm, I saw that thread last week but I'm still not sure what to think about it, I have no need for the disk space so I won't be running it myself, but I'll look into it and get back to you if I find anything useful.

Tom

Britton30 · 07 Oct 2013

I didn't really need the space, a science experiment. But I figure the updates would be on my C:\ drice which is an SSD.
Again thank you and Richard.

Layback Bear · 07 Oct 2013

I also saw that thread.
A step-by-step project for a patient meddler - cleanup Windows 7 image
Now I glad I didn't use the suggestions.

Britton30 · 11 Oct 2013

It happened again. SFC first failed, then said I had corrupt files.
Maybe related, IE10 stops working often, NVidia display driver stopped and recovered. I got a Windows message saying Windows search stopped, but I wasn't using it.

Attachment 289269

grits · 11 Oct 2013

"Running SFC 3 times to fix corruption is actually an urban myth and has no real benefit :) Twice is very rarely necessary, but the third run is excessive. If there is a file SFC can use as a replacement (from winsxs), then it will either perform the replacement or pend it to be done over a reboot if the file is in use. If there's no suitable replacement, then it doesn't matter how many times you run SFC, it won't fix it because there's simply not a file there" ( quoting Tom)

This is the first & only time I've ever seen that. Every post advising someone to run SFC has always said to run 3 times. I only did the 'inquire' option myself onetime so I'm not speaking from experience, just curious as to why it's always suggested to run 3 times.

Britton30 · 11 Oct 2013

Thanks, Tom said that is post#2.

Tom, now the sfc come back with no integrity violations. I'd like to know what the log says when you have time. Well, I know what it says, but it's in Klingon.

tom982 · 11 Oct 2013

Tom, now the sfc come back with no integrity violations. I'd like to know what the log says when you have time. Well, I know what it says, but it's in Klingon.

SFC is detecting no problems now!? Your last run detected three corrupt files and showed no sign that it repaired them, I'm confused

Code:

2013-10-11 16:56:11, Info                  CSI    00000371 [SR] Repairing 32 (0x0000000000000020) components
2013-10-11 16:56:11, Info                  CSI    00000372 [SR] Beginning Verify and Repair transaction
2013-10-11 16:56:11, Info                  CSI    00000373 Hashes for file member \SystemRoot\WinSxS\amd64_averfx2hbtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_2973b7e011e9c731\MVDetection64.ax do not match actual file [l:32{16}]"MVDetection64.ax" :
  Found: {l:32 b:yQsDp01wdDTIKgf4TKhp1Sq5W3LelIfHeM5C88AeP40=} Expected: {l:32 b:sqJ0WSGZkIXJ3zbXQOvJLpHzSBTPawkZf7Wrv9asdes=}
2013-10-11 16:56:11, Info                  CSI    00000374 [SR] Cannot repair member file [l:32{16}]"MVDetection64.ax" of averfx2hbtv_x64.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-11 16:56:11, Info                  CSI    00000375 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-b..core-fonts-cht-boot_31bf3856ad364e35_6.1.7600.16385_none_1a0b146e42cd86a8\cht_boot.ttf do not match actual file [l:24{12}]"cht_boot.ttf" :
  Found: {l:32 b:kohWsz75D0EVOtIxda4+cLyTSkzZO5DMjr0AYK+/Chk=} Expected: {l:32 b:cT6pzfiKFBufX+mDr+cpb/YHSfk0Zj1aK2LLSar3vhI=}
2013-10-11 16:56:11, Info                  CSI    00000376 [SR] Cannot repair member file [l:24{12}]"cht_boot.ttf" of Microsoft-Windows-BootEnvironment-Core-Fonts-CHT-Boot, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-11 16:56:12, Info                  CSI    00000377 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.2.9200.16721_none_c1ed866c2e354c5b\jscript9.dll do not match actual file [l:24{12}]"jscript9.dll" :
  Found: {l:32 b:BbwVqAB9L+LsY73llj5gGi8nj8r99szl+L3K6Y/yoao=} Expected: {l:32 b:saWfpiJEBL1x9eFXeu2cgTbqIc6e3hJJbQhhgHe/QiQ=}
2013-10-11 16:56:12, Info                  CSI    00000378 [SR] Cannot repair member file [l:24{12}]"jscript9.dll" of Microsoft-Windows-Scripting-JScript9, Version = 10.2.9200.16721, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-10-11 16:56:12, Info                  CSI    00000379 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_10.2.9200.16721_none_c1ed866c2e354c5b\jscript9.dll do not match actual file [l:24{12}]"jscript9.dll" :
  Found: {l:32 b:k62MS/vUw28/5X8ctO7240gO2wp2tdO0urgll1W5ALg=} Expected: {l:32 b:saWfpiJEBL1x9eFXeu2cgTbqIc6e3hJJbQhhgHe/QiQ=}
2013-10-11 16:56:12, Info                  CSI    0000037a [SR] Cannot repair member file [l:24{12}]"jscript9.dll" of Microsoft-Windows-Scripting-JScript9, Version = 10.2.9200.16721, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

grits said:

"Running SFC 3 times to fix corruption is actually an urban myth and has no real benefit :) Twice is very rarely necessary, but the third run is excessive. If there is a file SFC can use as a replacement (from winsxs), then it will either perform the replacement or pend it to be done over a reboot if the file is in use. If there's no suitable replacement, then it doesn't matter how many times you run SFC, it won't fix it because there's simply not a file there" ( quoting Tom)

This is the first & only time I've ever seen that. Every post advising someone to run SFC has always said to run 3 times. I only did the 'inquire' option myself onetime so I'm not speaking from experience, just curious as to why it's always suggested to run 3 times.

I'm still not quite sure how it all started, but most members here will suggest three SFC runs and I can only assume that it's something they have picked up off others and has been passed on. It does no harm, it's just a waste of time :) I explained why in my post that you quoted.