[SOLVED] Error 8007371B - W 7 - 64

Clade · Jan 28, 2016

Sorry. Now work.

Code:

SFCFix version 2.4.5.0 by niemiro.Start time: 2016-01-28 14:11:02.641
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Clade\Desktop\SFCFixScript.txt [1]








Collect:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 75 datablocks.
Finish time: 2016-01-28 14:11:30.019
----------------------EOF---

zcomputerwiz · Jan 28, 2016

Please manually upload the components hive by following these instructions:

Upload Components Hive

Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select copy
Note: If you get an error that the file is in use, reboot your computer and then try again.
Right-click on your Desktop and select paste
Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.

Clade · Jan 28, 2016

Follog File:

https://www.sendspace.com/file/uu1elo

zcomputerwiz · Jan 29, 2016

Follow these instructions to replace the components hive with the edited version:

View attachment 18824

Step 1 - Replace Components Hive Manually

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.

Download COMPONENTS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the COMPONENTS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

When the replacement is complete, run SURT again and attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

Clade · Jan 30, 2016

I do not know if I acted correctly. . . After transferring the said file to the target. . . I thought about restarting the equipment, but did not.

SURT worked for about 15 hours and continued into the early stage. I decided to restart the equipment and apply the SURT and within minutes SURT completed work. . .

Follows the log:

Code:

[


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-30 07:24


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI Missing Component Key	0x00000000	wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c	HKLM\Components\DerivedData\Components	
(fix)	CSI Missing Component Key	CSI Registry Item Repaired	Key created.  There will be more reports as values are replaced.
(f)	CSI Missing Identity	0x00000000	identity	wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c	
(fix)	CSI Missing Identity	CSI Registry Item Repaired	wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c
(f)	CSI F Mark Missing	0x00000002	f!wuapi.dll.mui	wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c	
(fix)	CSI F Mark Missing	CSI Registry Item Repaired	Wrote wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c\f!wuapi.dll.mui: wuapi.dll.mui
(f)	CSI Missing C Mark	0x00000000	c!83f62977fbe..098bac30654_31bf3856ad364e35_7.6.7601.19046_b721cb40f3c902b9	wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c	Missing c!
(fix)	CSI Missing C Mark	CSI Registry Item Repaired	c!83f62977fbe..098bac30654_31bf3856ad364e35_7.6.7601.19046_b721cb40f3c902b9 successfully added to wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_f2d6e8c2b5855a4c


Summary:
Seconds executed: 849
 Found 4 errors
 Fixed 4 errors
  CSI Missing Component Key Total count: 1
  Fixed: CSI Missing Component Key.  Total count: 1
  CSI Missing Identity Total count: 1
  Fixed: CSI Missing Identity.  Total count: 1
  CSI Missing C Mark Total count: 1
  Fixed: CSI Missing C Mark.  Total count: 1
  CSI F Mark Missing Total count: 1
  Fixed: CSI F Mark Missing.  Total count: 1


/CODE]

zcomputerwiz · Jan 31, 2016

Very good. Please check for updates and install any that are offered.
If the updates fail, zip up and attach C:\Windows\Logs\CBS\CBS.log with your reply.

Clade · Jan 31, 2016

worked for nine updates, but were 11 important updates. No previous Updates, December / 2015 and January / 2016, still under installation, in addition to receiving the message (normal) from Microsoft in 2nd plan, which is available to upgrade to Windows 10.

Follow CBS log:

Download CBS.zip from Sendspace.com - send big files the easy wa

zcomputerwiz · Feb 1, 2016

SFCFix Script

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

When SFCFix has completed, run SURT again and attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

Clade · Feb 1, 2016

Follow log SFCfix:

Code:

SFCFix version 2.4.9.2 by niemiro.Start time: 2016-02-01 18:33:48.302
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Clade\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\14b55b7ffc4..3a8204d39d2_31bf3856ad364e35_6.1.7601.18985_cbb537cb21fc6534 with error code 0x77CD2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2aad91adc06..cd9083158de_31bf3856ad364e35_6.3.9600.18097_474c900a165dac3e with error code 0x77CD2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_14b55b7ffc4cf7818d41f3a8204d39d2_31bf3856ad364e35_6.1.7601.18985_none_cbb537cb21fc6534 with error code 0x77CD2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_2aad91adc0628066554a5cd9083158de_31bf3856ad364e35_6.3.9600.18097_none_474c900a165dac3e with error code 0x77CD2F6D.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b549e64227cc18f9f69d3ecb7958286e_31bf3856ad364e35_6.1.7601.19045_none_d8a673b6ec957877.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_fd78b9dd344d62f98d7314d7b8806763_31bf3856ad364e35_6.1.7601.18923_none_4eb8e3a27cf103d7 with error code 0x0.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.19045_none_68b84edd92872c26 with error code 0x0.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-msxml60_31bf3856ad364e35_6.1.7601.18923_none_e688224bad7f0a37 with error code 0x0.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b549e64227c..ecb7958286e_31bf3856ad364e35_6.1.7601.19045_d8a673b6ec957877.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fd78b9dd344..4d7b8806763_31bf3856ad364e35_6.1.7601.18923_4eb8e3a27cf103d7.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_69b74df333d810b1 with error code 0x0.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18985_none_21236b21e5bf0127.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_3e54dec2067cdf4c with error code 0x0.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18923_pt-br_870d13144cc5ad21.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\14b55b7ffc4..3a8204d39d2_31bf3856ad364e35_6.1.7601.18985_cbb537cb21fc6534 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\2aad91adc06..cd9083158de_31bf3856ad364e35_6.3.9600.18097_474c900a165dac3e with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_14b55b7ffc4cf7818d41f3a8204d39d2_31bf3856ad364e35_6.1.7601.18985_none_cbb537cb21fc6534 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_2aad91adc0628066554a5cd9083158de_31bf3856ad364e35_6.3.9600.18097_none_474c900a165dac3e with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_b549e64227cc18f9f69d3ecb7958286e_31bf3856ad364e35_6.1.7601.19045_none_d8a673b6ec957877.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_fd78b9dd344d62f98d7314d7b8806763_31bf3856ad364e35_6.1.7601.18923_none_4eb8e3a27cf103d7 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.19045_none_68b84edd92872c26 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-msxml60_31bf3856ad364e35_6.1.7601.18923_none_e688224bad7f0a37 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b549e64227c..ecb7958286e_31bf3856ad364e35_6.1.7601.19045_d8a673b6ec957877.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\fd78b9dd344..4d7b8806763_31bf3856ad364e35_6.1.7601.18923_4eb8e3a27cf103d7.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_69b74df333d810b1 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18985_none_21236b21e5bf0127.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_3e54dec2067cdf4c with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18923_pt-br_870d13144cc5ad21.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.

Log CheckSUR:

https://www.sendspace.com/file/mkxsgy






Failed to process all directives successfully.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 89 datablocks.
Finish time: 2016-02-01 18:33:54.633
Script hash: x9KqOgd/zwLHWdD5vIMsmnpWOmqaASTpC7se7NbrsHg=
----------------------EOF-----------------------

zcomputerwiz · Feb 2, 2016

I'd like to take a look at the Components hive again.

SFCFix Script

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.

[sfcfixdownload]Download SFCFix[/sfcfixdownload] (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u...eric/Collect/COMPONENTS/SFCFixScript.txt?dl=1

Clade · Feb 2, 2016

Follow log:

[CODESFCFix version 2.4.9.2 by niemiro.Start time: 2016-02-02 18:48:03.645
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Clade\Desktop\SFCFixScript.txt [1]

Collect:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 89 datablocks.
Finish time: 2016-02-02 18:50:06.517
Script hash: duc6swbHUuscraK6n0RQWoNjUFLL0qXEg6xxnCShc8o=
----------------------EOF-----------------------][/CODE]

zcomputerwiz · Feb 2, 2016

Looks like the automatic upload still isn't working.

Please manually upload the components hive by following these instructions:

Upload Components Hive

Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select copy
Note: If you get an error that the file is in use, reboot your computer and then try again.
Right-click on your Desktop and select paste
Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.

Clade · Feb 2, 2016

Follow link "compomemts":

Download components.zip from Sendspace.com - send big files the easy wa

zcomputerwiz · Feb 3, 2016

Follow these instructions to replace the components hive with the edited version:

View attachment 18943

Step 1 - Replace Components Hive Manually

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.

Download COMPONENTS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the COMPONENTS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

When the replacement is complete, run SURT again and attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.

Clade · Feb 3, 2016

Follow CheckSUR log:

Code:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-02-03 19:23


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI Missing Component Key	0x00000000	amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6	HKLM\Components\DerivedData\Components	
(fix)	CSI Missing Component Key	CSI Registry Item Repaired	Key created.  There will be more reports as values are replaced.
(f)	CSI Missing Identity	0x00000000	identity	amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6	
(fix)	CSI Missing Identity	CSI Registry Item Repaired	amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6
(f)	CSI F Mark Missing	0x00000002	f!msspellcheckingfacility.e_a032e8b15b3370c9	amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6	
(fix)	CSI F Mark Missing	CSI Registry Item Repaired	Wrote amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6\f!msspellcheckingfacility.e_a032e8b15b3370c9: MsSpellCheckingFacility.exe
(f)	CSI C Mark Deployment Missing	0x00000000	c!596598cba46..0fa9b953c9f_31bf3856ad364e35_7.6.7601.19046_966cf71e7084bb7c	amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_3e54dec2067cdf4c	
(f)	CSI Missing C Mark	0x00000000	c!2aad91adc06..cd9083158de_31bf3856ad364e35_6.3.9600.18097_474c900a165dac3e	amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6	Missing c!
(fix)	CSI Missing C Mark	CSI Registry Item Repaired	c!2aad91adc06..cd9083158de_31bf3856ad364e35_6.3.9600.18097_474c900a165dac3e successfully added to amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.18097_none_5f62a3a0ff774eb6
(f)	CSI C Mark Deployment Missing	0x00000000	c!4b807419fec..bd3b3dddaa5_31bf3856ad364e35_6.1.7601.18923_9678edf918bdd776	x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18923_pt-br_870d13144cc5ad21	


Summary:
Seconds executed: 1170
 Found 6 errors
 Fixed 4 errors
  CSI Missing Component Key Total count: 1
  Fixed: CSI Missing Component Key.  Total count: 1
  CSI Missing Identity Total count: 1
  Fixed: CSI Missing Identity.  Total count: 1
  CSI Missing C Mark Total count: 1
  Fixed: CSI Missing C Mark.  Total count: 1
  CSI C Mark Deployment Missing Total count: 2
  CSI F Mark Missing Total count: 1
  Fixed: CSI F Mark Missing.  Total count: 1

This question can have to do with the .NET Framework 3.5, Windows 7 - SP 1 kb 3099862 of 08/12/2015, on which started it all?

zcomputerwiz · Feb 5, 2016

It doesn't seem to be related to that particular update.

SFCFix Script

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

View attachment SFCFix.zip

When SFCFix has completed, run the System Update Readiness Tool again.
When SURT has finished, attach CheckSUR.log with your reply.

Clade · Feb 5, 2016

SFCfix log:

[CODESFCFix version 2.4.9.2 by niemiro.Start time: 2016-02-05 19:11:41.472
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Clade\Desktop\SFCFix.zip [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.

Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\596598cba46..0fa9b953c9f_31bf3856ad364e35_7.6.7601.19046_966cf71e7084bb7c with error code 0x773C2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4b807419fec..bd3b3dddaa5_31bf3856ad364e35_6.1.7601.18923_9678edf918bdd776 with error code 0x773C2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_4b807419fec7c48727ef4bd3b3dddaa5_31bf3856ad364e35_6.1.7601.18923_none_9678edf918bdd776 with error code 0x773C2F6D.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_596598cba46689644ce840fa9b953c9f_31bf3856ad364e35_7.6.7601.19046_none_966cf71e7084bb7c with error code 0x773C2F6D.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\05965d817a44a7eaf50351fdecf6dec3e381b4644a87def6e170b896d80c3a32.
Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fde1d33a256b51308aaacd6ddf079d68375bf06f9e531e56bafdff972cc73b98 with error code 0x0.

Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\596598cba46..0fa9b953c9f_31bf3856ad364e35_7.6.7601.19046_966cf71e7084bb7c with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4b807419fec..bd3b3dddaa5_31bf3856ad364e35_6.1.7601.18923_9678edf918bdd776 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_4b807419fec7c48727ef4bd3b3dddaa5_31bf3856ad364e35_6.1.7601.18923_none_9678edf918bdd776 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_596598cba46689644ce840fa9b953c9f_31bf3856ad364e35_7.6.7601.19046_none_966cf71e7084bb7c with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\05965d817a44a7eaf50351fdecf6dec3e381b4644a87def6e170b896d80c3a32.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\fde1d33a256b51308aaacd6ddf079d68375bf06f9e531e56bafdff972cc73b98 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
RegistryScript:: directive failed to complete successfully.

Failed to process all directives successfully.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 96 datablocks.
Finish time: 2016-02-05 19:11:44.030
Script hash: uS0NBXmjMKiRxmrSP814ddqyDNAripzSlVHZexKabns=
----------------------EOF-----------------------][/CODE]

SURT log:

Code:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-02-05 19:17


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)	CSI C Mark Deployment Missing	0x00000000	c!596598cba46..0fa9b953c9f_31bf3856ad364e35_7.6.7601.19046_966cf71e7084bb7c	amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7601.19046_pt-br_3e54dec2067cdf4c	
(f)	CSI C Mark Deployment Missing	0x00000000	c!4b807419fec..bd3b3dddaa5_31bf3856ad364e35_6.1.7601.18923_9678edf918bdd776	x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18923_pt-br_870d13144cc5ad21	


Summary:
Seconds executed: 708
 Found 2 errors
  CSI C Mark Deployment Missing Total count: 2

zcomputerwiz · Feb 5, 2016

Please manually upload the components hive by following these instructions:

Upload Components Hive

Navigate to C:\Windows\System32\config
Right-click on the current COMPONENTS file and select copy
Note: If you get an error that the file is in use, reboot your computer and then try again.
Right-click on your Desktop and select paste
Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.

Clade · Feb 5, 2016

Follow Components:

Dropbox - components.zi

zcomputerwiz · Feb 8, 2016

Sorry, it doesn't look like the link works.
Could you upload the file again?

[SOLVED] Error 8007371B - W 7 - 64

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert

Well-known member

Windows Update Expert