[SOLVED] Server 2019 Update Error 0x80070002

flosch

New member
Joined
Feb 19, 2023
Posts
4
Hi,

I do have an update error since some time already - 0x80070002 -> I tried all the standard-suggestions. sfc, dism, remove softwaredistribution.... nothing worked.

attached a fresh cbs.log after an attempted install of 2023-02 update and an sfc /scannow as well as a Dism /Online /Cleanup-Image /RestoreHealth

Anyone able to help`?

thanks so much!
 

Attachments

Hi and welcome to Sysnative,

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

The Component Based Servicing hive is damaged beyond repair. Do you have recent backups of the Software hive from this directory: C:\Windows\System32\Config.
 
Hi,

thanks - since this issue already persists more then a year (noone cared to invest), I doubt that any recent backup (no backup before december 22) will have a working one (just restored one, but regedit says it can't load it...)
Any chance we can use one from a comparable server (which is up to date, of course).

If not, I guess I have to setup the server from scratch - unfortunately.
 
That's unfortunate, the registry of an up-to-date server will differ too much with the one that is damaged. So basically only an in-place upgrade or clean install from scratch remains to resolve this issue.
 
Been worth a try. I will set up the server fresh.
Thanks anyway - really appreciate the time and effort
 
You're welcome. Unfortunately, we couldn't solve this problem for you.
 

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

Back
Top