[SOLVED] Windows Update - Erro 80070002

Canad · Jun 8, 2015

Hello!
I am Brazilian and I have some difficulty with English, so I will use a translator. Sorry for any mistake of writing.

I have Windows Seven 64-bit Operating System.
Unless I am mistaken in January / 2015 realized that the Windows Update no longer worked, been giving the error 80070002.
Nothing decided to Restore Point.
I tried the fix suggested by Windows itself, that several times, and nothing resolved.
I searched the internet and followed several suggestions of Microsoft Windows, such as:
- Some use of fasteners
- Delete the file SoftwareDistribution
- Attempt to sfc / scannow (but it was not possible as it gave information "Windows Resource Protection can not perform the requested operation by.").
- And other suggestions.
It was during this research that recently found this site and decided to try to help, because the posts read by me have confidence that the subject is treated seriously and with certainty.

As of today (06/18/2015 - 18:10 hours), I downloaded the file and the SFCfix.exe performed, as directed.
At the end, it was present the following log:

----------------------------------------------------

SFCFix version 2.4.4.0 by niemiro.
Start time: 2015-06-08 18:11:24.554
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ncdprop.resources_31bf3<56ad364e35_6.1.7600.16385_ar-sa_f27afc8833b8f0a4
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-a..olicy-snapmn-native_31bf3856ad364e35_6.1.7600.16385_none_9b6078314990d8e8.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-dns-client.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_8453bbf133929cf1.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-i..er-engine.resources_31bf3856ad364e35_6.1.7600.16385_bg-bg_b4b71fbee3ef371a.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_11.2.=600.17280_none_cfaa7e32fdb2b96f.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoft-windows-t..minsnapin.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_736c71ed33c65e5c.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoft-windows-wab-core.resources_31bf7856ad364e35_6.1.7600.16385_ar-sa_1b8ec20933dd4c30.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoft-windows-wmadmoe_31bf3856ad364e35_6.1.7640.16385_none_8696c88e7f02ab7b.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7g0cee9f32465.

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

Successfully processed all directives.
SFCFix version 2.4.4.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-06-08 18:14:55.336
----------------------EOF-----------------------

----------------------------------------------------------------------------------

I await response as soon as possible.
Also follows the CBS.zip folder, log and error screen.

Canad

BrianDrab · Jun 10, 2015

Hi and welcome to Sysnative. Please do the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Canad · Jun 12, 2015

BrianDrab.
Thank you for having responded to my message.
I downloaded the file and performed.
Follows the Checksur.log file as requested.

-----------------------------------------------

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-06-12 19:22

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 x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465 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 x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465
(fix) CSI Missing Identity CSI Registry Item Repaired x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465
(f) CSI F Mark Missing 0x00000002 f!normalization.dll x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465
(fix) CSI F Mark Missing CSI Registry Item Repaired Wrote x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465\f!normalization.dll: normalization.dll
(f) CSI Mismatched Identity 0x00000000 appid wiaca00i.inf_31bf3856ad364e35_6.1.7600.16385_9dff40bd2f903760 appid and keyform do not match; appid is wrong.
(f) CSI Corrupt Deployment Keyform 0x00000000 appid wiaca00d.inf_31bf3856ad364e35_6.1.7600.16385_=b51e5b3b1f90953 appid and keyform do not match; keyform is wrong.
(f) CSI Corrupt Identity 0xC0150017 NetFx35Linq-System.Web.Extensions, Culture=neutral, Version=6.1.7601.18138, PubligKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionWcope=NonSxS amd64_netfx35linq-system.web.extensions_31bf3856ad364e35_6.1.7601.18138_none_2c8df1e901d6b014 Bad identity
(fix) CSI Corrupt Identity CSI Registry Item Repaired amd64_netfx35linq-system.web.extensions_31bf3856ad364e35_6.1.7601.18138_none_2c8df1e901d6b014
(f) CSI Corrupt Identity 0x00000000 identity x86_microsoft-windows-video-for-windows_31bf3856ad364e35_6.1.7600.16385_none_920846ceea15a95a identity and keyform do not match; identity is wrong.
(fix) CSI Corrupt Identity CSI Registry Item Repaired x86_microsoft-windows-video-for-windows_31bf3856ad364e35_6.1.7600.16385_none_920846ceea15a95a
(f) CSI Corrupt Identity 0x00000000 identity amd64_66094704a5fd23dc143aedcb1fc0bd96_b03f5f7f11d50a3a_6.1.7601.18523_none_c6a12185a133b8b1 identity and keyform do not match; identity is wrong.
(fix) CSI Corrupt Identity CSI Registry Item Repaired amd64_66094704a5fd23dc143aedcb1fc0bd96_b03f5f7f11d50a3a_6.1.7601.18523_none_c6a12185a133b8b1
(f) CSI Corrupt Identity 0x00000000 identity amd64_avc.inf_31bf3856ad364e35_6.1.7600.16385_none_084e3f0eabcf1e24 identity and keyform do not match; identity is wrong.
(fix) CSI Corrupt Identity CSI Registry Item Repaired amd64_avc.inf_31bf3856ad364e35_6.1.7600.16385_none_084e3f0eabcf1e24
(f) CSI Payload File Missing 0x00000000 prnrc005.inf_loc amd64_prnrc005.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f57ee14c6ceb463c
(f) CSI F Mark Missing 0x00000002 f!directdb.dll amd64_microsoft-windows-mail-app_31bf3856ad364e35_6.1.7601.17514_none_4f7e32f76654bd3c
(fix) CSI F Mark Missing CSI Registry Item Repaired Wrote amd64_microsoft-windows-mail-app_31bf3856ad364e35_6.1.7601.17514_none_4f7e32f76654bd3c\f!directdb.dll: DirectDB.dll
(f) CSI F Mark Missing 0x00000002 f!green_bubbles.htm_242729eeb480236b amd64_microsoft-windows-mail-app_31bf3856ad364e35_6.1.7601.17514_none_4f7e32f76654bd3c
(fix) CSI F Mark Missing CSI Registry Item Repaired Wrote amd64_microsoft-windows-mail-app_31bf3856ad364e35_6.1.7601.17514_none_4f7e32f76654bd3c\f!green_bubbles.htm_242729eeb480236b: Green Bubbles.htm
(f) CSI Corrupt Identity 0x00000000 identity msil_system.web.extensions_31bf3856ad364e35_6.1.7601.22306_none_3dd5cf0815634455 identity and keyform do not match; identity is wrong.
(fix) CSI Corrupt Identity CSI Registry Item Repaired msil_system.web.extensions_31bf3856ad364e35_6.1.7601.22306_none_3dd5cf0815634455
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-i..er-engine.resources_31bf3856ad364e35_6.1.7600.16385_bg-bg_b4b71fbee3ef371a identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Identity 0xC0150016 Microsoft-Windows-TPM-AdminSnapin.Resources, Culture=ar-SA, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonS|S x86_microsoft-windows-t..minsnapin.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_736c71ed33c65e5c Bad identity
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-t..minsnapin.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_736c71ed33c65e5c.manifest x86_microsoft-windows-t..minsnapin.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_736c71ed33c65e5c
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7g0cee9f32465 identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-wab-core.resources_31bf7856ad364e35_6.1.7600.16385_ar-sa_1b8ec20933dd4c30 identity and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 wiaca00f.inf_31bf3856ad364e35_6.1.7600.16385_9c640a1de4358225 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 4291db5a9b1..6a84afeefd4_b03f5f7f11d50a3a_6.1.7601.18410_a9ffbf3a8da96c1c HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-s..agement-policytools_31bf3856ad364e75_6.1.7600.16385_none_249d5e7365224ed8 identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-dns-client.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_8453bbf133929cf1 identity and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 1ad5a19b387..f9dcf94da71_b77a5c561934e089_6.1.7601.18410_b3c4b96dd50586f0 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 wiaca00d.inf_31bf3856ad364e35_6.1.7600.16385_9b51e5b3b1f90953 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 35e7f55fcae..77a6df7964e_b03f5f7f11d50a3a_6.1.7601.18532_311895cfa716adb7 HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-a..olicy-snapmn-native_31bf3856ad364e35_6.1.7600.16385_none_9b6078314990d8e8 identity and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 1c2352cacec..be05cd4c92f_b03f5f7f11d50a3a_6.1.7601.22733_594a2fc4d6adc45f HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 0cda7b0da49..76eada96003_31bf3856ad364e35_6.1.7601.21733_01790ff8d4991aca HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 1d496f993d5..2a384b7f87f_31bf3856ad364e35_6.1.7601.22653_bc83718ba2150dd0 HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 0e9454fbac4..eac54ced60e_b77a5c561934e089_6.1.7601.18586_7e7e9fd0b91346e6 HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-ncdprop.resources_31bf3<56ad364e35_6.1.7600.16385_ar-sa_f27afc8833b8f0a4 identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-IE-VGX,$Culture=neutral, Version=11.2.9600.17280, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_11.2.=600.17280_none_cfaa7e32fdb2b96f Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_11.2.=600.17280_none_cfaa7e32fdb2b96f.manifest amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_11.2.=600.17280_none_cfaa7e32fdb2b96f
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-wmadmoe_31bf3856ad364e35_6.1.7640.16385_none_8696c88e7f02ab7b identity and keyform do not match; keyform is wrong.
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c wow64_microsoft-windows-p..structure.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_cd022e1d76b01875 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c successfully added to wow64_microsoft-windows-p..structure.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_cd022e1d76b01875
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c x86_microsoft-windows-label.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_e83a48187233c491 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c successfully added to x86_microsoft-windows-label.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_e83a48187233c491
(f) CSI Missing C Mark 0x00000000 c!03750db1828..bfb1b08ff4f_31bf3856ad364e35_6.1.7601.18409_d46690cd7039c0c4 amd64_03750db1828f79cdf5292bfb1b08ff4f_31bf3856ad364e35_6.1.7601.18409_none_d46690cd7039c0c4 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!03750db1828..bfb1b08ff4f_31bf3856ad364e35_6.1.7601.18409_d46690cd7039c0c4 successfully added to amd64_03750db1828f79cdf5292bfb1b08ff4f_31bf3856ad364e35_6.1.7601.18409_none_d46690cd7039c0c4
(f) CSI Missing C Mark 0x00000000 c!windowsfoundation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739474c x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!windowsfoundation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739474c successfully added to x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465
(f) CSI Missing C Mark 0x00000000 c!windowsfoundation_31bf3856ad364e35_6.1.7600.16385_5f2ecc1aaa4ac3b2 x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!windowsfoundation_31bf3856ad364e35_6.1.7600.16385_5f2ecc1aaa4ac3b2 successfully added to x86_netfx-normalization_dll_b03f5f7f11d50a3a_6.1.7600.16385_none_b0b7c0cee9f32465
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c amd64_microsoft-windows-m..ilerepair.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_a06faa45e015ccba Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c successfully added to amd64_microsoft-windows-m..ilerepair.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_a06faa45e015ccba
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_c954e5281446299d x86_microsoft-windows-c..andprompt.resources_31bf3856ad364e35_6.1.7600.16385_en-us_7f58345bf33dc87d Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_c954e5281446299d successfully added to x86_microsoft-windows-c..andprompt.resources_31bf3856ad364e35_6.1.7600.16385_en-us_7f58345bf33dc87d
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c wow64_microsoft-windows-m..ents-mdac.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_39ab2784dd4a3f4c Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c successfully added to wow64_microsoft-windows-m..ents-mdac.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_39ab2784dd4a3f4c
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c amd64_microsoft-windows-upnpssdp.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_fd68769aa58f6dce Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5f90bf2c45fcb11c successfully added to amd64_microsoft-windows-upnpssdp.resources_31bf3856ad364e35_6.1.7600.16385_pt-br_fd68769aa58f6dce

Summary:
Seconds executed: 928
Found 43 errors
Fixed 19 errors
CSI Manifest Missing Total count: 2
CSI Missing Component Key Total count: 1
Fixed: CSI Missing Component Key. Total count: 1
CSI Missing Deployment Key Total count: 9
CSI Corrupt Deployment Keyform Total count: 1
CSI Corrupt Component Keyform Total count: 8
CSI Missing Identity Total count: 1
Fixed: CSI Missing Identity. Total count: 1
CSI Corrupt Identity Total count: 7
Fixed: CSI Corrupt Identity. Total count: 5
CSI Mismatched Identity Total count: 1
CSI Missing C Mark Total count: 9
Fixed: CSI Missing C Mark. Total count: 9
CSI Payload File Missing Total count: 1
CSI F Mark Missing Total count: 3
Fixed: CSI F Mark Missing. Total count: 3

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-t..minsnapin.resources_31bf3856ad364e35_6.1.7600.16385_er-sa_736c71ed33c65e5c.manifest
winsxs\manifests\amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_11.2.=600.17280_none_cfaa7e32fdb2b96f.manifest

-----------------------------------------------------------------------------------View attachment CheckSUR.log View attachment CheckSUR.log

BrianDrab · Jun 12, 2015

Thank you. Please run it one more time and provide the new log.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Canad · Jun 14, 2015

BrianDrab.
Clarify something: on Friday made use of KB947821 tool; yesterday (Saturday), my computer gave an error at startup, slowed and then asked to repair, which allowed, but returned message that failed to redress. After four attempts, the computer normally opened and gave two blue screens. Finally I hung up and waited ten minutes. I restarted the computer and it opened normally and fast, been operating normally rest of the day. Today he opened normally and fast.
It has something to do using the tool KB947821 what happened or was something isolated, generated by some other problem?
I ask this because you asked me to use the tool KB947821 again.
Await answers.

Canad

BrianDrab · Jun 14, 2015

The System Update Readiness Tool (KB947821) is designed to fix corruptions/missing files. You had many corruptions which were fixed. That may have contributed to your problems although I don't know why it would.

We do need you to run this another time however.

Canad · Jun 15, 2015

BrianBrad
This afternoon again had problems connecting the computer. He caught at startup. I hung up and reconnect, presented screen to repair startup. During repair, asked to restore the Restore Point, as accepted. Finally, he presented screen saying that the restoration was successful and the startup repair as well. Then he opened normally. I turned off the computer and waited ten minutes. The computer connected normally and is operating normally so far, as of 19:53 minutes.
I again ran the System Update Readiness Tool (SUR). Follows the Checksur.log file.

Thank you for your attention, so far.

CanadView attachment CheckSUR.log

BrianDrab · Jun 15, 2015

It looks like when you restored to the restore point that we lost some of the fixes that we did. So please do the following one more time. Thanks.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Canad · Jun 15, 2015

BrianBrad
Just run again the System Update Readiness Tool (SUR). Follows the new log.

grateful

Canad
View attachment CheckSUR.log

BrianDrab · Jun 15, 2015

Perfect. We have 24 errors we need to correct. Much of it is registry corruption. I will need your components hive to resolve. Please do the following.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.

Canad · Jun 15, 2015

BrianDrab
Follow the link requested:

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

I will need to leave but come back tomorrow if the computer starts (hshshs)

Good evening.

Canad

BrianDrab · Jun 16, 2015

This may take a few rounds of fixing. I believe I fixed most of them though. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
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

Step#2 - Replace Manually
1. Download COMPONENTSNEW.ZIP and save to your desktop.
2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
3. Now we have the COMPONENTS file that we will be using to replace your current one.
4. Navigate to C:\Windows\System32\config
5. 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.
6. Take the file from the Componentsnew folder on your desktop and paste it into C:\Windows\System32\config

Thank you.

Canad · Jun 16, 2015

BrianDrab
Good afternoon!
The computer booted normally this morning.
Performed steps 1 and 2 in the order you instructed.
Then I restarted the computer and it opened normally.
Follows the result log.

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-16 11:49:18.140
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Nadur\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_prnrc005.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f57ee14c6ceb463c

Successfully copied file C:\Users\Nadur\AppData\Local\niemiro\Archive\winsxs\amd64_prnrc005.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f57ee14c6ceb463c\prnrc005.inf_loc to C:\Windows\winsxs\amd64_prnrc005.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f57ee14c6ceb463c\prnrc005.inf_loc.

Successfully restored ownership for C:\Windows\winsxs\amd64_prnrc005.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f57ee14c6ceb463c
Successfully restored permissions on C:\Windows\winsxs\amd64_prnrc005.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f57ee14c6ceb463c
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-06-16 11:49:18.686
Script hash: frWSS94txw4ZjWlcOO7eMatEHWfIs87Tuuxkw1MxHNU=
----------------------EOF-----------------------

Thank you.

Canad

BrianDrab · Jun 16, 2015

Excellent job. Let's see what's left to fix. Please run the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Canad · Jun 16, 2015

BrianDrab
In terms of gratitude, I do have a lot to thank him because while many told me to forget, it was not to update the windows or simply format the computer you in a few instructions and guidelines, fixed the problem. After all, IT is not for anyone, it is for those who know, and you seem to know very much. Many thanks for the help so far.

After my last post, I left the computer on and had to leave, but now return in the late afternoon, already I found updates on Windows Update. I have checked and there are over 1,205 mb updates. As my internet is not very good, temporarily deactivated Windows Update to be able to navigate and pass this message. Can let upgrade all at once or gradually let go?
Spun again, SUR, as instructed. Follow the log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-06-16 17:33

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Mismatched Identity 0x00000000 appid wiaca00i.inf_31bf3856ad364e35_6.1.7600.16385_9dff40bd2f903760 appid and keyform do not match; appid is wrong.
(f) CSI Missing Deployment Key 0x00000000 4291db5a9b1..6a84afeefd4_b03f5f7f11d50a3a_6.1.7601.18410_a9ffbf3a8da96c1c HKLM\Components\CanonicalData\Deployments

Summary:
Seconds executed: 724
Found 2 errors
CSI Missing Deployment Key Total count: 1
CSI Mismatched Identity Total count: 1

Canad

BrianDrab · Jun 16, 2015

I would do a batch at a time to make sure things are working properly. We do have two errors that we still need to fix. I'll be back with you shortly to fix those.

BrianDrab · Jun 16, 2015

This should fix one more of the issues. Please do the following. I spent a couple hours trying to work out the last missing deployment key and haven't been able to but hopefully this won't affect your windows updates.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

Canad · Jun 17, 2015

BrianDrab
Good Morning!
I ran the file as requested.
Follow the log:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-17 11:24:16.738
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Nadur\Desktop\SFCScript.txt [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wiaca00i.inf_31bf3856ad364e35_6.1.7600.16385_9dff40bd2f903760.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wiaca00i.inf_31bf3856ad364e35_6.1.7600.16385_9dff40bd2f903760.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wiaca00i.inf_31bf3856ad364e35_6.1.7600.16385_9dff40bd2f903760.
RegistryScript:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2015-06-17 11:24:17.128
Script hash: pQsWrt2oUaKRfchrmwkPvKOc2rK2L1wDRLk/hrTWN6E=
----------------------EOF-----------------------

Canad

BrianDrab · Jun 17, 2015

Let me know how your Windows Updates work. Thanks.

Canad · Jun 17, 2015

BrianDrab
Excuse me, but did not quite catch the last post.
However, I will give an answer. If the right, all right, but, detail what to do, okay?
Such as Windows Update returned to work yet; It had 1,200 mb updates; and my internet is not as fast so I decided to set Windows Update to "Check for updates but let me choose whether to download them and install them." So I'm updating slowly. But the updates are taking place normally.

One question: will, based on the logs you have seen, it is possible to know what caused the problem? If it was a program, what was it; it was a virus, which was, etc.? Or can not know that?

Canad

[SOLVED] Windows Update - Erro 80070002

Member

Attachments

Emeritus

Member

Emeritus

Member

Emeritus

Member

Emeritus

Member

Emeritus

Member

Emeritus

Attachments

Member

Emeritus

Member

Emeritus

Emeritus

Attachments

Member

Emeritus

Member