[SOLVED] DISM 1734 Array Bounds Are Invalid Error

I

itguy540

Active member
Joined
Jan 19, 2024
Posts
29
Every time I install Windows Updates on this particular Windows host, it reboots and then rolls back the update.

When I run the "Dism /Online /Cleanup-Image /RestoreHealth" command, it gives me the 1734 array bounds are invalid error.

I ran the SFCFIX tool, but unfortunately it did not make a difference. I also ran the "Reset-WUComponents" powershell script/command, but that didn't help either.

Attached are my CBS.log and ComponentsScanner.txt files

Thanks in advance!
 

Attachments

Hi and welcome to Sysnative,

Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code: 
wusa /uninstall /KB:5031362
  • Let me know if it says it was successful or you get the message: The update KB5031362 is not installed on this computer.
 
Thank you for your help! It comes back and says "The update KB5031362 is not installed on this computer."
 
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: 
KB5031362
  • 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.
 
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

Plewse 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
 
The DISM command completed successfully this time, however I tried to then install the available Windows Updates. They installed and then when it rebooted, it went through the usual "undoing changes" and reverted back to before the updates were installed.

Is there a log that would show why it reverted?
 
Just to provide some more info. I see the following error in the system event log after the update rolls back:

Code: 
Installation Failure: Windows failed to install the following update with error 0x8007000D: 2024-01 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5034119).

The update appears to install fine, but when I go to reboot, it hangs on trying to stop the Windows Update Orchestrator and Trusted Installer services - it eventually stops/kills them after a good 10 minutes (at least) and then when it boots back up, it also rolls back the update.

Any thoughts? Thank you!
 
Hi,

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.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.
 
Rich (BB code): 
2024-01-21 16:38:49, Error                 CBS    Startup: Failed executing critical driver operations queue [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

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.
657716925b62b-setup-api-dev-folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
Attached is the setupapi.dev.log zipped. I included the last two files (with the most recent dates) since the current one seemed small.
 

Attachments

Export registry key as hive file.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into the command prompt and press enter.
Code: 
reg save "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" "%userprofile%\Desktop\Services.hiv"
  • Once done, a file will appear on your desktop, called Services.hiv.
  • ZIP this file and attach it to your next reply.
 
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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.
 

Attachments

Unfortunately, the fix failed! So we'll need to apply this fix with SYSTEM privileges.

Please follow these instructions to run the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool with system privileges.

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 PsExec from Microsoft Sysinternals to your desktop.
  • Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
  • Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
  • Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
  • Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
    Code: 
    psexec -i -d -s "%userprofile%\desktop\FRST64.exe"
  • FRST will make a new backup of the registry first, please wait until this process is completed.
  • Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then 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

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