8007370B Windows update encountered an unknown error

[Falskoren]

1 Ran SURT Windows6.1-KB947821-v34-x64.msu
Gray window successful

2. SFC Scan Failed Option 2 Elevated Dos Box in PDF

3. Windows Update Error Codes
Screenshot in PDF for windows Update

4. Log Collection
See attached zip

Additional notes:
Turn windows features On/Off is blank
Uninstall or check installed updates is blank

 

[NoelDP]

You appear to have a large number of bitflips in the registry - here's the CheckSUR summary...

Seconds executed: 348
 Found 63 errors
 Fixed 25 errors
  CSI Could Not Open file Total count: 1
  CSI Catalog Missing Total count: 4
  Fixed: CSI Catalog Missing.  Total count: 4
  CSI Missing Deployment Key Total count: 27
  CSI Missing Identity Total count: 9
  Fixed: CSI Missing Identity.  Total count: 7
  CSI Corrupt Identity Total count: 3
  Fixed: CSI Corrupt Identity.  Total count: 2
  CSI Missing C Mark Total count: 4
  Fixed: CSI Missing C Mark.  Total count: 4
  CSI C Mark Deployment Missing Total count: 6
  CSI Replacement File: CreateFile Failed Total count: 17
  CSI Payload File Missing Total count: 1
  CSI F Mark Missing Total count: 8
  Fixed: CSI F Mark Missing.  Total count: 8

almost all of these errors are caused by bitflips - which probably means that other areas are also damaged.

There is no point in attempting to cure the remaining problems unless the cause of the bitflips is first eliminated.
This is usually the result of failing RAM.

Please follow the instructions here... http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html and see what it reports.

 

[Falskoren]

Checked the Memory, pulled out 1 bad stick.
Redid Procedure
Attachments included.

 

[NoelDP]

OK - in that case, I need to see your COMPONENTS registry hive...


I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

 

[Falskoren]

https://drive.google.com/file/d/0BwViZ6Vt5U8gMUR0ckdXM3hKZWc/view?usp=sharing

 

[NoelDP]

I've uploaded a file - fknaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]COPY "%userprofile%\desktop\fknaa\COMPONENTS" C:\Windows\System32\config[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"] [/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"].

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

 

[Falskoren]

AS requested

Your zip did not create the folder for your path on the script, so i created it and put your components in.
Ran the 3 commands without error.
Attached is just the CheckSUR unless you ewant the whole shooting match

 

[NoelDP]

There are a fair number of errors appearing now - I've attempted to fix most of them, but the fix may bring a lot more errors to light


We'll see how this lot go before working out where to go next...

I've uploaded a file - fknab.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]COPY "%userprofile%\desktop\fknab\COMPONENTS" C:\Windows\System32\config[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"] [/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"].

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

 

[Falskoren]

Much closer windows update working

Performed steps, ran the sequence 1-4 as you will notice windows update is working.
SFC /scannow still reports an error so included the entire CBS.
will let you knwo what happens after the first 30 updates run through.

 

[Falskoren]

Windows update works

Looks like you fixed it, both the update history and windows features work again.
It does still have errors when you run SFC /Scannow but if you want i can move that to a different thread.
thank you

 

[NoelDP]

Please post the latest CBS.log after another SFC scan - then post another CheckSUR report, as I suspect that there will still be significant errors in that also

 

[Falskoren]

As Requested

Posted files as requested

 

[NoelDP]

the SFC scan shows this...

 Line 44119: 2014-12-10 20:57:45, Info                  CSI    00000388 [SR] Repairing 3 components
 Line 44120: 2014-12-10 20:57:45, Info                  CSI    00000389 [SR] Beginning Verify and Repair transaction
 Line 44125: 2014-12-10 20:57:45, Info                  CSI    0000038c [SR] Cannot verify component files for Microsoft-Windows-TextServicesFramework-msctf, Version = 6.1.7600.16385, 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)
 Line 44126: 2014-12-10 20:57:45, Info                  CSI    0000038d [SR] Cannot repair member file [l:24{12}]"Ph3xIBC5.inf" of ph3xibc5.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 44131: 2014-12-10 20:57:45, Info                  CSI    00000390 [SR] Cannot verify component files for WinINet.ETW, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

The CheckSUR scan shows this...

Checking Component Store
(f) CSI Payload File Missing 0x00000000 Ph3xIBC5.inf amd64_ph3xibc5.inf_31bf3856ad364e35_6.1.7600.16385_none_9e7d0270e1def2ea 
(f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_e86e6b9f25302ba0 
(f) CSI Catalog Missing 0x00000002 ff7d36516d1434f0afe881d2ba1d3660b8ab2595897a308e4fa4d5e1e26bd258.cat win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_e86e6b9f25302be0 Missing catalog or invalid CatalogThumprint
(fix) CSI Catalog Missing CSI File Replaced File: ff7d36516d1434f0afe881d2ba1d3660b8ab2595897a308e4fa4d5e1e26bd258.cat From: C:\windows\servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Shell-WinIP-Package~31bf3856ad364e35~amd64~et-EE~7.1.7601.16492.cat
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_dcdeaf1ab07f6937 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_f161491b8d26cb27 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_fed328da29f6220a HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eeaea00f212a4f51 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_fde02e301753d31c HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_fb10d8de77ed2588 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eee3432b21035dac HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_ef8fa59929d753fb HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_f88c3390e734fb46 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_fd4cb07e98bc1f17 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_f16cb41cbb01056b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_f53dca606dd39bff HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 873033b2f15..d1715f94402_31bf3856ad364e35_6.1.7601.17720_86d856ca0a13c371 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_f33b39c3b072b729 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_ff8af78629849adc HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_ee889ac5213aba75 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_2e4e27eca6282ffd HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_9c5f7805355a970a HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_f07f79af8db75b4b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_edcef0d72b035dd0 HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Missing 0x00000000 c!f5124a5f846..a916910508c_31bfs856ad364e35_6.1.7601.17720_dd338e1174e72b50 amd64_f5124a5f846b1b9d5d6cba916910508c_31bf3856ad364e35_6.1.7601.17720_none_dd338e1174e72b50 
(f) CSI C Mark Deployment Missing 0x00000000 c!13d3e746f2a..962eeb153e2_31bf3856ad360e35_6.1.7601.21855_fafba71daf621235 amd64_13d3e746f2a0446080beb962eeb153e2_31bf3856ad364e35_6.1.7601.21855_none_fafbe71daf625235 
(f) CSI C Mark Deployment Missing 0x00000000 c!c982b74b248..9ef2295ae55_31bf3856ad364e35_6.1.7601.17720_0409b118eb5f6054 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.17720_bg-bg_970e2cb70b921705

I'll try posting fixes later.