[SOLVED] sfc found corrupt files unable to fix, win update broken..

scottfree1

Member
Joined
Oct 25, 2013
Posts
9
Main symptom is windows update has stopped working with various generic 0x800 failure messages, sfc's getting a few or a bunch (see attached) of these,

Info CSI 0000003b [SR] Cannot verify component files for Microsoft-Windows-Application-Experience-Upgrade-Compat-Telemetry, Version = 6.1.7601.18444, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

"info" seems an optimistic description, helpful info would be nice, have run checksur, sfc and tweaking.com's "all-in-one windows repair tool" multiple times with no change, this seems right in your guys wheelhouse was hopping you can help? Thanks
 

Attachments

Sorry for the delay! We're really snowed under with work at the moment, and are just beginning to dig ourselves out of it all. There are only a few of us who deal with Windows Update threads, so we can become overwhelmed with work quite quickly! Anyway...

Wow, your CheckSUR log is pretty busy!

Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-06-04 10:29

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x80070026    servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~%n-US~7.q.7601.16492nmum        Line 1: X„
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~%n-US~7.q.7601.cat        
(f)    CBS MUM Corrupt    0x80070026    servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~!md64~en-US~7.1.w601.16492.m5m        Line 1: X6
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~!md64~en-US~7.1.w601.16492.cat        

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_2_for_KB2964358~31bf3856ad364e35~amd64~~6.1.1.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2964358_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2964358~31bf3856ad364e35~amd64~~6.1.1.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~en-US~7.1.7601.16492.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~en-US~7.1.7601.16492.mum        

Checking Component Store
(f)    CSI Payload File Missing    0x00000000    System.Web.RegularExpressions.dll    amd64_netfx-system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.18320_none_7e1d06775ff8f8a9    
(f)    CSI Payload File Missing    0x00000000    webengine.dll    amd64_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.18320_none_c34fc404e0119b41    
(f)    CSI Manifest Missing    0x00000002    amd64_be9d73899a580155d2f4c7699dd64558_31bf3856ad364e35_8.0.7601.18446_none_49310c4954a2e7eb.manifest    amd64_be9d73899a580155d2f4c7699dd64558_31bf3856ad364e35_8.0.7601.18446_none_49310c4954a2e7eb    
(f)    CSI Payload File Missing    0x00000000    kerberos.dll    amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.17926_none_44f41adac7735d74    
(f)    CSI Payload File Missing    0x00000000    kerberos.dll    wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.17926_none_4f48c52cfbd41f6f    
(f)    CSI Payload File Missing    0x00000000    aspnet_wp.exe    amd64_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.18320_none_5199598a346f14bb    
(f)    CSI Manifest Missing    0x00000002    amd64_83a8cc8b5b01d4cd4310479ce169dce7_31bf3856ad364e35_8.0.7601.22657_none_c10d16ebcfd0e4f9.manifest    amd64_83a8cc8b5b01d4cd4310479ce169dce7_31bf3856ad364e35_8.0.7601.22657_none_c10d16ebcfd0e4f9    
(f)    CSI Payload File Missing    0x00000000    System.Web.dll    amd64_system.web_b03f5f7f11d50a3a_6.1.7601.18320_none_83d82ebcbea9a2ee    
(f)    CSI Payload File Missing    0x00000000    aspnet_wp.exe    x86_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.18320_none_9946906148eb3dc1    
(f)    CSI Manifest Missing    0x00000002    amd64_423d04ba87e48f1e56d8e4abd90cb62b_31bf3856ad364e35_6.1.7601.18444_none_692ba3b4a3cfb708.manifest    amd64_423d04ba87e48f1e56d8e4abd90cb62b_31bf3856ad364e35_6.1.7601.18444_none_692ba3b4a3cfb708    
(f)    CSI Payload File Missing    0x00000000    System.Web.dll    x86_system.web_b03f5f7f11d50a3a_6.1.7601.18320_none_cb856593d325cbf4    
(f)    CSI Manifest Missing    0x00000002    amd64_decd919d90e8825e76adc9988e2245f0_31bf3856ad364e35_6.1.7601.18444_none_a1a3cdcea8866bdb.manifest    amd64_decd919d90e8825e76adc9988e2245f0_31bf3856ad364e35_6.1.7601.18444_none_a1a3cdcea8866bdb    
(f)    CSI Manifest Missing    0x00000002    amd64_0e06d2ed6f93d560f6a34c100512684b_31bf3856ad364e35_6.1.7601.18444_none_8c92b13960b1699a.manifest    amd64_0e06d2ed6f93d560f6a34c100512684b_31bf3856ad364e35_6.1.7601.18444_none_8c92b13960b1699a    
(f)    CSI Payload File Missing    0x00000000    webengine.dll    x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.18320_none_0afcfadbf48dc447    
(f)    CSI Payload File Missing    0x00000000    System.Web.RegularExpressions.dll    msil_system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.18320_none_21e88724db220fa6    
(f)    CSI Manifest Missing    0x00000002    wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22657_none_96d950c5fd673509.manifest    wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22657_none_96d950c5fd673509    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22657_none_8c84a673c906730e.manifest    amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22657_none_8c84a673c906730e    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18446_none_8c04d764afe1a0d5.manifest    amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18446_none_8c04d764afe1a0d5    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-a..rience-program-data_31bf3856ad364e35_6.1.7601.18444_none_cf6dcf3199c084a3.manifest    amd64_microsoft-windows-a..rience-program-data_31bf3856ad364e35_6.1.7601.18444_none_cf6dcf3199c084a3    
(f)    CSI Manifest Missing    0x00000002    wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18446_none_965981b6e44262d0.manifest    wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18446_none_965981b6e44262d0    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-a..de-compat-telemetry_31bf3856ad364e35_6.1.7601.18444_none_e5b1b7ec100d8e3b.manifest    amd64_microsoft-windows-a..de-compat-telemetry_31bf3856ad364e35_6.1.7601.18444_none_e5b1b7ec100d8e3b    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-a..ence-telemetry-sdbs_31bf3856ad364e35_6.1.7601.18444_none_66295be460b59c2a.manifest    amd64_microsoft-windows-a..ence-telemetry-sdbs_31bf3856ad364e35_6.1.7601.18444_none_66295be460b59c2a    
(f)    CSI Payload File Missing    0x00000000    System.Web.dll    x86_system.web_b03f5f7f11d50a3a_6.1.7601.22515_none_b4b64c7decce9319    
(f)    CSI Payload File Missing    0x00000000    kerberos.dll    amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22084_none_453aadc5e0c3a851    
(f)    CSI Payload File Missing    0x00000000    aspnet_wp.exe    x86_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.22515_none_8277774b629404e6    
(f)    CSI Payload File Missing    0x00000000    System.Web.RegularExpressions.dll    amd64_netfx-system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.22515_none_674ded6179a1bfce    
(f)    CSI Payload File Missing    0x00000000    System.Web.dll    amd64_system.web_b03f5f7f11d50a3a_6.1.7601.22515_none_6d0915a6d8526a13    
(f)    CSI Payload File Missing    0x00000000    System.Web.RegularExpressions.dll    msil_system.web.regularexpressions_b03f5f7f11d50a3a_6.1.7601.22515_none_0b196e0ef4cad6cb    
(f)    CSI Payload File Missing    0x00000000    webengine.dll    x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.22515_none_f42de1c60e368b6c    
(f)    CSI Payload File Missing    0x00000000    kerberos.dll    wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22084_none_4f8f581815246a4c    
(f)    CSI Payload File Missing    0x00000000    aspnet_wp.exe    amd64_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7601.22515_none_3aca40744e17dbe0    
(f)    CSI Payload File Missing    0x00000000    webengine.dll    amd64_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.22515_none_ac80aaeef9ba6266    

Summary:
Seconds executed: 343
 Found 45 errors
  CSI Manifest Missing Total count: 12
  CSI Payload File Missing Total count: 20
  CBS MUM Missing Total count: 9
  CBS MUM Corrupt Total count: 2
  CBS Catalog Missing Total count: 2

Unavailable repair files:
    winsxs\manifests\amd64_be9d73899a580155d2f4c7699dd64558_31bf3856ad364e35_8.0.7601.18446_none_49310c4954a2e7eb.manifest
    winsxs\manifests\amd64_83a8cc8b5b01d4cd4310479ce169dce7_31bf3856ad364e35_8.0.7601.22657_none_c10d16ebcfd0e4f9.manifest
    winsxs\manifests\amd64_423d04ba87e48f1e56d8e4abd90cb62b_31bf3856ad364e35_6.1.7601.18444_none_692ba3b4a3cfb708.manifest
    winsxs\manifests\amd64_decd919d90e8825e76adc9988e2245f0_31bf3856ad364e35_6.1.7601.18444_none_a1a3cdcea8866bdb.manifest
    winsxs\manifests\amd64_0e06d2ed6f93d560f6a34c100512684b_31bf3856ad364e35_6.1.7601.18444_none_8c92b13960b1699a.manifest
    winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22657_none_96d950c5fd673509.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22657_none_8c84a673c906730e.manifest
    winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18446_none_8c04d764afe1a0d5.manifest
    winsxs\manifests\amd64_microsoft-windows-a..rience-program-data_31bf3856ad364e35_6.1.7601.18444_none_cf6dcf3199c084a3.manifest
    winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18446_none_965981b6e44262d0.manifest
    winsxs\manifests\amd64_microsoft-windows-a..de-compat-telemetry_31bf3856ad364e35_6.1.7601.18444_none_e5b1b7ec100d8e3b.manifest
    winsxs\manifests\amd64_microsoft-windows-a..ence-telemetry-sdbs_31bf3856ad364e35_6.1.7601.18444_none_66295be460b59c2a.manifest
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~%n-US~7.q.7601.mum
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~%n-US~7.q.7601.mum
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~!md64~en-US~7.1.w601.16492.mum
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~!md64~en-US~7.1.w601.16492.mum
    servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_2_for_KB2964358~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB2964358_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB2964358~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~en-US~7.1.7601.16492.mum
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~en-US~7.1.7601.16492.mum
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~%n-US~7.q.7601.cat
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~%n-US~7.q.7601.cat
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~!md64~en-US~7.1.w601.16492.cat
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~!md64~en-US~7.1.w601.16492.cat
    servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_2_for_KB2964358~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB2964358_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB2964358~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~en-US~7.1.7601.16492.cat
    servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~en-US~7.1.7601.16492.cat

This is going to take a few different repairs to do, so don't expect any immediate improvement! Let's start with this.

Windows Update Package Replacement

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. Please download the file, Packs.zip from my Dropbox -->here<--and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

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



  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages



  7. Run the System Update Readiness Tool (SURT) again
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log


Stephen
 
Finally got an in-place upgrade, I have not been able to do that before because the official iso from ms would always fail with..

"You can’t upgrade 64-bit Windows to a 32-bit version of Windows. To upgrade, obtain a 64-bit version of the installation disc, or go online to see how to install Windows 7 and keep your files and settings.
32-bit Windows cannot be upgraded to a 64-bit version of Windows. To upgrade, obtain a 32-bit version of the Windows installation disc."

Of course it was the it was the same iso I originally had installed with, so just more ms catch 22.. 64.. 32.. hut. hut..but I just ran across these new iso's "Windows 7 SP1 Media Refresh edition" and they did the trick and allowed an in-place upgrade, that allowed me to get ie11 to install. Of course it's MS so fix one, break another and now .net 4.0/4.51 are hosed..

Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft .NET Framework 4.5.1 for Windows 7 x64-based Systems (KB2858725).

Haven't gotten into this error to much, but the .net cleanup tool and full install as admin were flops, so if you have any incite on it thanks..
 
Last edited:
Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft .NET Framework 4.5.1 for Windows 7 x64-based Systems (KB2858725).

Haven't gotten into this error to much, but the .net cleanup tool and full install as admin were flops, so if you have any incite on it thanks..

.NET Framework updates can be tricky beasts, but I'm more than willing to have a look for you. Please re-run SURT for me again. If you no longer have a copy of SURT, please download it again from here: What is the System Update Readiness Tool? - Windows Help. Once SURT has completed installing, please zip up and attach the following log to your next post:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Stephen
 
Sfc came up clean, I'm getting a fresh copy surt to make sure I have the latest one, this in why I hate in-place/fresh installs my system was virtually error free no errors from the OS, other than when ms would ignore "hide update" and put the the IE update back on the list just to bait me, now after doing the in place I've got 5 red x errors in the eventlog I need to hash out, fun..
 
Things that make you go didn't I fix these already, thanks for the "error restore" ms.

So if I remember correctly I disable the .net optimization service and wish they made a .net strangulation service.. Never seen the Shim thing before, and the WMI error 10 seems familiar but not sure what the fix was..

----
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service reached limit of transient errors. Will shut down. Last error returned from Service Manager: 0x80029c4a.
----

Shim database version C:\Windows\Microsoft.NET\Framework\v4.0.30319 doesn't have a matching runtime directory

----

The description for Event ID 10 from source Microsoft-Windows-WMI cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


If the event originated on another computer, the display information had to be saved with the event.


The following information was included with the event:


//./root/CIMV2
SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99
0x80041003

-----
 
1. Disabled .net 2.0 don't ever remember anything needing it anyway..

2. Ran the .net cleanup tool and removed the remnants of the failed 4.0 install, again don't ever recall anything asking for 4.0, 3.5 is installed and that seems to be the only one programs squawk about..

3. Used tweaking.com's all-in-one WMI repair tool and that seems to have fixed my wmi problem...

4. Yeah!! I'm done!!! Thanks guys, take the rest of the weekend off!!
 

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

Back
Top