[SOLVED] Windows update error 0x80073712 and DISM Error: 1734 The array bounds are invalid.

Hi,

Please attempt to update and if it fails attach a new copy of the CBS logs.
 
Sorry for late response, still Windows update Error code: (0x80073712).

We have a WSUS server, i tried to run updates with and without the WSUS server.

CBS.log
 
Rich (BB code):
2024-03-04 15:33:23, Error                 CSI    00001a5d@2024/3/4:14:33:23.690 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3705): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'amd64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.5246_tr-tr_6b3d071c8a7406dd'[gle=0x80004005]

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.
 
Hi,

Download
6530fbb0f4101-56f31e53c97da-SFCFix.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.
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.

Afterwards reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Hi,

You're welcome. Glad to hear the problem has been resolved.

There are several reasons for these kind of corruptions, like connectivity issues, power cycle failures, forced shutdowns, system crashes. Allthough is difficult to ascertain what the exact cause was.
 
Okay i understand, thanks again for the help, i'll post a new thread regarding another machine with similar issues.
 

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

Back
Top