[SOLVED] Server 2019 - Installation of KB5015811 fails with 0x80073712

L

LarryK

Contributor
Joined
Jan 13, 2020
Posts
41
My RMM's NOC has repeatedly attempted to get the July monthly update installed on this (and other) Windows 2019 Standard server(s).
It has failed repeatedly with above error.
They have run SFC /Scannow. They have run multiple forms of DISM.
I kicked them off the system because, after 5 hours, I have no patience for the stupidity of re-running the same tasks and failing each time without ANY analysis.

Atttached are the latest CBS and DISM logs.
Willing to contribute to get this solved, because if it works here, it may fix two other servers.
Thanks, in advance, for your help - once again.

Larry
 

Attachments

Could you please provide the CBS persist logs as well? The latest CBS log doesn't appear to reveal much unfortunately.
 
As per your request, zipped CBS folder containing all files.
Appreciate your help.
 

Attachments

Thanks, I had to go back to the earliest log to find anything useful:

Rich (BB code): 
2022-08-06 12:53:01, Info                  CBS    FLOW: Enter Installation Stage: Closure Analysis, Current Operation Stage: Resolving
2022-08-06 12:53:09, Error                 CSI    00001c06 (F) CertCreateCTLContext returned ERROR_INVALID_DATA.
[gle=0x80004005]
2022-08-06 12:53:09, Error                 CSI    00001c07@2022/8/6:16:53:09.342 (F) Attempting to mark store corrupt with category [l:14 ml:15]'CorruptCatalog'[gle=0x80004005]
2022-08-06 12:53:09, Error                 CSI    00001c08@2022/8/6:16:53:09.343 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1626): Store corruption detected in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: 0
  FileHashMismatch on resource '\winsxs\catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.cat'[gle=0x80004005]

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 WeTransfer and then just provide the link in your reply.
 
Thanks, please find the fix script attached below.

SFCFix Script
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. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-18 19:43:00.491
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\InstallAdmin\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\windows\WinSxS\Catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.cat

Successfully copied file C:\Users\InstallAdmin\AppData\Local\niemiro\Archive\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.cat to C:\windows\WinSxS\Catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.cat.

Successfully restored ownership for C:\windows\WinSxS\Catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.cat
Successfully restored permissions on C:\windows\WinSxS\Catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.cat
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\7fe155ca9a7bbca5bd5fcd17a44c1207f0e1b78ea283a196a453607d99a03d2f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2022-08-18 19:43:01.436
Script hash: KikDR946M8UeuN3Aa4GlE9SML0MpuXXF2jidmESeF7A=
----------------------EOF-----------------------

The remaining question: do I need to reboot this server?
 
You shouldn't have to, however, I would run the usual DISM command to make sure everything is okay before attempting to update again.

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth
 
Command run at 07:40 on 08/19/2022. File attached.
Looks "clean" to me - do you concur?
 

Attachments

The CBS log would be more useful but if DISM didn't throw any errors while running then I would attempt to update again.
 
This month's (August) updates were installed successfully, so this issue can be closed.
I'll be opening a new thread for the other affected server.
Thank you very much for your help with this problem.
 
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