Solved SFC logs and how to fix.

[wben353]

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)

 

[wben353]

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_16c76c7c8091ce9b.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.

 

[NoelDP]

There's nothing in the SFC details that can be fixed by file replacements.

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...

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).

 

[wben353]

There's nothing in the SFC details that can be fixed by file replacements.

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...

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

 

[NoelDP]

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.

 

[wben353]

NoelDP did you obtain those files from your computer? I searched mine, nada on those files.

 

[UsernameIssues]

NoelDP did you obtain those files from your computer? I searched mine, nada on those files.

See the 3rd bullet in this post:
http://www.sevenforums.com/windows-...838-returns-error-800b0100-2.html#post3102436

 

[wben353]

3rd bullet in post

Read entire post, didn't find answer to where noeldp found the files to upload.

 

[NoelDP]

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.

 

[wben353]

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?

 

[NoelDP]

All the required files are inside the standalone updates - for all languages.

 

[Type24]

Hello again! Sorry for the delay and thanks again for all the replies. It's very much appreciated. I've gone ahead and downloaded that zip and moved the files into their respective directories. I ran the readiness tool and I've attached the latest checksur log.

 

[wben353]

Hello again! Sorry for the delay and thanks again for all the replies. It's very much appreciated. I've gone ahead and downloaded that zip and moved the files into their respective directories. I ran the readiness tool and I've attached the latest checksur log.

Log looks good, all files with (f) have corresponding (fix)

Summary:
Seconds executed: 175
Found 3 errors
Fixed 3 errors
CSI Manifest Failed Catalog Check Total count: 2
Fixed: CSI Manifest Failed Catalog Check. Total count: 2
CBS MUM Missing Total count: 1
Fixed: CBS MUM Missing. Total count: 1
Fixed: CBS Paired File. Total count: 1

run sfc /scannow again and all should be well!!

 

[NoelDP]

Hello again! Sorry for the delay and thanks again for all the replies. It's very much appreciated. I've gone ahead and downloaded that zip and moved the files into their respective directories. I ran the readiness tool and I've attached the latest checksur log.

CheckSUR at least is happy now - please run SFC /SCANNOW again, and post the new CBS.log.
Then I can work on the file problems from that.

 

[Type24]

That's great news! thanks again! I've run another SFC scan. Here are the detail logs for that as attached.

 

[NoelDP]

Great - nothing there apart from a couple of false-positives created by an MS screwup with KB3068708, which can be ignored.

Do a Check for Updates - attempt to install ONLY the oldest update found. What happens?

 

[Type24]

That's good news! In regards to the check for updates; was that a check for windows update and then look under the 'optional' updates for the oldest windows update there?

 

[NoelDP]

If there's no Important ones, then yes - but it's better to first concentrate on the Security/Important updates if you can.

 

[Type24]

Okay there was just 1 important update. A small one. Installed it. Nothing unusual happened.

 

[NoelDP]

There'll be a few more later today

Sounds like it's fixed - but today's updates will confirm it.