sfc can't repair some of the files

M

masterding

Member
Joined
Feb 8, 2015
Posts
14
After I ran sfc /scannow, I got this message "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log." I wrote the sfc related entries in cbs.log to sfcdetails.txt using "findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt", I found problematic entry in sfcdetails.txt
"2015-02-04 22:01:22, Info CSI 0000092c [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = 4.0.9600.16384, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing ",
I suspect it is related to .NET Framework . I tracked down 6 directories which I believe were system.resources.dll related under c:\windows\winsxs
608932

there's a system.resources.dll under every of these 6 directories.I open the first directory ,and found that size of the system.resources.dll is suspicious, I suspect it was corrupt. So I deleted the file ,and also I deleted the 4th directory which I believe might be relevant because the number in the name of the directory is somewhat consistent with the system.resources.dll version number provided by sfcdetails.txt . After that I ran DISM /Online /Cleanup-Image /RestoreHealth , the file and directory I deleted was recovered successfully, then I ran sfc /scannow ,now there're two problematic entries in sfcdetails.txt :
2015-02-08 20:29:05, Info CSI 0000123f [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = 4.0.9600.16384, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-02-08 20:29:05, Info CSI 00001242 [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = 4.0.9600.16404, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
The first problem persists ,and now there's this second problematic entry ,what does it tell?
My OS is win 8.1 update 1
 
Hello and welcome to the forum :)

To start of with, it is never a good idea to just look at sfcdetials.txt as this cuts of so much important information that is normally crucial to knowing what the exact issue is.

In the case here you have two diffrent errors in two different folders:

Code: 
2015-02-08 20:29:05, Info CSI 0000123f [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = [COLOR="#0000FF"]4.0.9600.16384[/COLOR], pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, [COLOR="#FF0000"]file is missing[/COLOR]

Code: 
You may have to scroll across to view it all. The part in red is the actual error System.resources.dll is missing. The part in blue shows the version number associated to the folder found inside WinSxS.
2015-02-08 20:29:05, Info CSI 00001242 [SR] Cannot repair member file [l:40{20}]"System.resources.dll" of System.resources, Version = [COLOR="#0000FF"]4.0.9600.16404[/COLOR], pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, [COLOR="#FF0000"]file cannot be decompressed[/COLOR]

This file can not be decompressed, if you look at the version number here it will indicate this file belongs to another folder inside the WinSxS folder.

Before we start repairing everything manually, please run the following tool:
Download and Run SFCFix

Please download and run SFCFix from >Here<

It will take about 15 minutes to process. Once the scan has completed a notepad file will launch with the results. Please copy and paste the entire contents of the results and post them back into this thread. Please put [CODE][/CODE] tags around the log to break up the text.
 
Thank you for replying my thread on such short notice. Yes , you're right , there're two diffrent errors in two different folders, the second error is related to the first folder in the picture I uploaded ,namely"msil_system.resources_b77a5c561934e089_4.0.9600.16404_zh-cn_12920e0ef53bd53d", and the first error is somewhat related to the 4th folder in the picture, namely "msil_system.resources_b77a5c561934e089_6.3.9600.16384_zh-cn_67fcb7c5132f5c6b", but there's small difference , the version number in the folder is "6.3.9600.16384" ,the version number in sfcdetials.txt is "4.0.9600.16384".
I've download SFCFIX ,and run it , but it takes like forvever to complete the operation , it's been running for more than 2 hours , it paused under " "the restore operation completed successfully.the component store corruption was repaired", should I let it run a longer time or just stop it?
 
I stopped it finally, and tried to run sfc /scannow ,but got an error ""Windows Resource Protection could not start the repair service" ,I booted into safemode ,and ran sfc /scannow again, the same error.
 
I have solved the "Windows Resource Protection could not start the repair service" by running sfc /scannow /offbootdir=C:\ /offwindir=c:\windows at boot time, now I can run sfc /scannow with no problem.
I tried deleting the two folders "msil_system.resources_b77a5c561934e089_4.0.9600.16404_zh-cn_12920e0ef53bd53d", and "msil_system.resources_b77a5c561934e089_6.3.9600.16384_zh-cn_67fcb7c5132f5c6b" , and ran sfc /scannow again, "file is missing" error persisted , but "file cannot be decompressed" error disappeared, I don't know if this information can help figure out the problem.
 
Sure I should be able to solve this one. Can you please provide a new CBS log, then I can prepare a manual fix. Also if you delete folders from WinSxS it will cause SFC to fall over the files are crucial system folders and need to be there.
 
Thank you.

What we have to determine now is if this file (System.resources.dll) can not be decompressed due to it being corrupt or the registry showing the incorrect value.

First thing first is to check the file's hash.

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    AutoAnalysis::

FileScan::
System.resources.dll)
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. 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.
 
Thank you so much. I am on a vacation with my family now ,probably gonna be away for like ten days, I will follow your instructions as soon as I get home, thanks again.
 
Hi. I'm back from the vacation ,thanks again for your help.
I followed your instructions, but the same problem happed again,it seems SFCFix would never complete the operation, it paused again at "the restore operation completed successfully.the component store corruption was repaired".
 
hello again,

Please try and run this script on its own, I have removed the part that would of made SFCFix stall.

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    FileScan::
System.resources.dll
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. 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.
 
It seems things are getting even worse. The operation finished the minute I started it this time, SFCFix.txt was created. Now I can't run sfc /scannow again, got the same error "Windows Resource Protection could not start the repair service", I can't even do it at boot time, I can't run DISM /Online /Cleanup-Image /RestoreHealth, got "Error: 14098,The component store has been corrupted." ,and even worse .net framework has mysteriously disappeared from the Windows Features dialog box(maybe some other features too).I have uploaded SFCFix.txt along with dism.log for you to analyse .
thank you so much.
Code: 
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-02-27 22:47:57.964
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\fisher\Desktop\SFCFixScript.txt [1]
 

FileScan::
[0: 1] C:\Windows\SoftwareDistribution\Download\32446d9f1312acde67926ef67861ad57\msil_system.resources_b77a5c561934e089_4.0.9600.16404_zh-cn_12920e0ef53bd53d\System.resources.dll
File is untraceable.
 Found: eMAI6B6P8riUrh8IS5i88/Kao/lzT+Xk9FKBKt4PBwU=
 Found: 4.0.30319.33440
Trace not available.
 
[1: 2] C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.resources\v4.0_4.0.0.0_zh-HANS_b77a5c561934e089\System.resources.dll
File is untraceable.
 Found: eMAI6B6P8riUrh8IS5i88/Kao/lzT+Xk9FKBKt4PBwU=
 Found: 4.0.30319.33440
Trace not available.
 [C:\Windows\Microsoft.NET\Framework\v4.0.30319\zh-Hans\System.resources.dll]

[2: 1] C:\Windows\WinSxS\msil_system.resources_b77a5c561934e089_4.0.9600.20728_zh-cn_fbc60c7b0ee1cf17\System.resources.dll
File is untraceable.
 Found: 5SfE+6umGQ+AFjwBaMaCxSomXBvqLG8RpY7RtIycMrw=
 Found: 4.0.30319.36213
Trace not available.
 
[3: 1] C:\Windows\WinSxS\msil_system.resources_b77a5c561934e089_4.0.9600.17253_zh-cn_12972876f53736d4\System.resources.dll
File is untraceable.
 Found: zj486lvdrkcOAQQ1lQorW1tmIvrTRrdLQrGOlFs6TlU=
 Found: 4.0.30319.34209
Trace not available.
 
[4: 1] C:\Windows\WinSxS\amd64_netfx4-system.resources_b03f5f7f11d50a3a_4.0.9600.20728_zh-cn_3b6fb7f5eba04eca\System.resources.dll
File is untraceable.
 Found: 5SfE+6umGQ+AFjwBaMaCxSomXBvqLG8RpY7RtIycMrw=
 Found: 4.0.30319.36213
Trace not available.
 
[5: 2] C:\Windows\WinSxS\amd64_netfx4-system.resources_b03f5f7f11d50a3a_4.0.9600.17253_zh-cn_5240d3f1d1f5b687\System.resources.dll
File is untraceable.
 Found: zj486lvdrkcOAQQ1lQorW1tmIvrTRrdLQrGOlFs6TlU=
 Found: 4.0.30319.34209
Trace not available.
 [C:\Windows\Microsoft.NET\Framework64\v4.0.30319\zh-Hans\System.resources.dll]

[6: 1] C:\Windows\WinSxS\msil_system.resources_b77a5c561934e089_6.3.9600.16384_zh-cn_67fcb7c5132f5c6b\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 
[7: 1] C:\Users\fisher\Desktop\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 
[8: 1] C:\Windows\System32\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 
[9: 1] C:\$WINDOWS.~BT\Sources\OCPayload\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.16384_zh-cn_53c780c84d695002\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 
[10: 1] C:\$WINDOWS.~BT\Sources\OCPayload\msil_system.resources_b77a5c561934e089_6.3.9600.16384_zh-cn_67fcb7c5132f5c6b\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 
[11: 1] C:\$WINDOWS.~BT\Sources\OCPayload\x86_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.16384_zh-cn_f7a8e544950bdecc\system.Resources.dll
File is untraceable.
 Found: WyfNcqmzGTpPMThM/mjRpVjlblIE0HzVl8MyAneQdXE=
 Found: 2.0.50727.7905
Trace not available.
 
[12: 4] C:\Windows\Microsoft.NET\Framework64\v2.0.50727\zh-CHS\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 [C:\Windows\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.16384_zh-cn_53c780c84d695002\system.Resources.dll]
 [C:\Windows\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.20708_zh-cn_54aba3cd66426d15\system.Resources.dll]
 [C:\Windows\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.17226_zh-cn_540a48364d36f784\system.Resources.dll]

[13: 1] C:\Windows\WinSxS\amd64_netfx4-system.resources_b03f5f7f11d50a3a_4.0.9600.16404_zh-cn_523bb989d1fa54f0\System.resources.dll
File is untraceable.
 Found: eMAI6B6P8riUrh8IS5i88/Kao/lzT+Xk9FKBKt4PBwU=
 Found: 4.0.30319.33440
Trace not available.
 
[14: 4] C:\Windows\Microsoft.NET\Framework\v2.0.50727\zh-CHS\system.Resources.dll
File is untraceable.
 Found: WyfNcqmzGTpPMThM/mjRpVjlblIE0HzVl8MyAneQdXE=
 Found: 2.0.50727.7905
Trace not available.
 [C:\Windows\WinSxS\x86_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.20708_zh-cn_f88d0849ade4fbdf\system.Resources.dll]
 [C:\Windows\WinSxS\x86_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.16384_zh-cn_f7a8e544950bdecc\system.Resources.dll]
 [C:\Windows\WinSxS\x86_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.3.9600.17226_zh-cn_f7ebacb294d9864e\system.Resources.dll]

[15: 1] C:\Windows\SoftwareDistribution\Download\97b4e482cf922ba4d540202faf8bb480\msil_system.resources_b77a5c561934e089_6.3.9600.16384_zh-cn_67fcb7c5132f5c6b\system.Resources.dll
File is untraceable.
 Found: rSNSwB0/nGfKcGs0sp73Bc3CRhMU+dEyot7acKSQwBQ=
 Found: 2.0.50727.7905
Trace not available.
 
[16: 1] C:\Users\fisher\Desktop\msil_system.resources_b77a5c561934e089_6.3.9600.16384_zh-cn_67fcb7c5132f5c6b\System.resources.dll
File is untraceable.
 Found: +P24lXcIggOBRq6l1JDxI2ItDyihK5p3rbPQPPsX72o=
 Version number not available.
Trace not available.
 
[17: 1] C:\Windows\WinSxS\msil_system.resources_b77a5c561934e089_4.0.9600.16404_zh-cn_12920e0ef53bd53d\System.resources.dll
File is untraceable.
 Found: eMAI6B6P8riUrh8IS5i88/Kao/lzT+Xk9FKBKt4PBwU=
 Found: 4.0.30319.33440
Trace not available.
FileScan:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-02-27 22:47:58.667
Script hash: 0Cb3VhH47pBLbzuDjOqvLuUpFxz/4+6tNRp2o6TNQak=
----------------------EOF-----------------------
 

Attachments

I figured out why sfc and dism failed to run, it has nothing to do with sfcfix. Serval days ago I loaded hive file COMPONENTS under the fold C:\Windows\System32\config into the registry using regdit, but forgot to unloaded it.
now everytime I run DISM /Online /Cleanup-Image /RestoreHealth ,a subkey COMPONENTS will automatically added to the rootkey HKLM , but under the subkey COMPONENTS there're only two values with name "StoreArchitecture" and "StoreFormatVersion" , apparently the hive was corrupt. Is there any way to restore the hive file COMPONENTS ?
The reason I loaded the hive COMPONENTS is that I found a manifest file "msil_system.resources_b77a5c561934e089_4.0.9600.16384_zh-cn_129a1082f5349fa4.manifest"under the folder C:\Windows\WinSxS\Manifests, but there's no corresponding assembly folder under C:\Windows\WinSxS\, I believe that that is which caused sfc to report" {20}]"System.resources.dll" of System.resources, Version = 4.0.9600.16384, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"zh-cn", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing", So I loaded COMPONENTS to trace what windows update that manifest originated from, but unfortunately I made things even worse.
 
Sorry for the delay, I must of missed your thread.

Do you have a back up of the COMPONENTS hive?

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command
    dir %systemroot%\System32\config >1&&notepad 1
    [*]Please post the contents of the notepad file back into this thread


 
Don't worry for the delay . no rush at all
The contents of the notepad file :
Code: 
 Volume in drive C is  system
 Volume Serial Number is B61E-3B8F
 Directory of C:\Windows\System32\config 
2015/02/28  17:51    <DIR>          .
2015/02/28  17:51    <DIR>          ..
2014/11/14  19:17           262,144 BCD-Template
2015/02/26  20:42        74,711,040 COMPONENTS
2013/08/22  21:25                 0 COMPONENTS.LOG
2015/02/28  17:51           524,288 default
2013/08/22  21:25                 0 DEFAULT.LOG
2015/03/02  21:57         4,915,200 drivers
2013/08/22  21:29               164 FP
2013/08/22  21:25    <DIR>          Journal
2014/12/21  19:38    <DIR>          RegBack
2015/02/28  17:51           262,144 sam
2015/02/28  17:51           262,144 security
2013/08/22  21:25                 0 SECURITY.LOG
2015/02/28  17:51        62,390,272 software
2013/08/22  21:25                 0 SOFTWARE.LOG
2015/02/28  17:51        10,747,904 system
2013/08/22  21:25                 0 SYSTEM.LOG
2015/02/03  20:10    <DIR>          systemprofile
2015/02/03  20:12    <DIR>          TxR
              14 个File(s)    154,075,300 bytes
                6 Dir(s) 94,011,596,800 bytes free
Thank you so much.
 
The hive is still there, if DISM/SFC can not read the contents the header of the hive may be corrup.

Can you please upload the COMPONENTS hive? It is found inside C:\Windows\System32\config.
 
[NO-PARSE][/NO-PARSE]
Go The Power said:
The hive is still there, if DISM/SFC can not read the contents the header of the hive may be corrup.

Can you please upload the COMPONENTS hive? It is found inside C:\Windows\System32\config.
Click to expand...
Yes, I know the hive is still there ,but I believe it is corrupt, because as I said in the earlier post ,when I load the hive into registry ,there're only two values with name "StoreArchitecture" and "StoreFormatVersion" under the subkey COMPONENTS .
The hive is a bit too big to attach in the pose ,and I have no access to either dropbox or onedrive, cause I' m in China . :)
So I upload it to Amazon clouddrive

https://www.amazon.com/clouddrive/share/QaUcYsx6CxsvYCoFDNv53coWO9VM8tZUYDue1NYO1qc


Thank you so much.
 
I remember what you said earlier, what I was looking at was to see if any of the data was still in tact. I opened the file up with a Hex Editor and I can see a lot of the data is still there. This means that one of the registry hive editors may be corrupt, these can often be extremely difficult to track down. I will see if I can find out, but as a warning you will most likely need to do a repair install or a fresh install of windows here.
 
Go The Power said:
I remember what you said earlier, what I was looking at was to see if any of the data was still in tact. I opened the file up with a Hex Editor and I can see a lot of the data is still there. This means that one of the registry hive editors may be corrupt, these can often be extremely difficult to track down. I will see if I can find out, but as a warning you will most likely need to do a repair install or a fresh install of windows here.
Click to expand...
I'm well-prepared to do a fresh install, there're no important data on my computer , and I have very few third party applications installed. My system worked perfectly fine ,even though sfc reported errors. Actually I just wanted to find out what really caused sfc to report the errors, and to get to the bottom of it. now I've screwed things up, it seems that there's no way to figure it out.
Anyway thank you so much for your help and your time, I really appreciate it.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top