[SOLVED] Windows Update 8007370B problems

gschaper · Dec 30, 2014

I'm running Windows 7.

My history with this problem is that Windows Update has been nonfunctional for some months, giving me the error code 8007370B when trying to use Windows Update to check for updates. At the time I first encountered this I tried using System Restore, but after that failed I eventually turned off Windows Update.

It has become more pressing to try to fix the problems recently, because a new piece of software I've acquired is unable to install a Visual C++ redistributable.

My results with the diagnostic / repair tools suggested by Microsoft support pages have been as follows:

- sfc /scannow returns the message "Windows Resource Protection could not perform the requested operation."

- Running CheckSUR failed with a number of Corrupt Identity errors. The CheckSUR log in the attached CBS.zip is typical.

- Attempting a Windows 7 repair install failed (cleanly) with a message to the effect the the install could not be carried out.

SFCFix results:

SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-12-30 10:13:08.013
Not using a script file.

AutoAnalysis::
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-w..ex4ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4.
FAILED: Could not repair missing store directory C:\Windows\winsxs\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10 with error code ERROR_INVALID_NAME.

SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: -7744
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 5
SURT total detected corruption count: 31
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2014-12-30 10:14:02.649
----------------------EOF-----------------------

Go The Power · Jan 3, 2015

Hello and welcome to the forum :)

Taking a look over the CheckSUR log there appears to be a lot of 'bitflip' corruptions inside the your COMPONENTS registry. What this basically means is a lot of the values identified as corrupt is due to the registry value having the incorrect data. Most of the time this is obvious with random symbols added, but it can also be a case of a e turning into a 7 etc.

I have highlighted some of the obvious bitflips in red below, there is most likely a lot more. This was just what I picked up by having a quick read:

Code:

(f)	CSI Missing Deployment Key	0x00000000	microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_ae85be5cbbedf284	HKLM\Components\CanonicalData\Deployments	
(f)	CSI Corrupt Identity	0xC0150017	Microsoft-WindowsmDirectShow-Capture, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, P2ocessorArchitecture=amd64, vers[B][COLOR="#FF0000"])[/COLOR][/B]onScope=NonSxS	amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6.manifest	amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6	
(f)	CSI Corrupt Identity	0xC0150017	Microsoft-Windows-IIS-Authorizati/n-Deployment-LanguagePack, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64,[COLOR="#FF0000"][B]`[/B][/COLOR]versionScope=NonSxS	amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_s3080a925dfb8146	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_s3080a925dfb8146.manifest	amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_s3080a925dfb8146	
(f)	CSI Corrupt Identity	0xC0150019	M[COLOR="#FF0000"][B])[/B][/COLOR]crosoft-Windows-Help-Speech.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31[COLOR="#FF0000"][B]"[/B][/COLOR]f3856ad364e35, rocessorArchitecture=amd64, versionScope=NonSxS	amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8.manifest	amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8	
(f)	CSI Corrupt Identity	0xC0150017	Microsoft[COLOR="#FF0000"][B]m[/B][/COLOR]Windows-ContentmFilter-RTF, Cul[COLOR="#FF0000"][B]4[/B][/COLOR]ure=neutral, Version=7.0.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=N/nSxS	x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4	Bad identity
(f)	CSI Manifest Missing	0x00000002	x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4.manifest	x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4	
(f)	CSI Corrupt Identity	0xC0150016	Microsoft-Windows-Wlan-Extension[COLOR="#FF0000"][B].[/B][/COLOR]esources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e3[COLOR="#FF0000"][B]u[/B][/COLOR], ProcessorArchitecture=amd64, versionScope=Non[COLOR="#FF0000"][B][/B][/COLOR]xS	amd64_microsoft-windows-w..ex[COLOR="#FF0000"][B]4[/B][/COLOR]ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-w..ex[COLOR="#FF0000"][B]4[/B][/COLOR]ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e.manifest	amd64_microsoft-windows-w..ex[COLOR="#FF0000"][B]4[/B][/COLOR]ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_0e055f69dcbe16bf	amd64_microsoft-windows-b..mepremium.resources_31bf3856ad364e35_6.1.7600.16385_en-us_521ac6ec13124574	
(f)	CSI C Mark Deployment Missing	0x00000000	c!32freee420a..37fa36u7889_31bf3856ad364e35_6.1.7600.20498_d09a902cd50ccd70	wow64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7600.20498_none_109e822ec1bb2dae	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_cfca0194ff453bb0	amd64_microsoft-windows-b..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_cfca0194ff453bb0	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!tpm.inf_31bf3856ad364e35_6.1.7600.16385_0817dcde20d8acd1	amd64_tpm.inf_31bf3856ad364e35_6.1.7600.16385_none_0817dcde20d8acd1	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_0e055f69dcbe16bf	amd64_microsoft-windows-b..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_0e055f69dcbe16bf	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_cfca0194ff453bb0	amd64_microsoft-windows-b..-ultimate.resources_31bf3856ad364e35_6.1.7600.16385_en-us_60159d8e2e7b2507	
(f)	CSI C Mark Deployment Missing	0x00000000	c!b231cb54cb6n.2e55789ee9d_31"f3856ad364e35_6.1.7600.16402_fd1004ea638f1ad1	amd64_b231cb54cb6ac985c2c4f2e55789ee9d_31bf3856ad364e35_6.1.7600.16402_none_fd1004ea638f1ad1

When this many bitflips are present inside a registry hive it raises a lot of concerns of memory (RAM) failure.

Please follow the instructions for MemTest86+, for atleast 10 passes. Let me know the results.

gschaper · Jan 6, 2015

I was finally able to take the system out of use long enough to run the requested passes with Memtest. No errors were reported. The system has in the past run for an extended period with bad RAM, long since replaced. I can't say with any certainty how that period compares with the start of the Windows Update issues. As noted in the first post, those have been around for a long time.

Go The Power · Jan 6, 2015

Most likely when you had bad RAM it would of causes these bitflips inside the COMPONENTS hive. I will be honest with you here, it would take me countless hours to try and get this COMPONENTS hive repaired again and most likely some will be missed in process. As I said bitflips can be quite hard to spot, your best option from here would be to do a fresh install of Windows. You can try a repair install of Windows first, but this not always successful.

I hate going down this path, but with this many corruptions it is not realistic to be trying to fix.

Alex

gschaper · Jan 6, 2015

I see. Thank you.

Go The Power · Jan 7, 2015

Sorry it had to come to this, but unfortunately repairing the hive was not an option.

Alex

gschaper · Jan 7, 2015

I suppose my obvious disappointment that nothing can be done is a result of my not understanding the scan results, and having just looked at the fact that CheckSUR was reporting just 5 corrupt keys. I guess that it is just the tip of the iceberg?

Out of curiosity, how does the SFCFix scan come to its total, by scanning CBS.log ? It looked to me like a lot of those corrupted keys were just duplicates from multiple attempts that I'd made to run the Microsoft tools before bringing the problem to the forums.

In any event, I appreciate the work done to investigate it.

Go The Power · Jan 8, 2015

If it was only just 5 bitflips I would of tried to repair it with you, but there are 30 issues SURT has detected:

Code:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2014-12-30 00:51

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)	CSI Payload File Missing	0x00000000	mdmpp.inf	amd64_mdmpp.inf_31bf3856ad364e35_6.1.7600.16385_none_a9d2002feb81fa56	
(f)	CSI Payload File Missing	0x00000000	Amd64\smpclrc1.gpd	amd64_prnsa002.inf_31bf3856ad364e35_6.1.7600.16385_none_02a32ac8d56280f6	
(f)	CSI Payload File Missing	0x00000000	Amd64\smpclrc1.dll	amd64_prnsa002.inf_31bf3856ad364e35_6.1.7600.16385_none_02a32ac8d56280f6	
(f)	CSI Payload File Missing	0x00000000	Amd64\sml8x0.gpd	amd64_prnsa002.inf_31bf3856ad364e35_6.1.7600.16385_none_02a32ac8d56280f6	
(f)	CSI Payload File Missing	0x00000000	Amd64\sml8x0.ppd	amd64_prnsa002.inf_31bf3856ad364e35_6.1.7600.16385_none_02a32ac8d56280f6	
(f)	CSI Payload File Missing	0x00000000	System.Web.DynamicData.Design.dll	amd64_netfx35linq-system....dynamicdata.design_31bf3856ad364e35_6.1.7600.16385_none_f25d31ff0863a15e	
(f)	CSI Payload File Missing	0x00000000	System.Web.DynamicData.dll	amd64_netfx35linq-system.web.dynamicdata_31bf3856ad364e35_6.1.7600.16385_none_67cd22b90fc43ea8	
(f)	CSI Payload File Missing	0x00000000	System.Web.Entity.Design.dll	amd64_netfx35linq-system.web.entity.design_31bf3856ad364e35_6.1.7600.16385_none_f4f038842cb783b0	
(f)	CSI Payload File Missing	0x00000000	System.Web.Entity.dll	amd64_netfx35linq-system.web.entity_31bf3856ad364e35_6.1.7600.16385_none_91237576aca0d004	
(f)	CSI Payload File Missing	0x00000000	mdmpsion.inf	amd64_mdmpsion.inf_31bf3856ad364e35_6.1.7600.16385_none_5f62ca049c3c9107	
(f)	CSI Missing Identity	0x00000000	identity	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(f)	CSI Could Not Open file	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(w)	CSI Replacement File: CreateFile Failed	0x0000007B	winsxs\Manifests\x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10.manifest	x86_netfx-msbuild_targetfiles_b03f5f7f11d50a3a_6.1.7600.16385_none_61"8cce839a2db10	
(f)	CSI Missing Deployment Key	0x00000000	microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_ae85be5cbbedf284	HKLM\Components\CanonicalData\Deployments	
(f)	CSI Corrupt Identity	0xC0150017	Microsoft-WindowsmDirectShow-Capture, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, P2ocessorArchitecture=amd64, vers)onScope=NonSxS	amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6.manifest	amd64_microsoft-windows-directshow-capture_31bf3856ad364e35_6.1.7600.16385_none_14ce1tda393bbcc6	
(f)	CSI Corrupt Identity	0xC0150017	Microsoft-Windows-IIS-Authorizati/n-Deployment-LanguagePack, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64,`versionScope=NonSxS	amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_s3080a925dfb8146	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_s3080a925dfb8146.manifest	amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_s3080a925dfb8146	
(f)	CSI Corrupt Identity	0xC0150019	M)crosoft-Windows-Help-Speech.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31"f3856ad364e35, rocessorArchitecture=amd64, versionScope=NonSxS	amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8.manifest	amd64_microsoft-windows-help-speech.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c031aba69x8a59f8	
(f)	CSI Corrupt Identity	0xC0150017	MicrosoftmWindows-ContentmFilter-RTF, Cul4ure=neutral, Version=7.0.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=N/nSxS	x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4	Bad identity
(f)	CSI Manifest Missing	0x00000002	x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4.manifest	x86_microsoftmwindows-contentmfilter-rtf_31bf3856ad364e35_7.0.7600.16385_none_7ffdb5b2396b88d4	
(f)	CSI Corrupt Identity	0xC0150016	Microsoft-Windows-Wlan-Extension.esources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e3u, ProcessorArchitecture=amd64, versionScope=NonxS	amd64_microsoft-windows-w..ex4ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e	Bad identity
(f)	CSI Manifest Missing	0x00000002	amd64_microsoft-windows-w..ex4ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e.manifest	amd64_microsoft-windows-w..ex4ension.resource3_31bf3856ad364e35_6.1.7600.16385_en-us_9a69634299e2277e	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_0e055f69dcbe16bf	amd64_microsoft-windows-b..mepremium.resources_31bf3856ad364e35_6.1.7600.16385_en-us_521ac6ec13124574	
(f)	CSI C Mark Deployment Missing	0x00000000	c!32freee420a..37fa36u7889_31bf3856ad364e35_6.1.7600.20498_d09a902cd50ccd70	wow64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7600.20498_none_109e822ec1bb2dae	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_cfca0194ff453bb0	amd64_microsoft-windows-b..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_cfca0194ff453bb0	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!tpm.inf_31bf3856ad364e35_6.1.7600.16385_0817dcde20d8acd1	amd64_tpm.inf_31bf3856ad364e35_6.1.7600.16385_none_0817dcde20d8acd1	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_0e055f69dcbe16bf	amd64_microsoft-windows-b..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_0e055f69dcbe16bf	
(f)	CSI C Mark Deployment Not Marked	0x00000000	c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_cfca0194ff453bb0	amd64_microsoft-windows-b..-ultimate.resources_31bf3856ad364e35_6.1.7600.16385_en-us_60159d8e2e7b2507	
(f)	CSI C Mark Deployment Missing	0x00000000	c!b231cb54cb6n.2e55789ee9d_31"f3856ad364e35_6.1.7600.16402_fd1004ea638f1ad1	amd64_b231cb54cb6ac985c2c4f2e55789ee9d_31bf3856ad364e35_6.1.7600.16402_none_fd1004ea638f1ad1	

Summary:
Seconds executed: 103
[B][COLOR="#FF0000"] Found 30 errors[/COLOR][/B]

If we were to have a look at the COMPONENTS hive itself and scan it for bit flips, I am certain this number would double or triple.

Out of curiosity, how does the SFCFix scan come to its total, by scanning CBS.log ? It looked to me like a lot of those corrupted keys were just duplicates from multiple attempts that I'd made to run the Microsoft tools before bringing the problem to the forums.

SFCFix scans the CBS.log and CheckSur log and works out the calculations from there. But there is a minor bug which the developer is working on, as you can see here
CBS & SFC total detected corruption count: -7744

gschaper · Jan 8, 2015

Understood. Thanks for the information.

Go The Power · Jan 9, 2015

Your welcome.

[SOLVED] Windows Update 8007370B problems

gschaper

Member

Go The Power

Senior Administrator, Windows Update Expert, Contributor

gschaper

Member

Go The Power

Senior Administrator, Windows Update Expert, Contributor

gschaper

Member

Go The Power

Senior Administrator, Windows Update Expert, Contributor

gschaper

Member

Go The Power

Senior Administrator, Windows Update Expert, Contributor

gschaper

Member

Go The Power

Senior Administrator, Windows Update Expert, Contributor