[SOLVED] Win7 Windows update 80070002

M

mikent

Member
Joined
Aug 14, 2018
Posts
11
Hi,

I think i tried / applied / researched / re applied ... all ms fix, scan tools, sfc, everything i found.
Found this thread.

Ran sfcfix :

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-08-14 20:33:46.395
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








SFCFix version 3.0.0.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2018-08-14 20:37:57.828
----------------------EOF-----------------------


Bellow is the Checksur.log :



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-08-14 19:59


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 05737175c38..d366baed19b_31bf3856ad364e35_6.1.7601.24059_06a1338bb6c5403a HKLM\Components\CanonicalData\Deployments
(f) CSI Missing Deployment Key 0x00000000 b3316059937..a1b1582388e_31bf3856ad364e35_6.1.7601.24059_eeeb8747c582e0fd HKLM\Components\CanonicalData\Deployments
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_e5a6ec7fbu8720b1aqd348a8d70ee88c_31bf3856!d364e35_6.1.760q.18923_.one_d03232a36e4%9e70 identity and keyform do not match; keyform is wrong.


Summary:
Seconds executed: 300
Found 3 errors
CSI Missing Deployment Key Total count: 2
CSI Corrupt Component Keyform Total count: 1


I think i could use some help.

Thanks.
 
Hello and welcome!

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 a file sharing service and just provide the link here.
 
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Please run SURT again and attach CheckSUR.log.
 

Attachments

Last edited:
Here is the 2 files attached.
Seems like it been repaired according to checksur.log.
Awaiting instructions before doing anything else. (didnt even check windows update status)
 

Attachments

Still same error 80070002 :(
Attached CBS log : WeTransfer

I'll be away from this computer for 15 days starting tomorrow, i wont be able to remote onto it either. Will answedr later.
Thanks for your help so far.

Below, checksur :



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-08-15 20:33


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 297
No errors detected
 
No problem.

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 a file sharing service and just provide the link here.
 
Thanks!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

Let's try something different. Run the following fixlist, but do not attempt updates!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

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.



  1. Download COMPONENTS.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 Components folder on your desktop and paste it into C:\Windows\System32\config
Let me know when done.
 
Last edited:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-08-31 16:25


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 308
No errors detected
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
You must log in or register to reply here.

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

Back
Top