[SOLVED] WS2019 - 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT (xa-app-srv12)

Hmm, since the latest CBS logs are from a month ago, I would suggest to attempt to update first. If it fails attach a new copy of the CBS logs.
 
Pleas don't post the CBS in plain text in your post, just attach them. However the latest log didn't reveal anything so please attach a copy of all the CBS logs in your next post.

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Hi,

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:
749e436ba896d8019e360100a024a023
  • 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.
 
Rich (BB code):
2023-07-18 10:08:18, Info                  CSI    00000003 Mismatched pending xml and registry identifiers
  In registry [l:32]'749e436ba896d8019e360100a024a023'
  In pending.xml [l:32]'1c977d821e9dd901fc0c00009028781a'

2023-07-18 10:08:18, Error                 CSI    00000004@2023/7/18:08:08:18.032 (F) Attempting to mark store corrupt with category [l:27 ml:28]'CorruptPendingXmlIdentifier'[gle=0x80004005]
2023-07-18 10:08:18, Error                 CSI    00000005@2023/7/18:08:08:18.032 (F) onecore\base\wcp\componentstore\com\transaction.cpp(1244): Store corruption detected in function ComStoreImpl::VerifyPendingXmlSequenceIdAgainstStoreKey expression: 0
  RegistryCorruption on resource '\Registry\Machine\COMPONENTS\\PendingXmlIdentifier'[gle=0x80004005]

Open an elevated command prompt, run the following command and post the result.
Code:
reg load HKLM\COMPONENTS C:\Windows\System32\Config\COMPONENTS
reg query HKLM\COMPONENTS

And attach the following file to your next post: %windir%\winsxs\pending.xml
 
Here are the results.


Code:
HKEY_LOCAL_MACHINE\COMPONENTS
    StoreFormatVersion    REG_BINARY    30002E0030002E0030002E003600
    StoreArchitecture    REG_BINARY    09000000
    PendingXmlIdentifier    REG_BINARY    64003800320031003500610063003800380063006200610064003900300031006200370036006500300031003000300065003400320062006400340031006600
    ExecutionState    REG_DWORD    0x1

HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData
HKEY_LOCAL_MACHINE\COMPONENTS\CCPInterface
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData
HKEY_LOCAL_MACHINE\COMPONENTS\Drivers
HKEY_LOCAL_MACHINE\COMPONENTS\Installers
HKEY_LOCAL_MACHINE\COMPONENTS\NonCanonicalData
HKEY_LOCAL_MACHINE\COMPONENTS\ServicingStackVersions
 

Attachments

Please attach a new copy of the COMPONENTS hive.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Please post the latest CBS logs as well, the value data PendingXmlIdentifier corresponds with the identifier in Pending.xml.
 
Upload the setupapi.dev.log file
  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
Some interesting parts are happening after a reboot of the machine. I will now search for additional updates.

1690372644206.png
 
Look like this is fine now! Finding no more updates because of not approved updates on WSUS. I can also query again the installed windows features/roles which was not possible before.

You are the windows update god ;)
 
It's a bit unclear why the CBS reported an issue about "CorruptPendingXmlIdentifier" earlier, but glad to hear you were able to update after the last reboot.

I will mark this thread as solved then... (y)
 
You're welcome. This was a tough issue, especially rebuilding the components hive with the missing VersionIndex subkey from a backup was a challenge..
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top