[SOLVED] Win Server 2019 - KB5036896 - Error 0x80073712 and Dism + SFC /Scannow fails

L

LucasD

Member
Joined
Apr 15, 2024
Posts
11
Hello everyone,

I hope you can help me to fix the update error from my virtual machine. I have already tried to fix it with your SFCFix and ComponentsScanner (without a .zip config from another forum post) and therefore have the following attachments I can provide.
I will be pleased to provide you with more information. Let me know if you need more information. Everything below has been translated from German via Deepl, so the exact wording in the original may differ from the translation.

System: Windows Server 2019 Standard Version 1809 Build 17763.5576
Update that fails: KB5036896
Error code: 0x80073712

Reboot did not help.

SFC /scannow leads to the following error:
Windows Resource Protection could not perform the requested operation.

dism /online /cleanup-image /restorehealth leads to the following error:
[== 4.5% ]
Error: 14098

The component memory has been corrupted.
The DISM log file is located under "C:\Windows\Logs\DISM\dism.log".

SFCFix and ComponentsScanner, as well as DISM and CBS logs are attached.

Thank you very much. I appreciate your help!

Best regards
Lucas
 

Attachments

Hi and welcome to Sysnative,

Do you have recent backups of this server, this because the COMPONENTS hive is damaged beyond repair.

Rich (BB code): 
Number of keys: 2
Number of values: 0

==== Critical Errors ====
COMPONENTS hive is very small (<6MB). This could indicate major corruption & large missing sections of data
COMPONENTS hive contains no parsable registry values
Critical registry key "COMPONENTS\CanonicalData\Catalogs" does not exist or could not be loaded
Critical registry key "COMPONENTS\CanonicalData\Deployments" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\Components" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\VersionedIndex" does not exist or could not be loaded
Critical registry key "COMPONENTS\ServicingStackVersions" does not exist or could not be loaded
Critical registry key "COMPONENTS\Installers" does not exist or could not be loaded
 
Maxstar said:
Hi and welcome to Sysnative,

Do you have recent backups of this server, this because the COMPONENTS hive is damaged beyond repair.

Rich (BB code): 
Number of keys: 2
Number of values: 0

==== Critical Errors ====
COMPONENTS hive is very small (<6MB). This could indicate major corruption & large missing sections of data
COMPONENTS hive contains no parsable registry values
Critical registry key "COMPONENTS\CanonicalData\Catalogs" does not exist or could not be loaded
Critical registry key "COMPONENTS\CanonicalData\Deployments" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\Components" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\VersionedIndex" does not exist or could not be loaded
Critical registry key "COMPONENTS\ServicingStackVersions" does not exist or could not be loaded
Critical registry key "COMPONENTS\Installers" does not exist or could not be loaded
Click to expand...
I already thought that the server is no longer repairable. Unfortunately, we don't have a backup where the Components Store isn't broken yet.
Thank you. The thread can be closed.

Best regards
Lucas
 
Hi,

You're welcome. But do you have a very similar server (same patch level), perhaps we can use that COMPONENTS hive as replacement.
 
Is there a manual for this? How exact does the build level have to be? If it's newer, it certainly won't work, right?
 
Below the version numbers of this server, I would suggest to look if you have a server (same build / servicing stack / language packs).
Rich (BB code): 
Windows Version: Windows Server 2019 Standard x64 (10.0.17763.5576)
Servicing Stack v10.0.17763.5568 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.5568_none_56dc18119925eb9b\cbscore.dll
 
Where can I find out which SSU is installed?
I have a system that is on build 5329...
 
You can run the following commands in an elevated prompt to determine which is the active SSU.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
reg query "HKEY_LOCAL_MACHINE\COMPONENTS\ServicingStackVersions" /s
 
10.0.17763.5084 (WinBuild.160101.0800) REG_SZ 2024/4/23:9:24:12.229 10.0.17763.5084 (WinBuild.160101.0800) is the last entry

would that work? unfortunately I only have newer systems...
 
I've cloned the server and I'm currently installing the update. How would I proceed afterwards?
 
1. Create a full backup / snapshot of the problematic server.
2. Please run the following tool on the cloned server and attach the result.

Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
Great, please copy the COMPONENTS hive from the cloned server over to the problematic server.

Navigate to C:\Windows\System32\config on the problematic server.
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.
Take the file from the cloned server folder and paste it into C:\Windows\System32\config on the problematic server.

Then reboot the problematic server and run
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner again and post the result.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
Good morning too.

Let's try to perform a repair install at this stage, mostly it will bypass all the remaining issues.
  • Navigate to the URL below and sign-in with your MSDN registered account.
  • https://msdn.microsoft.com/subscriptions/securedownloads/
  • Use the search field to find and download the correct ISO file.
  • Mount the Windows Server ISO and run Setup.exe.
  • Use the option Download updates, drivers, and optional features (recommended) and click Next.
  • Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!!
  • When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here.

    653263088a599-windows-server-2022-setup.png

  • In the next screen, select the image of the installed Windows Server edition and click Next.
  • Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
  • After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
 
That worked! The server seems to be fixed as I was able to install updates from April afterwards as I only had an older ISO available.

Thank you very much for the great support!

Best regards
Lucas
 
You're welcome. Glad to hear it worked and the server is up-to-date now... (y)
I will mark this thread as solved.
 
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