[SOLVED] Error 0x800f0805 - Server 2019

F

flamingo2

Member
Joined
Jan 4, 2022
Posts
10
Location
UK
Hi all,

This server gets the above error when i try to get updates from the internet. I've downloaded KB5008218 and when I run it via DISM or GUI to says that it's not applicable to your computer.

The server doesn't report any errors from sfc /scannow, Dism /Online /Cleanup-Image /RestoreHealth or SFCFix

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-01-11 15:53:16.016
Microsoft Windows Server 10 Build 17763 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-01-11 19:01:45.693
----------------------EOF-----------------------

Any help would be appreciated.
 

Attachments

Hello flamingo2 :-)

There is an error in the CBS log relating to a problem with an absent language package.

Code: 
2022-01-11 15:07:53, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2022-01-11 15:07:53, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-LanguageFeatures-Basic-en-gb-Package~31bf3856ad364e35~amd64~~10.0.17763.1, status: 0x800f0954, failure source: CBS Other, start state: Absent, target state: Absent, client id: FodHelper(LanguageFeaturesOnDemand)
2022-01-11 15:07:53, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Let's see if adding this will help.

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 SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to analyse please.

When it has completed try to update again and upload new CBS logs if there are any problems.
 

Attachments

Please run a DISM restorehealth and then upload the new CBS Log please.

  1. Type cmd into the search box and right click on Command Prompt to select Run as Administrator
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
 
Please also provide the COMPONENTS hives:

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. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.


Export CBS hive
  • Click on the Start button and in the search box, 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.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.


Export SideBySide
  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\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.
Once done please upload this file via Dropbox or OneDrive or SendSpace.
 
Hello flamingo2,

You were too hasty and did not read the instructions carefully. You were asked to export the two files from your Registry as the Registry Hive File type not the .reg file type. Please do those again.
 
I am checking with other Windows update experts to see if there is anything we can do.

Your Registry has got severely damaged at some point. There are no packages keys in the Registry under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

There are no Components in the Component Detect key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect

Do you have any system restore points or registry backups that might help?
 
I do have backups of the virtual machine. I've restored a few different ones and found the ComponentDetect was there 2 weeks ago. I then figured out that running Dism /Online /Cleanup-Image /RestoreHealth deleted it.

I had to go back just over three months for the Packages.

I was exporting the ComponentDetect reg key as I went along and the size of the file is different when I find the Packages.

What would you advise? I will move onto a offline backup copy before doing anything with the live one.

Also what's the odds of it happening on two other server?
 
I don't know what caused the problem - it is unlikely to be the DISM command that did it.

If you setup an offline backup VM copy you can try the repair out and see if it works. I would copy the last good Packages key and the associated Component Detect key to see if that makes a difference. Also the Package Index key seems to be missing entries too. If the registry changes do not help it would be wise to wait until I have had a chance to review this with the other experts.
 
I exported the three missing reg keys from the backup from 3 months ago and applied them to an of line backup and ran Dism /Online /Cleanup-Image /RestoreHealth. CBS folder is attached
 

Attachments

It looks as if a lot of the corruption has been corrected but there are still 4737 warnings. No errors are showing in the CBS log.

Code: 
2022-01-20 18:55:14, Info                  CBS    Summary:
2022-01-20 18:55:14, Info                  CBS    Operation: Detect and Repair
2022-01-20 18:55:14, Info                  CBS    Operation result: 0x0
2022-01-20 18:55:14, Info                  CBS    Last Successful Step: Entire operation completes.
2022-01-20 18:55:14, Info                  CBS    Total Detected Corruption:    4737
2022-01-20 18:55:14, Info                  CBS        CBS Manifest Corruption:    0
2022-01-20 18:55:14, Info                  CBS        CBS Metadata Corruption:    4737
2022-01-20 18:55:14, Info                  CBS        CSI Manifest Corruption:    0
2022-01-20 18:55:14, Info                  CBS        CSI Metadata Corruption:    0
2022-01-20 18:55:14, Info                  CBS        CSI Payload Corruption:    0
2022-01-20 18:55:14, Info                  CBS    Total Repaired Corruption:    0
2022-01-20 18:55:14, Info                  CBS        CBS Manifest Repaired:    0
2022-01-20 18:55:14, Info                  CBS        CSI Manifest Repaired:    0
2022-01-20 18:55:14, Info                  CBS        CSI Payload Repaired:    0
2022-01-20 18:55:14, Info                  CBS        CSI Store Metadata refreshed:    True

Can you see what happens if you try and update or are you not going online with this test VM?
 
I don't think so because the update process should automatically take care of any missing items - these updates are cumulative and so they always incorporate the earlier updates.
 
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