What's new

80073712 - Windows Server 2016

redstar1

Member
Joined
May 11, 2018
Messages
6
Hi, I've been banging my head against this for a couple of weeks with no joy, but maybe someone here has some ideas I haven't thought of yet.

Attempting to install KB4467691 on Server 2016 and it is failing with 80073712 - SXS_COMPONENT_STORE_CORRUPT.

Have tried dism repairs from healthy sources to no avail and all sorts of other 'tricks' such as unpacking the update and trying to force an install of it, and previous updates giving the contents of some log files. About ready to give up and just rebuild the image but thought I'd try here first as I've seen miracles on this forum!

So... SFC /SCANNOW reports that corrupt files were found and successfully repaired - details in CBS.log.

SFCFix.exe returns no corruption.

CBS log folder is here: https://1drv.ms/u/s!AhCihTM3XDKT2W-tkVqDR2rkrFdY


Any help appreciated!
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Hello and welcome! Do you still require assistance?
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Please open Command Prompt as Administrator and enter the following commands pressing Enter after each:


Code:
reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5"  /ve /f
Code:
reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5\10.0"  /ve /f
Let me know if you get the message: "The operation completed successfully."
 

redstar1

Member
Joined
May 11, 2018
Messages
6
Please open Command Prompt as Administrator and enter the following commands pressing Enter after each:


Code:
reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5"  /ve /f
Code:
reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5\10.0"  /ve /f
Let me know if you get the message: "The operation completed successfully."

Key is deleted.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Good!

Step#1 - DISM /RestoreHealth Scan
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. Right-click on the Start button and select Command Prompt (Admin)
  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
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Excellent!

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the feature just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 

redstar1

Member
Joined
May 11, 2018
Messages
6
Excellent!

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the feature just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log

The Procmon log file will be enormous. What do you need to see in particular and I'll filter it.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Start it closer to failure then, but I do need to see the whole log. Zip it up to reduce the size.
 
Top