SFC corruption

Jeff

Member
Joined
Nov 24, 2014
Posts
6
I also am having problems with this same issue on my wife's Asus laptop X53S and tried uninstalling Asus Webstorage program and no help still get faults in the log attachment includes the end of the CBS log
 

Attachments

Re: SFC /scannow cannot repair member file PINTLGB.IMD

Included full CBS log had to compress it
 

Attachments

Hello and welcome to the forum

I have moved your post into a new thread :)

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.

SFC /SCANNOW
  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 SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code:
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Thanks,
Alex
 
Code:
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-11-26 07:51:28.212
Not using a script file.
 

AutoAnalysis:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-11-26 08:02:25.239
----------------------EOF-----------------------
 
no longer gives errors all the way thru but still shows some items that couldn't be repaired I think?? But at the end of the file it says Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired. Could you explain this?

Code:
POQ 310 ends.
2014-11-26 08:26:43, Info                  CSI    0000062e [SR] Verify complete
2014-11-26 08:26:43, Info                  CSI    0000062f [SR] Repairing 3 components
2014-11-26 08:26:43, Info                  CSI    00000630 [SR] Beginning Verify and Repair transaction
2014-11-26 08:26:43, Info                  CSI    00000631 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2014-11-26 08:26:43, Info                  CSI    00000632 [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, 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
2014-11-26 08:26:43, Info                  CSI    00000633 [SR] Cannot repair member file [l:40{20}]"system.Resources.dll" of System.resources, Version = 6.1.7601.18529, 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
2014-11-26 08:26:43, Info                  CSI    00000634 [SR] Cannot repair member file [l:40{20}]"system.Resources.dll" of System.resources, Version = 6.1.7601.18529, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"fr-fr", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-11-26 08:26:43, Info                  CSI    00000635 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2014-11-26 08:26:43, Info                  CSI    00000636 [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, 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
2014-11-26 08:26:43, Info                  CSI    00000637 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2014-11-26 08:26:44, Info                  CSI    00000638 Hashes for file member \??\C:\Windows\IME\IMESC5\DICTS\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2014-11-26 08:26:44, Info                  CSI    00000639 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b\PINTLGB.IMD do not match actual file [l:22{11}]"PINTLGB.IMD" :
  Found: {l:32 b:l4ReoUNWh7axj8oO76qf9ql41yMn3b3y+lmJH5RaV7w=} Expected: {l:32 b:J6AvUKZSQcIPKPun7NfGVWIMm3i+0inkQGELvMplJfQ=}
2014-11-26 08:26:44, Info                  CSI    0000063a [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD"; source file in store is also corrupted
2014-11-26 08:26:44, Info                  CSI    0000063b [SR] Cannot repair member file [l:40{20}]"system.Resources.dll" of System.resources, Version = 6.1.7601.18529, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"fr-fr", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2014-11-26 08:26:44, Info                  CSI    0000063c [SR] This component was referenced by [l:158{79}]"Package_12_for_KB2972100~31bf3856ad364e35~amd64~~6.1.1.0.2972100-28_neutral_GDR"
2014-11-26 08:26:44, Info                  CSI    0000063d [SR] Cannot repair member file [l:40{20}]"system.Resources.dll" of System.resources, Version = 6.1.7601.18529, 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
2014-11-26 08:26:44, Info                  CSI    0000063e [SR] This component was referenced by [l:158{79}]"Package_26_for_KB2972100~31bf3856ad364e35~amd64~~6.1.1.0.2972100-56_neutral_GDR"
2014-11-26 08:26:44, Info                  CSI    0000063f Repair results created:
 
no longer gives errors all the way thru but still shows some items that couldn't be repaired I think?? But at the end of the file it says Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired. Could you explain this?

The files are not repaired, they still need fixing.

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. Download SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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.

SFC /SCANNOW
  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 SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code:
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive
 
Yes i ran the fix read my post and my cbs.log file still shows could not repair 3 files
 
Yes i ran the fix read my post and my cbs.log file still shows could not repair 3 files

I read your post and your CBS log. Now can you follow my previous instructions? The instructions I provided should fix this file, and you have not provided the logs I requested after. So I can not see if it worked or not.....
 

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

Back
Top