Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: SFC logs and how to fix.

11 Jul 2015   #21
wben353

Win 7 Home Premium x64/Linux Lite 2.6 x64
 
 

Quote   Quote: Originally Posted by Type24 View Post
Oh okay, I see them now. Instructions had said: C:\Windows\Temp\CheckSUR\winsxs\Manifests. That one was empty. The other you mentioned is filled. I've replaced the files. Heres the new CheckSur log.
Here's 1 of the missing manifest files, I'll keep looking for the other(s)




Attached Files
File Type: zip Manifest.zip (2.9 KB, 0 views)
My System SpecsSystem Spec
.
11 Jul 2015   #22
wben353

Win 7 Home Premium x64/Linux Lite 2.6 x64
 
 

Quote   Quote: Originally Posted by wben353 View Post
Quote   Quote: Originally Posted by Type24 View Post
Oh okay, I see them now. Instructions had said: C:\Windows\Temp\CheckSUR\winsxs\Manifests. That one was empty. The other you mentioned is filled. I've replaced the files. Heres the new CheckSur log.
Here's 1 of the missing manifest files, I'll keep looking for the other(s)
I indexed my manifest folder, don't have:

winsxs\manifests\amd64_806a6b8758663009d2a7571371f341fe_31bf3856ad364e35_11.2.9600.17728_none_16c76c 7c8091ce9b.manifest

Maybe another forum member can supply that file.

Windows update should replace the KB .mum & .cat file if needed.

I'll check my desktop machine tomorrow for that file when I'm back at home. Currently dogsitting for my Sister.
My System SpecsSystem Spec
11 Jul 2015   #23
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

There's nothing in the SFC details that can be fixed by file replacements.
Code:
2015-07-08 12:50:23, Info                  CSI    00000706 [SR] Repairing 6 components
2015-07-08 12:50:23, Info                  CSI    00000707 [SR] Beginning Verify and Repair transaction
2015-07-08 12:50:23, Info                  CSI    0000070a [SR] Cannot verify component files for 528e4ea22a57c7e821dc4e0dae7ea698, Version = 6.1.7601.18758, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    0000070d [SR] Cannot verify component files for 806a6b8758663009d2a7571371f341fe, Version = 11.2.9600.17728, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000710 [SR] Cannot verify component files for bfb1fea2bdae7d1b916e2a4b72887137, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000713 [SR] Cannot verify component files for f39b168bc9d422afb9d29ab2ed224c81, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000716 [SR] Cannot verify component files for f9f796917d672e1e1f983f9f45e9d8dd, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000718 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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
2015-07-08 12:50:23, Info                  CSI    0000071a [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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
The CheckSUR report explains most of the above problems...
Code:
Unavailable repair files:
 winsxs\manifests\amd64_806a6b8758663009d2a7571371f341fe_31bf3856ad364e35_11.2.9600.17728_none_16c76c7c8091ce9b.manifest
 winsxs\manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23002_none_afecb2d81756dfe8.manifest
 servicing\packages\Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
I'll post a fix for those a little later.

The last two problems in the SFC are caused by a faulty Windows Update, which MS promise they'll get around to fixing one day (but don't hold your breath!) - KB3022345. You can either ignore it or uninstall the update (and hide both it, and KB3068708 when they appear in the update list).
My System SpecsSystem Spec
.

11 Jul 2015   #24
wben353

Win 7 Home Premium x64/Linux Lite 2.6 x64
 
 

Quote   Quote: Originally Posted by NoelDP View Post
There's nothing in the SFC details that can be fixed by file replacements.
Code:
2015-07-08 12:50:23, Info                  CSI    00000706 [SR] Repairing 6 components
2015-07-08 12:50:23, Info                  CSI    00000707 [SR] Beginning Verify and Repair transaction
2015-07-08 12:50:23, Info                  CSI    0000070a [SR] Cannot verify component files for 528e4ea22a57c7e821dc4e0dae7ea698, Version = 6.1.7601.18758, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    0000070d [SR] Cannot verify component files for 806a6b8758663009d2a7571371f341fe, Version = 11.2.9600.17728, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000710 [SR] Cannot verify component files for bfb1fea2bdae7d1b916e2a4b72887137, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000713 [SR] Cannot verify component files for f39b168bc9d422afb9d29ab2ed224c81, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000716 [SR] Cannot verify component files for f9f796917d672e1e1f983f9f45e9d8dd, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-07-08 12:50:23, Info                  CSI    00000718 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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
2015-07-08 12:50:23, Info                  CSI    0000071a [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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
The CheckSUR report explains most of the above problems...
Code:
Unavailable repair files:
 winsxs\manifests\amd64_806a6b8758663009d2a7571371f341fe_31bf3856ad364e35_11.2.9600.17728_none_16c76c7c8091ce9b.manifest
 winsxs\manifests\wow64_microsoft-windows-systemrestore-main_31bf3856ad364e35_6.1.7601.23002_none_afecb2d81756dfe8.manifest
 servicing\packages\Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
I'll post a fix for those a little later.

The last two problems in the SFC are caused by a faulty Windows Update, which MS promise they'll get around to fixing one day (but don't hold your breath!) - KB3022345. You can either ignore it or uninstall the update (and hide both it, and KB3068708 when they appear in the update list).
NoelDP Thanks for providing the additional help. I look forward to reviewing your fix. wben353
My System SpecsSystem Spec
11 Jul 2015   #25
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

I've uploaded a file - t24aa.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 thedefault location - which will create a new folder t24aa 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 thefolder

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.
My System SpecsSystem Spec
11 Jul 2015   #26
wben353

Win 7 Home Premium x64/Linux Lite 2.6 x64
 
 

NoelDP did you obtain those files from your computer? I searched mine, nada on those files.
My System SpecsSystem Spec
11 Jul 2015   #27
UsernameIssues

W7 Pro SP1 64bit
 
 

Quote   Quote: Originally Posted by wben353 View Post
NoelDP did you obtain those files from your computer? I searched mine, nada on those files.
See the 3rd bullet in this post:
Can't upgrade IE, KB2670838 returns error 800B0100
My System SpecsSystem Spec
11 Jul 2015   #28
wben353

Win 7 Home Premium x64/Linux Lite 2.6 x64
 
 
3rd bullet in post

Read entire post, didn't find answer to where noeldp found the files to upload.
My System SpecsSystem Spec
11 Jul 2015   #29
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Quote:
The SURT/CheckSUR tool scans all the components of Windows - which are recorded in the registry - and checks that all references are present, and all control files present (it now also checks for 'payload' files - but makes no attempt to repair them) and attempts to correct any errors it finds. The reason that it's so large is that it contains a huge store of potential replacement files (I once tried to expand all the files, and it got to 6GB before I stopped it!)
The trick is to have a similarly large stock of files from which to draw - my current archive weighs in at about 60GB (mostly Win7 x64 or x86, with a few Vista) from which you can cherry-pick the relevant files and then use CheckSUR to do the necessary replacement.
All updates can be downloaded as standalones - the trick is being able to unpack them and have the storage space to store them.
My System SpecsSystem Spec
11 Jul 2015   #30
wben353

Win 7 Home Premium x64/Linux Lite 2.6 x64
 
 

Thanks Noeldp for the informative reply. Never ending learning curve. Microsoft site how to read CheckSUR.log indicates that manifest files are found on computer running same os version of the computer needing replacement. Are the manifest files downloadable as well?
My System SpecsSystem Spec
Reply

 SFC logs and how to fix.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Error with WLM logs
Hi. I'm no longer able to open some old .xml logs I have saved many years ago. When i try to open it on IE it shows a blank screen. On other browsers: "error on line 1 at column 1: Encoding error". On a notepad it shows unreadable characters. So i guess somehow the encode got messed up...
Software
Windows 7 Main Account Logs On then Automatically Logs Off
New to the site and I hope this is in the right forum. I am using Windows 7 Pro 64 and my main account logs in then automatically logs off. I can successfully log in using Safe Mode to this account. I created another account called test and I can access this account in both Safe and Normal...
General Discussion
Windows logs off?
Everytime after a period of inactivity I'm logged out and get the enter password screen.. I've checked all the power save options and can't think what's causing it, any ideas??
General Discussion
logs in win 7
hello, It seems that win 7 is saving a lot of logs how can i fix it that win 7 is using the minimum of my hdd? in 2 weeks from 14 gb to 35
Performance & Maintenance


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:13.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App