New
#1
SFC cannot repair files
I installed some updated drivers from the Dell website & all seemed to be OK. Decided to run SFC & it said there were problems it could not repair. I have attached the CBS.log file.
Thanks for your help.
I installed some updated drivers from the Dell website & all seemed to be OK. Decided to run SFC & it said there were problems it could not repair. I have attached the CBS.log file.
Thanks for your help.
Try running these commands from a Elevated Command Prompt:
Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow
Or put them in a batch (.bat) file then run the batch file. It will then execute the commands sequentially without your interaction.
If you call the batch file DISMandSFC.bat and you run it like this:
DISMandSFC.bat 2>&1 > DISMandSFC.log
You won't see anything until the commands finish, which could be an hour or more, but all the output you would normally see will be placed in DISMandSFC.log.
The 2>&1 redirects standard error and standard output together into DISMandSFC.log.
A better way to do this is to install a windows port of the UNIX tee command. Then you woul enter:
DISMandSFC.bat" | tee DISMandSFC.log
You would get the normal output to the display and record it in DISMandSFC.log.
From: Windows batch: 'tee' command, 2nd response:
The GNU tool collection is always a good choice:
GnuWin32
The tee implementation is part of the core package:
CoreUtils for Windows
I tried to run the first command & received the reply "error 87 the startcomponenetcleanup option is not recognized in this context". Looking in the help section, I did not see a "startcomponenetcleanup" or a "restorehealth" command either. The only option that I saw that looked useful was "scanhealth", so I am running that.
Attached is the "checkSUR.log" from that scan.
My fault. Windows 7 uses SURT (System Update Readiness Tool). not DISM. That switch to DISM came in with Windows 8. Sorry about the mistake.
See here: What is the System Update Readiness Tool? - Windows Help
Download and run it then run sfc /scannow, see if SURT fixed anything.
You can also run sfc /scannow multiple (3-4) times as sometimes each run repairs a bit more.
I ran SUR & it came back with no problems. I have run SFC multiple times now & checked SFCdetails & it always reports the same 3 files as corrupt. As I understand the log, it is looking at another copy of each file & says they are corrupt also. I have searched for the 3 files & get at least 8 copies of each file on this machine. Looking at the date & time stamp, there are different files of each. I have done a hash comparison of the files, & have at least 3 copies of each file that are the same. Most of the files are dated this year, but each 1 also has a file dated from 2010 or 11. I have the Win7 install disk from Dell, can I find a good copy of the files there? Or have they been updated with a newer version? Attached is the latest SFCdetails.
As a side note, there were 12 MS updates that were installed last night. All installed without problems except the malicious software removal tool, which I was able to install this morning with no complaint?!
I have no expertise in fixing SFC problems. Never been able to figure it out. Seems like they could make the error messages simpler and more specific so it is obvious exactly which file or files are corrupted.
Hopefully one of the other folks here can help.
Yep, I agree, it seems like it could be easier. I think I have figured out the 3 files that are corrupt, but where are they located & where do I find good ones to copy? I have found multiple copies of each file on the machine & some of them have exact hash matches, so they can't all be corrupt (or can they?). And which one is the working copy? So far it is a mystery.
Thanks for your help.
Here's the error list from SFC's summary...
These seem to have crept in since your earlier thread!Code:2014-11-12 07:29:53, Info CSI 00000372 [SR] Beginning Verify and Repair transaction 2014-11-12 07:29:53, Info CSI 00000374 [SR] Cannot repair member file [l:54{27}]"PresentationHostDLL.dll.mui" of Microsoft-Windows-WPFCoreComp.Resources, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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 2014-11-12 07:29:53, Info CSI 00000376 [SR] Cannot repair member file [l:74{37}]"Microsoft.Transactions.Bridge.Dtc.dll" of Microsoft.Transactions.Bridge.Dtc, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2014-11-12 07:29:53, Info CSI 00000378 [SR] Cannot repair member file [l:42{21}]"SMConfigInstaller.exe" of WCF-M_SM_CFG_INS_EXE, Version = 6.1.7601.18523, 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-12 07:29:53, Info CSI 0000037a [SR] Cannot repair member file [l:54{27}]"PresentationHostDLL.dll.mui" of Microsoft-Windows-WPFCoreComp.Resources, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), 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 2014-11-12 07:29:53, Info CSI 0000037c [SR] Cannot repair member file [l:74{37}]"Microsoft.Transactions.Bridge.Dtc.dll" of Microsoft.Transactions.Bridge.Dtc, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2014-11-12 07:29:53, Info CSI 0000037e [SR] Cannot repair member file [l:42{21}]"SMConfigInstaller.exe" of WCF-M_SM_CFG_INS_EXE, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
I'll post a fix protocol when I can - after work!