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

Hi,

I would try to attempt to update, if it fails attach a new copy of the CBS logs.
 
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
 
Hi, it failed. Attached the output and CBSLogs.

1686558343131-png.87849
 

Attachments

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
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

Warning: This script was written specifically for this system. Do not run this script on another system.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hi,

here is the output:

Fix result of Farbar Recovery Scan Tool (x64) Version: 29-05-2023
Ran by t2-adminpodroseb (12-06-2023 11:20:16) Run:1
Running from C:\Users\t2-adminpodroseb\Desktop
Loaded Profiles: t2-adminpodroseb
Boot Mode: Normal
==============================================

fixlist content:
*****************
[HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0\2]
*****************

[HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0\2] => Error: No automatic fix found for this entry.

==== End of Fixlog 11:20:16 ====
 
Please run FRST again with the attached Fixlist, I made a mistake in the previous one.
 

Attachments

Hi,

now it removed it. Should we give the updates a new try ?

Fix result of Farbar Recovery Scan Tool (x64) Version: 29-05-2023
Ran by t2-adminpodroseb (12-06-2023 11:24:57) Run:2
Running from C:\Users\t2-adminpodroseb\Desktop
Loaded Profiles: t2-adminpodroseb
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0\2]
*****************

"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0\2" => removed successfully

==== End of Fixlog 11:24:57 ====
 
Yes, please try to update again, if it fails attach a new copy of the CBS logs.
 
Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hi there,

attached the CBSLogs, because error occurs again, and the result.



Fix result of Farbar Recovery Scan Tool (x64) Version: 29-05-2023
Ran by t2-adminpodroseb (12-06-2023 12:40:30) Run:3
Running from C:\Users\t2-adminpodroseb\Desktop
Loaded Profiles: t2-adminpodroseb
Boot Mode: Normal
==============================================

fixlist content:
*****************
CMD: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
DeleteValue: HKLM\COMPONENTS|ExecutionState
DeleteValue: HKLM\COMPONENTS|PendingXmlIdentifier
*****************


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.



========= End of CMD: =========

"HKLM\COMPONENTS\\ExecutionState" => removed successfully
"HKLM\COMPONENTS\\PendingXmlIdentifier" => removed successfully

==== End of Fixlog 12:40:33 ====
 

Attachments

Which error do you see in the Windows Update window, and is the update failing before or or after a reboot.

Please attach the following file as well: C:\Windows\WinSxS\pending.xml
Please attach al the previous CBS_persist logs as well.
 
Here's the next fix, afterwards please attempt to update again.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hi,

was successful. Now try to update again ?

Fix result of Farbar Recovery Scan Tool (x64) Version: 12-06-2023
Ran by t2-adminpodroseb (12-06-2023 14:28:36) Run:4
Running from C:\Users\t2-adminpodroseb\Desktop
Loaded Profiles: t2-adminpodroseb
Boot Mode: Normal
==============================================

fixlist content:
*****************
CMD: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS]
"PendingXmlIdentifier"=hex:37,00,34,00,39,00,65,00,34,00,33,00,36,00,62,00,61,\
00,38,00,39,00,36,00,64,00,38,00,30,00,31,00,39,00,65,00,33,00,36,00,30,00,\
31,00,30,00,30,00,61,00,30,00,32,00,34,00,61,00,30,00,32,00,33,00
"ExecutionState"=dword:00000005
EndRegedit:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0]
*****************


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.



========= End of CMD: =========

Registry ====> The operation completed successfully.

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0" => removed successfully

==== End of Fixlog 14:28:42 ====
 
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