Solved How to understand this SFCdetails.txt

dippas · Jul 16, 2015

How to understand file SFCdetails.txt

Hi everyone.

I recently had to format one machine at work that wasn't booting, so I managed to do that without data loss.

A few days the machine was doing some awkward stuff (I don't recall what to be honest), I googled and find out that could be HD bad clusters and it was that , which with a

Code:

 chkdsk /f/r

and a software called H.Dat managed to solve that.

Yesterday the machine restarted for updates, but failed to finished the update, giving me different errors for each update (total 5), I googled again and one of the errors (80070026) suggested me to do a system file checker, So I did, and it did find corrupt files being unable to fix them.

I already searched the internet for a "easy" way to fix this, but I really think this is a matter of understanding the SFCdetails.txt and with that being able to repair the corrupt files.

Things I've tried:

System Restore - was Successful but still errors in sfc
Uninstalling updates (even with wusa /uninstall /kb:{update ID}) - giving me errors in windows installer standalone 0x0800f0900

P.S. - The machine seems to be running smoothly, but I would appreciate any help in trying to fix this errors. Because at the moment windows update even if it can download, it can't fully install some of the the updates.

GokAy · Jul 16, 2015

There are about 8-10 corrupt files, I will PM our SFC master. Hopefully, he will advice you when he has the time.

dippas · Jul 16, 2015

GokAy said:
There are about 8-10 corrupt files, I will PM our SFC master. Hopefully, he will advice you when he has the time.

Thank you. I'll wait then.

NoelDP · Jul 17, 2015

The errors here are with the control files for updates, rather than active system files -

Code:

2015-07-16 20:55:18, Info                  CSI    000003c3 [SR] Repairing 8 components
2015-07-16 20:55:18, Info                  CSI    000003c4 [SR] Beginning Verify and Repair transaction
2015-07-16 20:55:18, Info                  CSI    000003c6 [SR] Cannot repair member file [l:32{16}]"IEExecRemote.dll" of IEExecRemote, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-16 20:55:18, Info                  CSI    000003c8 [SR] Cannot repair member file [l:54{27}]"OxpsConverter.Resources.dll" of OxpsConverter.Resources, Version = 6.1.7601.17932, pA = PROCESSOR_ARCHITECTURE_MSIL (8), 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
2015-07-16 20:55:18, Info                  CSI    000003cb [SR] Cannot verify component files for Microsoft-Windows-CmiTrustInfoInstallers, Version = 6.1.7601.18766, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:1122334455667788}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-16 20:55:18, Info                  CSI    000003cd [SR] Cannot repair member file [l:24{12}]"WUDFHost.exe" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, 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
2015-07-16 20:55:18, Info                  CSI    000003cf [SR] Cannot repair member file [l:56{28}]"Windows Navigation Start.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.17377, 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
2015-07-16 20:55:18, Info                  CSI    000003d2 [SR] Cannot verify component files for Microsoft-Windows-Legacy-Registry-Support-TCPIP, Version = 6.1.7601.17964, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-16 20:55:18, Info                  CSI    000003d5 [SR] Cannot verify component files for Microsoft-Windows-osk, Version = 6.1.7601.18512, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-16 20:55:18, Info                  CSI    000003d8 [SR] Cannot verify component files for wdmaudio.inf, Version = 6.1.7601.18276, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015

We need to use CheckSUR to fix/confirm these, rather than SFC...

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

dippas · Jul 17, 2015

Hi NoelDP,

thanks for your time, I've attached the checkSUR as you requested.

NoelDP · Jul 17, 2015

Not as bad as I was expecting

Code:

Unavailable repair files:
	winsxs\manifests\x86_microsoft-windows-cmitrustinfoinstallers_1122334455667788_6.1.7601.18766_none_93d8403915705daa.manifest
	winsxs\manifests\x86_microsoft-windows-cmitrustinfoinstallers_1122334455667788_6.1.7601.22972_none_94530dd62e99b130.manifest
	winsxs\manifests\x86_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7600.21203_en-us_c798ddbbd1ddb6cd.manifest
	winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22865_en-us_5c61885bd163d89d.manifest
	winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.18812_en-us_5c0afc34b8205e40.manifest
	winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.23017_en-us_5c997293d139afff.manifest
	winsxs\manifests\x86_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.18812_none_3cd2a358daf90b3c.manifest
	servicing\packages\Package_1_for_KB3010788~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_2_for_KB2931356~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_31_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_32_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_41_for_KB3008627~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_41_for_KB3008627~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_57_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_59_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_59_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_60_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_60_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_74_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_77_for_KB3008627~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_78_for_KB3008627~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_78_for_KB3008627~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB2931356_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB2968294~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3008627_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3010788_SP1~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_for_KB3010788~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_for_KB3011780_SP1~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_for_KB3014406~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_for_KB3033889_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3033889~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Win8IP-Microsoft-Windows-Printing-Package~31bf3856ad364e35~x86~~7.1.7601.16492.mum

I'll post a fix protocol when I can get to it!

dippas · Jul 17, 2015

Thank you, I'll wait for your reply. I'll appreciate your time on helping me out with this

NoelDP · Jul 18, 2015

Sorry about the delay - it took me a while to find some of the relevant updates!

I've uploaded a file - dpsaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder dpsaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

dippas · Jul 18, 2015

Hi NoelDP,

thanks for replying, don't you worry about being late, we all have a life besides Internet (therefore my late reply too)

as you asked, I've done all the steps above and here is the ckeckSUR logs.

I noticed that this time it fixed 22 out 31, against fixed 0 out 35 the first time, so we are going well

NoelDP · Jul 18, 2015

Odd - I thought I'd got them all...

Code:

Unavailable repair files:
	servicing\packages\Package_32_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.mum
	servicing\packages\Package_74_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB2968294~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3014406~31bf3856ad364e35~x86~~6.1.1.1.mum
	servicing\packages\Package_for_KB3033889_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3033889~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Win8IP-Microsoft-Windows-Printing-Package~31bf3856ad364e35~x86~~7.1.7601.16492.mum
	servicing\packages\Package_32_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5.cat
	servicing\packages\Package_74_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.cat
	servicing\packages\Package_for_KB2968294~31bf3856ad364e35~x86~~6.1.1.1.cat
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.cat
	servicing\packages\Package_for_KB3014406~31bf3856ad364e35~x86~~6.1.1.1.cat
	servicing\packages\Package_for_KB3033889_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
	servicing\packages\Package_for_KB3033889~31bf3856ad364e35~x86~~6.1.1.0.cat
	servicing\packages\Win8IP-Microsoft-Windows-Printing-Package~31bf3856ad364e35~x86~~7.1.7601.16492.cat

I'll post another fix tomorrow - hopefully it'll get the rest

dippas · Jul 18, 2015

Hi NoelDP,

Don't worry. just FYI

I double check the packages you sent me and for instances for this:

Code:

 servicing\packages\[B]Package_32_for_KB3011780~31bf3856ad364e35~x86~~6.1.1.5[/B].mum

you gave me these files below:

Code:

[B]package_32_for_kb3011780_bf~31bf3856ad364e35~x86~~6.1.1.5
package_for_kb3011780_sp1~31bf3856ad364e35~x86~~6.1.1.5
package_for_kb3011780~31bf3856ad364e35~x86~~6.1.1.5[/B]

I'm not an expert in this matter, but I'll take a guess that the names are mismatching (e.g - the first one has an extra _bf).

And for this one:

Code:

servicing\packages\Package_74_for_KB3068708~31bf3856ad364e35~x86~~6.1.1.0.mum

There is no file on the .zip you sent me.

Again don't worry, I'll wait for you fix, and thank you once more for your time.

NoelDP · Jul 18, 2015

I've uploaded a file - dpsab.zip - to my OneDrive at https://onedrive.live.com/?cid=936736BB8FCEB92F&id=936736BB8FCEB92F!1007
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder dpsab in the same place.
Open this folder - there should be one folders inside it (Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

dippas · Jul 19, 2015

Hi NoelDP,

thanks for sending me the fix so quickly, I did again the steps above, but still 2 packages to fix.

because you gave me AMD packages. I've attached the CheckSUR logs

Thanks, once more for your patient

NoelDP · Jul 19, 2015

Not enough caffeine!

Code:

Unavailable repair files:
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.mum
	servicing\packages\Package_for_KB3005607_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
	servicing\packages\Package_for_KB3005607~31bf3856ad364e35~x86~~6.1.1.0.cat

new file - dpsac.zip - same procedure.

dippas · Jul 19, 2015

Hi NoelDP,

as usual here I've attached the checkSUR logs (this time no errors

)

so I decided to run the

Code:

 SFC /scannow

but still giving me errors, so I've attached the SFCdetails.txt

hope you can help me pn this one too

NoelDP · Jul 20, 2015

OK - here's the error-list

Code:

	Line 292: 2015-07-19 16:38:18, Info                  CSI    000001ee [SR] Repairing 4 components
	Line 293: 2015-07-19 16:38:18, Info                  CSI    000001ef [SR] Beginning Verify and Repair transaction
	Line 294: 2015-07-19 16:38:18, Info                  CSI    000001f1 [SR] Cannot repair member file [l:32{16}]"IEExecRemote.dll" of IEExecRemote, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 295: 2015-07-19 16:38:18, Info                  CSI    000001f3 [SR] Cannot repair member file [l:54{27}]"OxpsConverter.Resources.dll" of OxpsConverter.Resources, Version = 6.1.7601.17932, pA = PROCESSOR_ARCHITECTURE_MSIL (8), 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
	Line 296: 2015-07-19 16:38:18, Info                  CSI    000001f5 [SR] Cannot repair member file [l:24{12}]"WUDFHost.exe" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, 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
	Line 297: 2015-07-19 16:38:18, Info                  CSI    000001f7 [SR] Cannot repair member file [l:56{28}]"Windows Navigation Start.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.17377, 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 for those when I can!

dippas · Jul 20, 2015

Thank you NoelDP, I'll wait

dippas · Jul 27, 2015

bump this

NoelDP · Jul 27, 2015

Sorry about that - 12-hour days and a cold don't lead to much coherent thought!

I've still not been able to find the last file, but I think I have a workaround for that

Let's fix the others in the meantime...

I've uploaded a file - dpsad.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\dpsad
hit the enter key - if you get a 'Not Found' error try
DIR D:\dpsad
or
DIR E:\dpsad

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\dpsad <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

dippas · Jul 27, 2015

HI NoelDP,

just followed every step, here is my CBS.log and just in case sfcdetails.txt

I'm not quiet sure if it registered something to checksur logs this time and my sfcdetails looks the same as my previous that I posted here.

Solved How to understand this SFCdetails.txt

Front-end Dev

Attachments

My Computer My Computer

New member

My Computer My Computer

Front-end Dev

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

Attachments

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

Attachments

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

Attachments

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

Attachments

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

My Computer My Computer

Front-end Dev

My Computer My Computer

Three-Toed Sloth

My Computer My Computer

Front-end Dev

Attachments

My Computer My Computer

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer