Can't install KB5043051 on Server 2016 - Error [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

MRezaHosseinian

MRezaHosseinian

Well-known member
Joined
Nov 28, 2023
Posts
66
Hello everyone,

Tried to Install the latest Cumulative Update for Windows Server 2016 x64 (KB5043051), but i have encountered failed operation (both from windows update option and manual .msu file installation). Ran the DISM Cleanup as well, then Checked the CBS.Log there is an Error code "0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT".

what can be done here, please help out. Thanks

Components File:

COMPONENTS.zip
 

Attachments

Please stop bumping your thread when you only posted yesterday; you even bumped on the same day! This is a support forum which is solely run by volunteers. If you need urgent help then I would suggest seeking paid support from Microsoft, otherwise please be patient and take note of the following post: Not received a reply? Quick note on response times

Hi all,

If you haven't received a response, then please take into account that all the Windows Update team members, are volunteers who kindly contribute their time and expertise to help you with your problems. Many have full-time jobs, families and other commitments which limits the amount of available time they have to answer threads.

Additionally, please take into consideration the following:
  1. The CBS log can be quite lengthy and take some time to analyse
  2. It can take some time to either find replacements for corrupted system files and/or fix registry corruption
  3. You may be running an old build number or an operating system which a helper doesn't have a VM for and therefore it can take some time to set one up
Please also note we're a very small team and one of the few forums (if not only forum) which are able to fix Windows Update problems. As a result of this, we usually receive far more threads than available helpers, therefore it may take several days for a helper to get to your thread.

Thanks,
Sysnative Windows Update Team
Click to expand...
 
Please guide me to get help from paid Microsoft forums. I really need to solve this problem, what is the paid forum's address?
 
Hi,

Microsoft Paid support has some waiting times too from what I've read in other threads, so I'm not sure if you will get any quicker response about this issue.

Step 1. Download
67139f7e69a58-SFCFix-ico.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thank you so much for the reply. SFCFix.txt is in attachment

Stage 1 of 6 in SFCFix.exe failed on server

DISM failed on 83.5% with the following error: 0x800f081f

The source files were not found.
Use the Source option to specify the location of the files required to restore the feature. For more information about specifying a source location, see Configure a Windows Repair Source.

DISM and CBS.log are also in attachment.
 

Attachments

Do you have a similar 2016 server in your network, if so please run the following command and post the result. (Replace Servername, with the correct name of the other server)
Code: 
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess
 
Rich (BB code): 
(p)    CSI Manifest Corrupt            amd64_b5977fed54447151eac614cce27b06c4_b03f5f7f11d50a3a_4.0.15744.161_none_b257f535f25ed3ad
Repair failed: Missing replacement manifest.

Great, you'll need to use a server which contain the above *.manifest files with this build number (4.0.15744.161). Unfortunately I don't have any VM with those files, and I have never been able to find this .NET update, only newer versions...
 
Just look into the "C:\Windows\WinSxS\Manifests" folder to see if the following file exists, or perform a search for this build number.

amd64_b5977fed54447151eac614cce27b06c4_b03f5f7f11d50a3a_4.0.15744.161_none_b257f535f25ed3ad.manifest
 
I found another VM with this build number. Ran DISM again but the same error:

Code: 
C:\Users\administrator.LANDGUT>DISM /Online /Cleanup-Image /RestoreHealth /Source:\\LandgutAV.landgut.landgut-behrenhoff.de\C$\Windows\WinSxS\ /LimitAccess

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.14393.4169

Abbildversion: 10.0.14393.4169

[==========================100.0%==========================]
Fehler: 0x800f081f

Die Quelldateien wurden nicht gefunden.
Geben Sie mit der Option "Quelle" den Ort der Dateien an, die zum Wiederherstellen des Features erforderlich sind. Weitere Informationen zum Angeben eines Quellorts finden Sie unter "http://go.microsoft.com/fwlink/?LinkId=243077".

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".
 

Attachments

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
4.0.15744.161
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Please do the following for just 1 *.manifest file, this to check if it's reported again in the CBS log. This because I see some signs about ManifestCache corruptions.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

SFCFix.txt attached. DISM did not completed successfully, new error at 83.5%:

Code: 
Abbildversion: 10.0.14393.4169

[===========================83.5%================          ]
Fehler: 1734

Die Datenfeldgrenzen sind unzulässig.

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".

C:\Users\administrator.LANDGUT>
 

Attachments

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