[SOLVED] [Win7 Pro x86] Windows Update error 80080005

dbdan22

Contributor
Joined
Jun 6, 2017
Posts
179
Hi,

Win 7 Pro 32 bit system

Windows Update error 80080005

sfc /scannow won't run, error: Windows Resource Protection could not start the repair service.

Ran both SURT and Windows 7 Update Troubleshooter. No change. Still won't update, won't run SFC

Ran SFCfix: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com

Zip file attached with CBS.log, checksur.log and SFCfix

Please help.

Thanks,
Dan
 

Attachments

Hello and welcome!

Export Component Based Servicing


  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  7. Right Click on the ComponentBasedServicing file on your Desktop and choose Send To -> Compressed (Zipped) Folder.


Once done please upload ComponentBasedServicing.zip via DropBox OneDrive or SendSpace etc. and include the link with your reply.
 
Hi,

Uploaded to Onedrive: https://1drv.ms/f/s!AHHOxq7pxsngcA

Thanks,
Dan

Hello and welcome!

Export Component Based Servicing


  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  7. Right Click on the ComponentBasedServicing file on your Desktop and choose Send To -> Compressed (Zipped) Folder.


Once done please upload ComponentBasedServicing.zip via DropBox OneDrive or SendSpace etc. and include the link with your reply.
 
Do you have an earlier system image? Your CBS key is severely corrupt.

System Restore was turned off on this PC.

Would it be possible to reset all of the Windows Update components? What is the correct procedure for this?

Thanks.
 
Apparently System Restore was turned off on this PC. So I don't have an earlier image.

Any other options?
 
There's one more thing to check.

If you go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\

Can you expand its contents and post a screenshot?
 
CBS key.jpg


I don't see any subkeys under it.

(On my own PC there are several.)


There's one more thing to check.

If you go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\

Can you expand its contents and post a screenshot?
 
Question. I have 4 other PC's that are more or less identical to this one. Can the subkeys be exported and imported, just to be able to do a sfc and surt?
 
Well... if my only other option is to reimage... then I guess it's worth a shot. If it at least allows sfc & surt to repair any resulting damage, then it's worth it. If it only makes things worse, then... we'll know for next time, won't we? :smile9: I guess I'll be the guinea pig then.

I will certainly make sure Windows Restore is turned on though!!!
 
Will do. I'm not onsite at the moment, I'm in via Logmein Rescue. I will be onsite at about 12:30 PM Eastern Daylight, about 1 1/2 hours from now. I'll post it as soon as I get there.

Thanks so much.
 
I'm sorry, I've done some testing in my Virtual environment and unfortunately, we cannot replace the corrupt hive because it does not exist in the file system like COMPONENTS/SYSTEM/SOFTWARE hives do.
 
I'm sorry, I've done some testing in my Virtual environment and unfortunately, we cannot replace the corrupt hive because it does not exist in the file system like COMPONENTS/SYSTEM/SOFTWARE hives do.

But I thought it was the registry key that was corrupted. Could we not just import the key from another system?

Anyhow, for what it's worth, here's the key from a healthy system: https://1drv.ms/u/s!AnHOxq7pxsngjDhgNRpF2NM1LXxY

It has all the subkeys.
 
Nope. If it was just the key, I would probably be able to recreate it after identifying which character has been bit shifted or importing a clean copy of the key from my virtual machine.

In your case, the whole "branch" is missing. In fact, multiple branches. Because CBS is the main key, and then there are multiple subkeys each of which contain more than a 1000 keys.

If it was a key or 10-20-50-100 I'd go for it, because we deal with those due to the fact that we know what is missing (usually reported by SURT), and if you look closely, you'll see that it reports PackageDetect and Packages errors.
The two keys in question contain data about which Packages are present (installed) on the system and report their state for each of the packages of an update individually.

I'm sorry to be the bearer of bad news,
 

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

Back
Top